Skip to content

Docuemnt how to use AWS IAM for S3 in AWS #2314

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

Merged
Weltraumschaf merged 1 commit into from
Feb 23, 2024
Merged

Docuemnt how to use AWS IAM for S3 in AWS #2314

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
9 changes: 8 additions & 1 deletion documentation/docs/getting-started/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ helm --namespace securecodebox-system upgrade --install securecodebox-operator s

If you didn't see any errors you now have the secureCodeBox Operator up and running! 🥳 🚀

Your now ready to install your [first scan types and start your first scans](/docs/getting-started/first-scans).
You're now ready to install your [first scan types and start your first scans](/docs/getting-started/first-scans).

## Version Support

Expand Down Expand Up @@ -74,6 +74,13 @@ s3:
keySecret: securecodebox-s3-credentials
```

:::info
Instead of using access keys it is possible to use **IAM roles** for more fien grained access management. To achieve that set in your helm values

1. `s3.authType` to `aws-irsa`, and
2. `s3.awsStsEndpoint` to your desired region (`https://sts.REGION.amazonaws.com`).
:::

#### Google Cloud Storage

```yaml
Expand Down