Skip to content

Commit 6b69b7b

Browse files
committed
Docuemnt how to use AWS IAM for S3 in AWS
Signed-off-by: Sven Strittmatter <sven.strittmatter@iteratec.com>
1 parent 57436a1 commit 6b69b7b

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

documentation/docs/getting-started/installation.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ helm --namespace securecodebox-system upgrade --install securecodebox-operator s
2626

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

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

3131
## Version Support
3232

@@ -74,6 +74,13 @@ s3:
7474
keySecret: securecodebox-s3-credentials
7575
```
7676
77+
:::info
78+
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
79+
80+
1. `s3.authType` to `aws-irsa`, and
81+
2. `s3.awsStsEndpoint` to your desired region (`https://sts.REGION.amazonaws.com`).
82+
:::
83+
7784
#### Google Cloud Storage
7885

7986
```yaml

0 commit comments

Comments
 (0)