From 1d345af5dbf0d6b0a7686fe8b42854a5795d8e43 Mon Sep 17 00:00:00 2001
From: Bharat <88349550+tinder-bharatchandrapenta@users.noreply.github.com>
Date: Sun, 19 Nov 2023 12:23:44 -0800
Subject: [PATCH] Update installation.md/IAM Roles

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>
---
 documentation/docs/getting-started/installation.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/documentation/docs/getting-started/installation.md b/documentation/docs/getting-started/installation.md
index 3d044a5160..8559152f1b 100644
--- a/documentation/docs/getting-started/installation.md
+++ b/documentation/docs/getting-started/installation.md
@@ -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.
+:::
 
 #### Google Cloud Storage