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

s3 bucket no longer made public by deploy #59

Open
sterling000 opened this issue Jul 29, 2020 · 1 comment
Open

s3 bucket no longer made public by deploy #59

sterling000 opened this issue Jul 29, 2020 · 1 comment

Comments

@sterling000
Copy link

sterling000 commented Jul 29, 2020

My vue-starter project no longer gives public read access to the access bucket when it's deployed, I have to manually make everything in the bucket public after every deploy.

Here are the steps I took to get into this state.

  1. Create a new project from the vue-starter template
  2. Run "sls" from the command line to deploy the website
  3. Open the serverless.yml and add a bucketName and domain that match.
  4. Change the app: vue-starter and the name: vue-starter to a new value
  5. Run "sls" again. Observe error that the bucket already exists for a different app and you should remove it first and redeploy.
  6. Stash the changes to the yml, and run "sls remove"
  7. Unstash your changes again and run "sls"
  8. Log into s3 and Observe that all the files in the bucket no longer have Read permissions for the Everyone group.
  9. Manually use the "Make Public" action in s3 to make everything available to the public.
  10. Run "sls" again to redeploy
  11. Refresh your website and see the 403 errors again, confirming in s3 that the files are no longer public again.
@wylie39
Copy link

wylie39 commented Jun 13, 2022

Has anyone found a fix for this?

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