Mastodon on AWS - CloudFormation Stack Failing

[Modaffinity]

Hi Andreas,

During the CloudFormation stack deployment, I encountered the following issue:

• The Bucket stack fails because CloudFrontOriginAccessIdentity cannot be created.
• The failing resource refers to external templates stored in:
  • bucket.yml
  • cloudfront.yml
• However, when I try to access these files at
  • https://s3.eu-central-1.amazonaws.com/mastodon-on-aws-cloudformation/latest/bucket.yml
  • https://s3.eu-central-1.amazonaws.com/mastodon-on-aws-cloudformation/latest/cloudfront.yml I received an Access Denied (403) error.

Steps Taken to Troubleshoot:

• Confirmed that the S3 bucket is referenced in quickstart.yml for nested stacks.
• Tried manually downloading bucket.yml and cloudfront.yml but received "AccessDenied" errors.
• Verified my AWS CLI credentials – I have the necessary permissions for other AWS actions, but I lack permissions for the referenced S3 bucket.
• Confirmed that the stack failure is caused by missing templates from mastodon-on-aws-cloudformation.

Thank you for your work on making Mastodon deployment easier!

[andreaswittig]

@Modaffinity What's the URL of the template you use to deploy the main stack?

Are you following our installation instructions and create the stack by clicking on the quick start link?