Skip to content

fix: update readme to 4.3.1 #1424

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 4, 2025
Merged

fix: update readme to 4.3.1 #1424

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 12 additions & 12 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,7 +178,7 @@ this action will always consider the `HTTP_PROXY` environment variable.

Manually configured proxy:
```yaml
uses: aws-actions/[email protected].0
uses: aws-actions/[email protected].1
with:
aws-region: us-east-2
role-to-assume: my-github-actions-role
Expand Down Expand Up @@ -249,13 +249,13 @@ line.
<summary>Inline session policy examples</summary>

```yaml
uses: aws-actions/[email protected].0
uses: aws-actions/[email protected].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/[email protected].0
uses: aws-actions/[email protected].1
with:
inline-session-policy: >-
{
Expand All @@ -281,13 +281,13 @@ the role.
<summary>Managed session policy examples</summary>

```yaml
uses: aws-actions/[email protected].0
uses: aws-actions/[email protected].1
with:
managed-session-policies: arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess
```
And we can pass multiple managed policies likes this:
```yaml
uses: aws-actions/[email protected].0
uses: aws-actions/[email protected].1
with:
managed-session-policies: |
arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess
Expand Down Expand Up @@ -325,7 +325,7 @@ You can specify the audience through the `audience` input:

```yaml
- name: Configure AWS Credentials for China region audience
uses: aws-actions/[email protected].0
uses: aws-actions/[email protected].1
with:
audience: sts.amazonaws.com.cn
aws-region: cn-northwest-1
Expand Down Expand Up @@ -399,7 +399,7 @@ Examples
### AssumeRoleWithWebIdentity
```yaml
- name: Configure AWS Credentials
uses: aws-actions/[email protected].0
uses: aws-actions/[email protected].1
with:
aws-region: us-east-2
role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role
Expand All @@ -413,13 +413,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/[email protected].0
uses: aws-actions/[email protected].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/[email protected].0
uses: aws-actions/[email protected].1
with:
aws-region: us-east-2
role-to-assume: arn:aws:iam::987654321000:role/my-second-role
Expand All @@ -434,7 +434,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/[email protected].0
uses: aws-actions/[email protected].1
with:
aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
Expand All @@ -453,7 +453,7 @@ name, like `role-to-assume: my-github-actions-role`.
```yaml
- name: Configure AWS Credentials 1
id: creds
uses: aws-actions/[email protected].0
uses: aws-actions/[email protected].1
with:
aws-region: us-east-2
role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role
Expand All @@ -462,7 +462,7 @@ name, like `role-to-assume: my-github-actions-role`.
run: |
aws sts get-caller-identity
- name: Configure AWS Credentials 2
uses: aws-actions/[email protected].0
uses: aws-actions/[email protected].1
with:
aws-region: us-east-2
aws-access-key-id: ${{ steps.creds.outputs.aws-access-key-id }}
Expand Down
Loading