Support for temporary credential with OIDC
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
Research direction
Start by reading the example workflow in the issue and compare the existing AWS access-key inputs with the aws-actions/configure-aws-credentials@v4 step. Determine how this action receives credentials and what OIDC-based usage should look like; done means a temporary role can deploy the Lambda without static access-key inputs, with documentation or workflow validation covering the example.
Written by the indexing model from the issue text.
Description
This should be in gist but no other place to put it.
This action supports the use of OIDC for authentication
Instead of the AWS Access KEY, which inherits human flaws and cannot be whitelisted
uses: appleboy/lambda-action@v0.2.0
with:
aws_access_key_id: ${{ secrets.AWS_ACCESS_KEY_ID }}
aws_secret_access_key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
aws_region: ${{ secrets.AWS_REGION }}
function_name: gorush
zip_file: output.zip
dry_run: true
With OIDC/AUTH2, granular permissions can be given with temporary access.
The example below shows the action used with OIDC support.
- name: Configure AWS credentials
uses: aws-actions/configure-aws-credentials@v4
with:
role-to-assume: arn:aws:iam::${{ secrets.awsAccountId }}:role/github-actions-oidc-role
aws-region: ${{ secrets.AWS_REGION }}
- name: Deploy function
uses: appleboy/lambda-action@v0.2.0
with:
function_name: function_name
zip_file: funciton.zip
aws_region: region_name
- Dominant language
- D2
- Stars
- 435
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from appleboy/lambda-action
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
appleboy/lambda-action#87 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
appleboy/lambda-action#84 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
appleboy/lambda-action#83 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
appleboy/lambda-action#82 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
appleboy/lambda-action#81 · 9 comments ·
All issues in appleboy/lambda-action
Similar issues
-
kb-infra-drift
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
OCHA-DAP/ds-knowledge-base#653 · 1 comment ·
-
intake mcp-intake needs-ac needs-human-review priority:medium type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Ikalus1988/MisakaNet#2102 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
llvm/lighthouse#283 ·
-
🤔 refinement needed
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
equinor/radix-operator#1979 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100