From 7fe9149dbf4499d1a4cc09a80181504115f930b3 Mon Sep 17 00:00:00 2001
From: Henry Griffiths <42880130+henrygriffiths@users.noreply.github.com>
Date: Mon, 24 Nov 2025 17:11:13 -0600
Subject: [PATCH] chore: update readme version to v5.1.1
---
README.md | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/README.md b/README.md
index 17bdc50d1..d1c840e8c 100644
--- a/README.md
+++ b/README.md
@@ -181,7 +181,7 @@ this action will always consider the `HTTP_PROXY` environment variable.
Manually configured proxy:
```yaml
-uses: aws-actions/configure-aws-credentials@v5.1.0
+uses: aws-actions/configure-aws-credentials@v5.1.1
with:
aws-region: us-east-2
role-to-assume: my-github-actions-role
@@ -252,13 +252,13 @@ line.
Inline session policy examples
```yaml
- uses: aws-actions/configure-aws-credentials@v5.1.0
+ uses: aws-actions/configure-aws-credentials@v5.1.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@v5.1.0
+ uses: aws-actions/configure-aws-credentials@v5.1.1
with:
inline-session-policy: >-
{
@@ -284,13 +284,13 @@ the role.
Managed session policy examples
```yaml
- uses: aws-actions/configure-aws-credentials@v5.1.0
+ uses: aws-actions/configure-aws-credentials@v5.1.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@v5.1.0
+ uses: aws-actions/configure-aws-credentials@v5.1.1
with:
managed-session-policies: |
arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess
@@ -328,7 +328,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@v5.1.0
+ uses: aws-actions/configure-aws-credentials@v5.1.1
with:
audience: sts.amazonaws.com.cn
aws-region: cn-northwest-1
@@ -402,7 +402,7 @@ Examples
### AssumeRoleWithWebIdentity
```yaml
- name: Configure AWS Credentials
- uses: aws-actions/configure-aws-credentials@v5.1.0
+ uses: aws-actions/configure-aws-credentials@v5.1.1
with:
aws-region: us-east-2
role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role
@@ -416,13 +416,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@v5.1.0
+ uses: aws-actions/configure-aws-credentials@v5.1.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@v5.1.0
+ uses: aws-actions/configure-aws-credentials@v5.1.1
with:
aws-region: us-east-2
role-to-assume: arn:aws:iam::987654321000:role/my-second-role
@@ -439,7 +439,7 @@ Note that the trust relationship/trust policy of the second role must grant the
### AssumeRole with static IAM credentials in repository secrets
```yaml
- name: Configure AWS Credentials
- uses: aws-actions/configure-aws-credentials@v5.1.0
+ uses: aws-actions/configure-aws-credentials@v5.1.1
with:
aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
@@ -458,7 +458,7 @@ name, like `role-to-assume: my-github-actions-role`.
```yaml
- name: Configure AWS Credentials 1
id: creds
- uses: aws-actions/configure-aws-credentials@v5.1.0
+ uses: aws-actions/configure-aws-credentials@v5.1.1
with:
aws-region: us-east-2
role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role
@@ -467,7 +467,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@v5.1.0
+ uses: aws-actions/configure-aws-credentials@v5.1.1
with:
aws-region: us-east-2
aws-access-key-id: ${{ steps.creds.outputs.aws-access-key-id }}