From 80ed412f2cb94a8ed20a779c0e7ff3bd0d685100 Mon Sep 17 00:00:00 2001 From: Tom Keller <1083460+kellertk@users.noreply.github.com> Date: Mon, 4 Aug 2025 16:17:49 -0700 Subject: [PATCH] fix: update readme to 4.3.1 (#1424) This is a fix instead of a chore to force a 4.3.1 tag Release-as: 4.3.1 --- README.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/README.md b/README.md index 01295e4..b498cd7 100644 --- a/README.md +++ b/README.md @@ -179,7 +179,7 @@ this action will always consider the `HTTP_PROXY` environment variable. Manually configured proxy: ```yaml -uses: aws-actions/configure-aws-credentials@v4.3.0 +uses: aws-actions/configure-aws-credentials@v4.3.1 with: aws-region: us-east-2 role-to-assume: my-github-actions-role @@ -262,13 +262,13 @@ line. Inline session policy examples ```yaml - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: inline-session-policy: '{"Version":"2012-10-17","Statement":[{"Sid":"Stmt1","Effect":"Allow","Action":"s3:List*","Resource":"*"}]}' ``` Or we can have a nicely formatted JSON as well: ```yaml - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: inline-session-policy: >- { @@ -294,13 +294,13 @@ the role. Managed session policy examples ```yaml - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: managed-session-policies: arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess ``` And we can pass multiple managed policies likes this: ```yaml - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: managed-session-policies: | arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess @@ -338,7 +338,7 @@ You can specify the audience through the `audience` input: ```yaml - name: Configure AWS Credentials for China region audience - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: audience: sts.amazonaws.com.cn aws-region: cn-northwest-1 @@ -412,7 +412,7 @@ Examples ### AssumeRoleWithWebIdentity ```yaml - name: Configure AWS Credentials - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: aws-region: us-east-2 role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role @@ -426,13 +426,13 @@ environment variable and use it to assume the role ### AssumeRole with role previously assumed by action in same workflow ```yaml - name: Configure AWS Credentials - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: aws-region: us-east-2 role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role role-session-name: MySessionName - name: Configure other AWS Credentials - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: aws-region: us-east-2 role-to-assume: arn:aws:iam::987654321000:role/my-second-role @@ -447,7 +447,7 @@ role, `arn:aws:iam::987654321000:role/my-second-role`. ### AssumeRole with static IAM credentials in repository secrets ```yaml - name: Configure AWS Credentials - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }} aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }} @@ -466,7 +466,7 @@ name, like `role-to-assume: my-github-actions-role`. ```yaml - name: Configure AWS Credentials 1 id: creds - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: aws-region: us-east-2 role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role @@ -475,7 +475,7 @@ name, like `role-to-assume: my-github-actions-role`. run: | aws sts get-caller-identity - name: Configure AWS Credentials 2 - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: aws-region: us-east-2 aws-access-key-id: ${{ steps.creds.outputs.aws-access-key-id }}