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

Make S3 bucket public in integration #101

Closed
chrisroos opened this issue Jul 31, 2017 · 5 comments
Closed

Make S3 bucket public in integration #101

chrisroos opened this issue Jul 31, 2017 · 5 comments
Assignees

Comments

@chrisroos
Copy link
Contributor

chrisroos commented Jul 31, 2017

We'll need to do this in order to serve assets directly from S3.

@chrisroos chrisroos added this to the Serve assets directly from S3 milestone Jul 31, 2017
@floehopper floehopper self-assigned this Aug 3, 2017
@floehopper
Copy link
Contributor

I think this is simply a matter of changing the acl argument on the bucket from "private" to "public-read". See the documentation for Terraform's aws_s3_bucket resource and S3 canned ACLs.

@floehopper
Copy link
Contributor

@chrisroos
Copy link
Contributor Author

We've made and merged the necessary change in alphagov/govuk-terraform-provisioning#130. We're currently waiting for this change to be deployed to integration.

@chrisroos chrisroos changed the title Make S3 bucket public Make S3 bucket public in integration Aug 9, 2017
@chrisroos
Copy link
Contributor Author

The changes in alphagov/govuk-terraform-provisioning#130 have now been deployed to integration.

I've tested that the change is working as expected by uploading an attachment to a Manual Section (in Manuals Publisher) and requesting the uploaded asset with the redirect_to_s3=true querystring.

@floehopper
Copy link
Contributor

Based on @chrisroos' last comment, I'm closing this issue. @chrisroos: Please re-open if you think we've missed anything.

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

No branches or pull requests

2 participants