Skip to content

ODM-12525 add Cross-account S3 access #120

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

Merged
tropnikovvl merged 2 commits into from
May 8, 2025
Merged

ODM-12525 add Cross-account S3 access #120

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
62f3ccf
feature/ODM-12525 add Cross-account S3 access
tropnikovvl May 8, 2025
ec34439
Update docs/home/clouds/aws.md
tropnikovvl May 8, 2025
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
10 changes: 10 additions & 0 deletions docs/home/clouds/aws.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,6 +123,16 @@

- Be careful when using it, you should limit the list of zones with which it can work. And if the zone is used for something else, then make sure that it will not delete records from there.

## Cross-account S3 access

The approach is based on the [official documentation](https://repost.aws/knowledge-center/cross-account-access-s3) section `IAM policies and resource-based bucket policies`.

If the S3 bucket uses `SSE-KMS` encryption, then it is necessary to additionally grant access to the KMS key in the items below:

- in the `IAM policy` that is attached to the IAM role/user

- in the `Key policy` of the KMS key that is used to encrypt data in the S3 bucket

## Configuration examples

<details><summary>AbortIncompleteMultipartUpload rule</summary>
Expand Down