1 Answer
- Newest
- Most votes
- Most comments
0
I figured out the 2 permissions needed to get past this error, I created the policy below and attached it to the Code Deploy role:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"iam:PassRole",
"ec2:RunInstances"
],
"Resource": "*"
}
]
}
Edited by: mguignard on Jan 22, 2019 4:38 AM
answered 5 years ago
Relevant content
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago
- What's the difference between Lambda function execution role permissions and invocation permissions?AWS OFFICIALUpdated 2 years ago