No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Sorry for the trouble!  Per <https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using-service-linked-roles.html#create-service-linked-role>, I believe this shouldn't happen unless the IAM user you were deploying with doesn't have sufficient permissions.  Per those same docs, could you try running `aws iam create-service-linked-role --aws-service-name <http://ecs.amazonaws.com|ecs.amazonaws.com>` and see if that unblocks things?