Skip to content

Commit 1edbbe4

Browse files
committed
update policy for user
1 parent d109a42 commit 1edbbe4

File tree

1 file changed

+3
-9
lines changed

1 file changed

+3
-9
lines changed

README.md

+3-9
Original file line numberDiff line numberDiff line change
@@ -122,15 +122,9 @@ kept in the `application-prod.yml` file.
122122
### User credentials
123123

124124
Before getting started, it's important to note that an IAM user, who's credentials will be used,
125-
needs to be created with the following policies:
126-
127-
- AmazonS3FullAccess
128-
- AWSLambda_FullAccess
129-
- AmazonDynamoDBFullAccess
130-
- AmazonSNSFullAccess
131-
- AmazonSQSFullAccess
132-
- AWSLambdaExecute
133-
- AmazonS3ObjectLambdaExecutionRolePolicy
125+
needs to be created with the `AdministratorAccess` policy. Of course, working in a company will have more restrictive and fine-grained
126+
permissions defined, for allowing the creation/update of each individual resource. In this case, we will choose an umbrella policy, that
127+
covers all our needs.
134128

135129
For simplicity, we chose to use full access to all the services, so we don't have to add new permissions later on.
136130
We will be using the user's credentials and export them as temporary environment variables with the

0 commit comments

Comments
 (0)