Skip to content

Commit 1901d0c

Browse files
committed
updated doc for AWS secrets
1 parent 9e4efbc commit 1901d0c

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

docs/IntelOwl/advanced_configuration.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -208,11 +208,13 @@ You need to configure the environment variable `AWS_SES` to `True` to enable it.
208208

209209
You can use the "Secrets Manager" to store your credentials. In this way your secrets would be better protected.
210210

211-
Instead of adding the variables to the environment file, you should just add them with the same name on the AWS Secrets Manager and Intel Owl will fetch them transparently.
211+
First you need to set the environment variable `AWS_SECRETS` to `True` to enable this mode.
212212

213-
Obviously, you should have created and managed the permissions in AWS in advance and accordingly to your infrastructure requirements.
213+
Then, instead of adding the variables to the environment file, you should just add them with the same name on the AWS Secrets Manager and Intel Owl will fetch them transparently.
214214

215-
Also, you need to set the environment variable `AWS_SECRETS` to `True` to enable this mode.
215+
Beware! Any left environment variable would be prioritized. So, you want to use your secrets in AWS, make sure to have removed the related environment variables locally.
216+
217+
Obviously, you should also have created and managed the permissions in AWS in advance and accordingly to your infrastructure requirements.
216218

217219
#### NFS
218220

0 commit comments

Comments
 (0)