From 2481858bee3aaf233cea20246a2555f1997d3149 Mon Sep 17 00:00:00 2001 From: Sven Strittmatter Date: Fri, 23 Feb 2024 12:11:16 +0100 Subject: [PATCH] Docuemnt how to use AWS IAM for S3 in AWS Signed-off-by: Sven Strittmatter --- documentation/docs/getting-started/installation.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/documentation/docs/getting-started/installation.md b/documentation/docs/getting-started/installation.md index 5427e1b213..246e519531 100644 --- a/documentation/docs/getting-started/installation.md +++ b/documentation/docs/getting-started/installation.md @@ -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 @@ -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