Skip to content

Documenting AWS IAM Role Support for S3 Configuration #2106

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

Closed
tinder-bharatchandrapenta wants to merge 1 commit into from
Closed

Documenting AWS IAM Role Support for S3 Configuration #2106

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
3 changes: 3 additions & 0 deletions documentation/docs/getting-started/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,6 +69,9 @@ s3:
# kubectl create secret generic securecodebox-s3-credentials --from-literal=accesskey="******" --from-literal=secretkey="******"
keySecret: securecodebox-s3-credentials
```
:::note
If you prefer to use AWS IAM roles instead of access keys for authentication, set s3.authType to aws-irsa and s3.awsStsEndpoint should be configured as https://sts.eu-west-1.amazonaws.com in your helm values. This approach leverages IAM roles for more secure and efficient access management.

@Weltraumschaf Weltraumschaf Jan 16, 2024

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO it would be better to use a more generic URL e.g. https://sts.REGION.amazonaws.com to prevent user to simply copy & paste this and accidentally use a bad region. You should also encapsulate the URL with backticks to format it as code, since Docusaurus does not allow plain URLs in markdown anymore.

:::

#### Google Cloud Storage

Expand Down