You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -108,7 +108,7 @@ There are four different supported ways to retrieve credentials. We recommend
108
108
using [GitHub's OIDC provider](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services)
109
109
to get short-lived credentials needed for your actions. Specifying
110
110
`role-to-assume`**without** providing an `aws-access-key-id` or a
111
-
`web-identity-token-file`(or setting `role-chaining`) will signal to the action that you wish to use the
111
+
`web-identity-token-file`, or setting `role-chaining`, will signal to the action that you wish to use the
112
112
OIDC provider. If `role-chaining` is `true`, existing credentials in the environment will be used to assume `role-to-assume`.
113
113
114
114
The following table describes which identity is used based on which values are supplied to the Action:
0 commit comments