Build failed: The bucket policy is either missing or has insufficient permissions for this operation

Ok - found my simple issue.. (hangs head in embarassment...) Somehow my index.html file had a capital I. Changed this to a lower case, and everything started working!

I've re-tested this scenario and can confirm it is definately the case - so the failure message is certainly misleading! Hope this helps!

I'm getting exactly the same issue.

I can see that the Amplify has self generated the Bucket Policy - but clearly it's not sufficent in order to allow it the requried access (or the error message is misleading!)

Thank you for this tip. I was trying to deploy a very simply 'site' by following the guide at https://docs.aws.amazon.com/AmazonS3/latest/userguide/website-hosting-amplify.html Sites don't come much simpler than mine - it's just to host customers' BIMI certificates, MTA-STS text files, etc. Every time I created an 'app' and hit deploy I got the failed rocket page. Adding a dummy index.html to each folder I was using as the S3 bucket root resolved the issues with the deployment failing. I now have a couple of successful sites with custom domains in production. Thank you again, Darren.

The issue you're experiencing with the build failure despite following the blog post steps is likely due to insufficient permissions in the bucket policy. While a policy was created on the S3 bucket, it appears to be missing some crucial permissions that Amplify Hosting requires to deploy your static website successfully.

The current policy allows Amplify to list the bucket contents and read objects, but it doesn't explicitly grant permissions to write or modify objects in the bucket. For Amplify Hosting to deploy your static website, it needs additional permissions, particularly the ability to put objects into the bucket.

To resolve this issue, you should modify the bucket policy to include the necessary permissions for Amplify Hosting. Specifically, you need to add a statement that allows the s3:PutObject action. Here's an example of an additional statement you could add to your bucket policy:

{ "Sid": "AllowAmplifyToPutObjects", "Effect": "Allow", "Principal": { "Service": "amplify.amazonaws.com" }, "Action": "s3:PutObject", "Resource": "arn:aws:s3:::<<BUCKET>>/*", "Condition": { "StringEquals": { "aws:SourceArn": "arn:aws:amplify:ap-southeast-2:<<ACCOUNT_ID>>:apps/<<APP_ID>>/branches/staging", "aws:SourceAccount": "<<ACCOUNT_ID>>" } } }

After adding this statement to your bucket policy, try redeploying your Amplify app. This should grant Amplify the necessary permissions to write files to your S3 bucket during the deployment process.

If you continue to experience issues, you may need to review the Amplify app settings and ensure that the S3 bucket location is correctly specified. Additionally, verify that the IAM role associated with your Amplify app has the required permissions to interact with the S3 bucket.
Sources
Simplify and enhance Amazon S3 static website hosting with AWS Amplify Hosting | AWS News Blog
Deploying a static website to AWS Amplify Hosting from an S3 general purpose bucket - Amazon Simple Storage Service