aws-actions/configure-aws-credentials

• https://github.com/aws-actions/configure-aws-credentials

 aws-actions/configure-aws-credentials@v4
 aws-actions/configure-aws-credentials@v3
 aws-actions/configure-aws-credentials@v2
 aws-actions/configure-aws-credentials@v1

  aws-actions/configure-aws-credentials@v1
    - name: Configure AWS credentials
      uses: aws-actions/configure-aws-credentials@v1
      with:
        aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
        aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
        aws-region: ${{ env.AWS_REGION }}

- name: Configure AWS credentials
       id: creds
       uses: aws-actions/configure-aws-credentials@v4
       with:
         audience: sts.amazonaws.com
         role-to-assume: arn:aws:iam::$Template:Secrets.AWS ACCOUNT ID YOURENV:role/OIDC_YourGitHubActions
         aws-region: ${{ secrets.AWS_REGION_YOURENV }}

( audience: The JWT audience when using OIDC )

Official example

   - name: Configure AWS Credentials
     uses: aws-actions/configure-aws-credentials@v1
     with:
       role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role
       aws-region: us-east-2

Related

• aws-actions/configure-aws-credentials@v1-node16
• aws-access-key-id
• secrets.
• env.
• Node 16

Activities

• Understand security benefits of role-to-assume vs aws-access-key-id https://github.com/aws-actions/configure-aws-credentials#assuming-a-role

See also

• aws-actions/configure-aws-credentials
• aws-actions: configure-aws-credentials, amazon-ecr-login, checkout
• uses:, checkout@v3, configure-aws-credentials, docker/login-action, 1password/