too many individual instances failed deployment, too few healthy instances are available for deployment

sunmingtao / sample-code

3 stars 4 forks source link

too many individual instances failed deployment, too few healthy instances are available for deployment #130

Closed sunmingtao closed 4 years ago

sunmingtao commented 4 years ago

Follow https://www.udemy.com/course/aws-certified-developer-associate-dva-c01/learn/lecture/11851340?start=15#overview to learn codeDeploy

Deployment fails with error

"The overall deployment failed because too many individual instances failed deployment, too few healthy instances are available for deployment, or some instances in your deployment group are experiencing problems."

Specifically it fails at step DownloadBundle, errorCode=UnknownError, message=Access Denied

sunmingtao commented 4 years ago

Turns out when creating the role EC2InstanceRoleForCodeDeploy, I mistakenly attached the policy AmazonEC2ReadOnlyAccess to the role, while it should have been AmazonS3ReadOnlyAccess