aws-actions/configure-aws-credentials
1
0
Fork 0
mirror of https://github.com/aws-actions/configure-aws-credentials.git synced 2026-09-02 05:55:10 +09:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source 
Updated version tags in examples to reflect the latest semantic version.
This commit is contained in:
Alisha Kulkarni
2025-04-17 13:35:40 -07:00
committed by kellertk
parent 232435c0c0
commit cd5db3dc55
1 changed files with 13 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+13 -13
View File
@@ -197,7 +197,7 @@ line like this:
``` ```
Or we can have a nicely formatted JSON as well: Or we can have a nicely formatted JSON as well:
```yaml ```yaml
uses: aws-actions/configure-aws-credentials@v4 uses: aws-actions/configure-aws-credentials@v4.1.0
with: with:
inline-session-policy: >- inline-session-policy: >-
{ {
@@ -218,13 +218,13 @@ The Amazon Resource Names (ARNs) of the IAM managed policies that you want to
use as managed session policies. The policies must exist in the same account as use as managed session policies. The policies must exist in the same account as
the role. You can pass a single managed policy like this: the role. You can pass a single managed policy like this:
```yaml ```yaml
uses: aws-actions/configure-aws-credentials@v4 uses: aws-actions/configure-aws-credentials@v4.1.0
with: with:
managed-session-policies: arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess managed-session-policies: arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess
``` ```
And we can pass multiple managed policies likes this: And we can pass multiple managed policies likes this:
```yaml ```yaml
uses: aws-actions/configure-aws-credentials@v4 uses: aws-actions/configure-aws-credentials@v4.1.0
with: with:
managed-session-policies: | managed-session-policies: |
arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess
@@ -299,7 +299,7 @@ You can specify the audience through the `audience` input:
```yaml ```yaml
- name: Configure AWS Credentials for China region audience - name: Configure AWS Credentials for China region audience
uses: aws-actions/configure-aws-credentials@v4 uses: aws-actions/configure-aws-credentials@v4.1.0
with: with:
audience: sts.amazonaws.com.cn audience: sts.amazonaws.com.cn
aws-region: us-east-3 aws-region: us-east-3
@@ -434,7 +434,7 @@ You can use this action to simply configure the region and account ID in the
environment, and then use the runner's credentials for all AWS API calls made by environment, and then use the runner's credentials for all AWS API calls made by
your Actions workflow: your Actions workflow:
```yaml ```yaml
uses: aws-actions/configure-aws-credentials@v4 uses: aws-actions/configure-aws-credentials@v4.1.0
with: with:
aws-region: us-east-2 aws-region: us-east-2
``` ```
@@ -444,7 +444,7 @@ APIs called by your Actions workflow.
Or, you can use this action to assume a role, and then use the role credentials Or, you can use this action to assume a role, and then use the role credentials
for all AWS API calls made by your Actions workflow: for all AWS API calls made by your Actions workflow:
```yaml ```yaml
uses: aws-actions/configure-aws-credentials@v4 uses: aws-actions/configure-aws-credentials@v4.1.0
with: with:
aws-region: us-east-2 aws-region: us-east-2
role-to-assume: my-github-actions-role role-to-assume: my-github-actions-role
@@ -466,7 +466,7 @@ variable.
Manually configured proxy: Manually configured proxy:
```yaml ```yaml
uses: aws-actions/configure-aws-credentials@v4 uses: aws-actions/configure-aws-credentials@v4.1.0
with: with:
aws-region: us-east-2 aws-region: us-east-2
role-to-assume: my-github-actions-role role-to-assume: my-github-actions-role
@@ -493,7 +493,7 @@ should include the AWS CLI by default.
### AssumeRoleWithWebIdentity (recommended) ### AssumeRoleWithWebIdentity (recommended)
```yaml ```yaml
- name: Configure AWS Credentials - name: Configure AWS Credentials
uses: aws-actions/configure-aws-credentials@v4 uses: aws-actions/configure-aws-credentials@v4.1.0
with: with:
aws-region: us-east-2 aws-region: us-east-2
role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role
@@ -507,13 +507,13 @@ environment variable and use it to assume the role
### AssumeRole with role previously assumed by action in same workflow ### AssumeRole with role previously assumed by action in same workflow
```yaml ```yaml
- name: Configure AWS Credentials - name: Configure AWS Credentials
uses: aws-actions/configure-aws-credentials@v4 uses: aws-actions/configure-aws-credentials@v4.1.0
with: with:
aws-region: us-east-2 aws-region: us-east-2
role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role
role-session-name: MySessionName role-session-name: MySessionName
- name: Configure other AWS Credentials - name: Configure other AWS Credentials
uses: aws-actions/configure-aws-credentials@v4 uses: aws-actions/configure-aws-credentials@v4.1.0
with: with:
aws-region: us-east-2 aws-region: us-east-2
role-to-assume: arn:aws:iam::987654321000:role/my-second-role role-to-assume: arn:aws:iam::987654321000:role/my-second-role
@@ -528,7 +528,7 @@ role, `arn:aws:iam::987654321000:role/my-second-role`.
### AssumeRole with static IAM credentials in repository secrets ### AssumeRole with static IAM credentials in repository secrets
```yaml ```yaml
- name: Configure AWS Credentials - name: Configure AWS Credentials
uses: aws-actions/configure-aws-credentials@v4 uses: aws-actions/configure-aws-credentials@v4.1.0
with: with:
aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }} aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }} aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
@@ -547,7 +547,7 @@ name, like `role-to-assume: my-github-actions-role`.
```yaml ```yaml
- name: Configure AWS Credentials 1 - name: Configure AWS Credentials 1
id: creds id: creds
uses: aws-actions/configure-aws-credentials@v4 uses: aws-actions/configure-aws-credentials@v4.1.0
with: with:
aws-region: us-east-2 aws-region: us-east-2
role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role
@@ -556,7 +556,7 @@ name, like `role-to-assume: my-github-actions-role`.
run: | run: |
aws sts get-caller-identity aws sts get-caller-identity
- name: Configure AWS Credentials 2 - name: Configure AWS Credentials 2
uses: aws-actions/configure-aws-credentials@v4 uses: aws-actions/configure-aws-credentials@v4.1.0
with: with:
aws-region: us-east-2 aws-region: us-east-2
aws-access-key-id: ${{ steps.creds.outputs.aws-access-key-id }} aws-access-key-id: ${{ steps.creds.outputs.aws-access-key-id }}