Skip to content

Recommend tighter AWS IAM policy to access S3 #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Recommend tighter AWS IAM policy to access S3 #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 25 additions & 1 deletion onpremises/07-data-storage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,31 @@ Alternatively, Amazon Web Services S3 (or an S3 compatible service) can be used
The basic steps to configure S3 are:

- Create a bucket under your AWS account (folders named `workspaces` and `reviews` will be created in this bucket).
- Create a new programmatic access user in AWS, with the following permissions: `AmazonS3FullAccess`.
- Create a new programmatic access user in AWS, with the following IAM policy - make sure to replace the bucket name:
```
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:Get*",
"s3:List*"
],
"Resource": "arn:aws:s3:::BUCKET_NAME"
},
{
"Effect": "Allow",
"NotAction": [
"s3:CreateBucket",
"s3:DeleteBucket"
],
"Resource": "arn:aws:s3:::BUCKET_NAME/*"
}
]
}
```

- Modify your `structurizr.properties` file to configure AWS S3 integration as follows:

| Property name | Property value |
Expand Down