Role is not attaching or available for use after creation for Container Services
For container instances to receive the new ARN and resource ID format, the root user needs to opt in for the container instance IAM role.
I've made a role that should have the right permissions, but** I can't find how to attach it to admin/root.** Step 10 here - The formatting doesn't work in both PowerShell and CLI.
The role is made, but it's also** not showing up in the drop down under** 'Container instance IAM role'.
aha, please try the following:
{
"Version": "2008-10-17",
"Statement": [
{
"Sid": "",
"Effect": "Allow",
"Principal": {
"Service": "ecs.amazonaws.com"
},
"Action": "sts:AssumeRole"
}
]
}
This is probably why you dont see the role under ECS.
Have you swapped EC2 with ecs? This is the key difference
Can you paste the trust policy of the IAM Role that you created for the ECS service?
{ "Version": "2008-10-17", "Statement": [ { "Sid": "", "Effect": "Allow", "Principal": { "Service": "ec2.amazonaws.com" }, "Action": "sts:AssumeRole" } ] }
Relevant questions
Which role do I have to use for the Fargate tasks on AWS Batch?
Accepted Answerasked 6 months agoThe "new" Amazon ECS Console is missing fundamental options like container command overrides
asked 5 months agoHow to access container from another container
asked 9 months agoECS Container not recognizing EC2 instances after updating AMI
asked 3 years agoEnable awsvpctrunking at container instance level
asked 3 years agoRole is not attaching or available for use after creation for Container Services
asked 18 days agoWhat is the storage limit for the AWS Lightsail container service?
asked 6 months agoUnable to get secret for login to external private Container Registry
asked 2 years agowhen to use ECR in lambda ?
asked 2 months agoLightsail: can't upgrade to large container
asked a day ago
It still isn't working; It's the same code (I haven't figured out the inline code block so the formatting is like...that.