-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Copying the wildrydes files from s3 fails with access denied #292
Comments
Hi @daiscog - I had the same problem. I resolved it by granting the IAM user that was doing the copy the AmazonS3ReadOnlyAccess policy - this gave the user permission to read from S3. |
Worked for me as well! Thanks |
Adding AmazonS3ReadOnlyAccess policy did not work for me |
@phmohan I had to wait a few minutes after granting the IAM user |
how much wait is required? |
Ok so the solution is a few things:
|
@mtreby worked for me thanks! |
@ranaalisaeed , I have done no2, and it did not work, how can I go about doing no1 Ok so the solution is a few things:
|
I faced same issue and resolved it using IAM. My IAM policies had S3 full access, Cloudshell full access(Since I used AWS CLI) |
Can anyone help me with the below error for the above tutorial: aws s3 cp s3://wildrydes-us-east-1/WebApplication/1_StaticWebHosting/website ./ --recursive |
Thanks that work for me. @aditya-grk try to generate new access keys in the security credentials of your IAM user. |
I had the same issue. It worked for me by adding this Policy. Great job AWS.. absolutely no context left in the description about that. |
@mtreby - worked for me! Thanks |
I've found the "same" tutorial at https://webapp.serverlessworkshops.io/ is more up-to-date. It also pulls from GitHub. |
After doing the following, i still have the same issue. Anyone have any ideas?
My AmazonS3ReadOnlyAccess looks like this: |
as at today 13th February 2024, I still have this issue |
the problem is that the s3 bucketv isn't publicly accessible anymore. in order to find it check it here |
i too got the same access denied error i have granted administrator access. |
create a new repo and start all over again , with the git clone etc process. Also make sure you are in the us-west-2 region this is very important . I had to change my region and created the repo in this region |
did you name the repo you created in the us-west-2 region " wildrydes-site " when I had similar issues, I deleted the repos there, started again and named my repo "wildrydes-site" not " wildrydes-site2 " |
C:\Users\compu\wildrydes-site>git add . |
This's exactly the solution for me. Thanks you! |
Change the remote URL by running: then run git push |
|
it works |
That solved my issue, thanks man! |
You are a savior 🙏 |
Thank you !. you made the journey seamless |
Thank you! Just a bit reminder. the remote repo address is changed to |
Yup, |
As others have stated, you can use @blossom2016 s3 bucket to cp:
You then, if you are working on a repo in a different region, need to reset the git head to your cloned URL, which will be in your region, i.e., as @A-ravi stated, use,
|
please help my wildrydes-site is not deployed . it is showing master "failed ". i have added amplify.yml file in the base directory |
What is showing as master failed? Can you copy+paste the code/log? |
Thank you so much, it works but only when you have created your CodeCommit Repo in the region: us-west-2 |
This worked for me! |
Following the "build a serverless web app" tutorial, and hit two issues in the Copy the files from S3 step in Module 1 - Static Web Hosting with Continuous Deployment.
Firstly, the pre-requisites for the tutorial didn't mention the need to install the aws cli, so I had to go and figure that out (more an annoyance than a blocker, as a quick Google for "aws cli" sorted that).
Then once the CLI is installed, running the
aws s3 cp s3://wildrydes-us-east-1/WebApplication/1_StaticWebHosting/website ./ --recursive
command as instructed results in this error:I assume the target S3 bucket is no longer publicly available...
The text was updated successfully, but these errors were encountered: