2 Answers
- Newest
- Most votes
- Most comments
0
Hi,
The error looks similar to the following problem reported by another user a few days ago. Can you check if the solution is also useful for you? If not, can you provide us with more information?
0
Earlier Elastic Beanstalk used to create a default EC2 instance profile named aws-elasticbeanstalk-ec2-role the first time an AWS account created an environment. However, recent AWS security guidelines don’t allow an AWS service to automatically create roles with trust policies to other AWS services, EC2 in this case. Please check this detailed answer on StackOverflow to fix the issue - https://stackoverflow.com/a/76620598/12326605
answered 3 years ago
Relevant content
- AWS OFFICIALUpdated 2 years ago
