add cross-account for CopyObject #9806
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bentsku
added
aws:s3
macnev2013
approved these changes
Dec 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
As reported here: https://discuss.localstack.cloud/t/nosuchbucket-error-when-copying-file/640
The user had an issue where the bucket was created by another account, and he would then try to call
CopyObjecton it.I don't really have the setup for testing multi-account against AWS, but it feels like as S3 buckets are global, this should be possible and only a matter of IAM permission / ACL.
https://docs.aws.amazon.com/AmazonS3/latest/API/API_CopyObject.html
Changes
CopyObjectuse cross-account access while getting the S3 buckets