By using AWS re:Post, you agree to the Terms of Use
/Role is not attaching or available for use after creation for Container Services/

Role is not attaching or available for use after creation for Container Services

0

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'.

2 Answers
0

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.

answered 13 days 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.

  • Have you swapped EC2 with ecs? This is the key difference

0

Can you paste the trust policy of the IAM Role that you created for the ECS service?

answered 13 days ago
  • { "Version": "2008-10-17", "Statement": [ { "Sid": "", "Effect": "Allow", "Principal": { "Service": "ec2.amazonaws.com" }, "Action": "sts:AssumeRole" } ] }

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