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.

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

Jump to bottom

Public access now blocked by default for new S3 buckets #2

Closed
guillerodriguez opened this issue Jun 12, 2023 · 6 comments
Closed

Public access now blocked by default for new S3 buckets #2

guillerodriguez opened this issue Jun 12, 2023 · 6 comments

Comments

@guillerodriguez
Copy link
Collaborator

Starting April 2023, Amazon has changed the default configuration for new S3 buckets and now "S3 Block Public Access" is enabled by default: https://aws.amazon.com/es/blogs/aws/heads-up-amazon-s3-security-changes-are-coming-in-april-of-2023/

For new S3 buckets that will be used to host a website, it is necessary to modify this setting.

Configuration of the S3 bucket is actually handled by the configure-s3-website gem. I opened an issue in the upstream repo, but the author informed me that the gem is no longer maintained.

So in order to fix this I understand that you would first need to fork configure-s3-website and modify s3_website_revived's gemspec file to use the forked gem. Then the forked gem can be patched to fix the issue.

Do you agree with this?

If so, I can help preparing a PR once the configure-s3-website gem is forked.

Please let me know if this sounds ok to you.
@ivoanjo
Copy link
Owner

ivoanjo commented Jun 12, 2023

👋 nice to meet you Guillermo!

To be honest, I never used the configure-s3-website bits -- I did my own setup and then used s3website just for the uploady bits, so I'm not sure I'm the best warden for it :)

Can I convince you to fork it yourself, and I'll link to your version of the gem from s3_website_revived? 😉

If not, that's fine, and I'm still up for going with your initial suggestion.

@guillerodriguez
Copy link
Collaborator Author

Yes, sure! I will get back to you.

@guillerodriguez
Copy link
Collaborator Author

Sorry for the delay, here's an updated gem that fixes the mentioned issue: https://rubygems.org/gems/configure-s3-website-ng

Sources: https://github.com/ingelabs/configure-s3-website

@ivoanjo
Copy link
Owner

ivoanjo commented Jul 12, 2023

Awesome! I'm a bit busy over the next few days, but I'll update the dependency as soon as things calm down a bit :)

ivoanjo added a commit that referenced this issue Jul 23, 2023
@ivoanjo
Replace abandoned configure-s3-website gem with `configure-s3-websi…
ed6d682 
…te-ng` fork

Thanks @guillerodriguez for the awesome work!

Issue #2
@ivoanjo
Copy link
Owner

ivoanjo commented Jul 23, 2023

@guillerodriguez Thanks a lot! I finally had a bit of time today, and I've:

  1. Adopted your new gem as a dependency
  2. Put out a new release (4.0.2) using it
  3. Sent you an invite to collaborate on this repo, since like me you seem to be interested in helping keep this tiny useful gem alive :)

@ivoanjo ivoanjo closed this as completed Jul 23, 2023
@guillerodriguez
Copy link
Collaborator Author

Great! Thank you ☺️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@guillerodriguez @ivoanjo