Skip to content
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.

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

AWS Cross Account S3 Buckets #233

Open
gugacavalieri opened this issue Oct 20, 2022 · 2 comments · May be fixed by #240
Open

AWS Cross Account S3 Buckets #233

gugacavalieri opened this issue Oct 20, 2022 · 2 comments · May be fixed by #240

Comments

@gugacavalieri
Copy link

gugacavalieri commented Oct 20, 2022

First of all, congrats for the project. It's awesome how fast it runs and how simple is to setup everything!

I think this actually broke AWS Cross account functionality (PR: #212). I am trying to store the dumps on a S3 bucket in another account.

When you use list_buckets the S3 Client won't return the buckets from another account. Do you remember why get_bucket_accelerate_configuration was breaking at first place?

Also the list_buckets operation requires s3:ListAllMyBuckets on the s3:* account level not on a bucket level so maybe switching to the list_bucket operation to list the files inside of a S3 bucket would also improve the security in terms of policy.

Let me know how I can help!

PS. Just tested with v0.9.6 and I am able to write/access the dumps to a S3 bucket in another account.

@gugacavalieri gugacavalieri changed the title Bug: AWS Cross Account S3 Buckets AWS Cross Account S3 Buckets Oct 21, 2022
@evoxmusic
Copy link
Contributor

Hi @gugacavalieri , since I don't have so much time those days. Do you think you can provide a fix? Thank you for your help

@gugacavalieri
Copy link
Author

Hi @evoxmusic. Sure, I will try to get a fix in the next weeks and let you know! Glad to help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants