Documenting AWS IAM Role Support for S3 Configuration#2106
Documenting AWS IAM Role Support for S3 Configuration#2106tinder-bharatchandrapenta wants to merge 1 commit intosecureCodeBox:mainfrom
Conversation
By explicitly documenting this option, we make our tool more accessible and user-friendly, especially for those adhering to specific security policies or new to AWS services. Signed-off-by: Bharat <88349550+tinder-bharatchandrapenta@users.noreply.github.com>
✅ Deploy Preview for docs-securecodebox ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Hi @tinder-bharatchandrapenta, thanks for your contribution. We'll review it as soon as possible. In the meantime, would you please register here as a contributor? |
Weltraumschaf
left a comment
Weltraumschaf
left a comment
There was a problem hiding this comment.
Thanks for your contribution <3
Please see my comment in the the code.
Also, please add your self to the CONTRIBUTORS.md and sign-off your commits. You can do it in this PR.
| 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. |
There was a problem hiding this comment.
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.
|
|
See #2314 |
2 participants
By explicitly documenting this option, we make our tool more accessible and user-friendly, especially for those adhering to specific security policies or new to AWS services.
Description
Checklist