Skip to content
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

nit: possibly the biggest vocabulary nitpick of all time #5131

Merged
merged 1 commit into from
Dec 13, 2024
Merged

nit: possibly the biggest vocabulary nitpick of all time #5131

Show file tree
Hide file tree
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
12 changes: 6 additions & 6 deletions app/docs/src/explanation/aws-authentication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,13 +11,13 @@ System Initiative provides a number of ways to authenticate to AWS.

If you have generated static access keys for a user then you can set
`AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` directly in the `AWS Credential`
asset.
Asset.

## AWS SSO Credentials

If you have generated credentials via the command `aws sso login` then you can
set `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY` and `AWS_SESSION_TOKEN`
directly in the `AWS Credential` asset.
directly in the `AWS Credential` Asset.

## Assuming a Role

Expand All @@ -28,7 +28,7 @@ nothing except assume roles in other accounts. The ARN of the user is

Every workspace has a unique token assigned to it at creation. It is accessible
from within your workspace via the gear icon in the upper right. Please treat
this as a secret.
this as a Secret.

You can create a role using the token and the arn above, with a trust
relationship as below and attach any required permissions you want to give the
Expand All @@ -55,6 +55,6 @@ role:
```

Take the arn of the role that you created and set that in the `AssumeRole` field
in the AWS Credential asset. You don’t need to set an access key or a secret
access key. You can ensure it works by putting an AWS Credential on the asset,
selecting the secret you created and it will validate your credentials.
in the AWS Credential Asset. You don’t need to set an access key or a secret
access key. You can ensure it works by putting an AWS Credential on the Asset,
selecting the Secret you created and it will validate your credentials.
Loading
Loading