New AMI on t3 fails Opsworks launch

0

I created a new AMI based on a t3 running the latest Amazon Linux 2.

After creating a new instance in my Opsware stack that uses it, it's stuck in Booting for about 10 minutes before it fails.

When I look in /var/log/aws/opsworks, I see that it failed with: downloader: [ERROR] File size test failed. HTTP/1.1 403 Forbidden url: https://opsworks-instance-assets-us-west-2.s3.amazonaws.com/packages/amazon/2/opsworks-agent-ruby-2.0.0-p481-1.x86_64.rpm

Any ideas about what I did wrong? Did I miss a step for it to use the Opsworks agent? Thanks!

asked 2 years ago104 views
No Answers

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions