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

hey, sorry for the delay. in a lot of examples we don't add the service linked roles because they usually exist in the account. If you're using a brand new account, they may not exist

<https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html>

A good practice is to have a separate, distinct project that manages service linked roles

hey Jaxx, thanks for getting back to me.. ok thank you for that info - i was just about to come back and update this thread. I 'solved' it by creating it in my stack:

```        var ecsServiceLinkedRole = new ServiceLinkedRole("ecsServiceLinkedRole", new ServiceLinkedRoleArgs
        {
            AwsServiceName = "<http://ecs.amazonaws.com|ecs.amazonaws.com>",
        });```
but i'll take your advice on board and look to set up a separate project.. i'm thinking that for things like the VPC and subnet, they should prob be in a separate project too

that's good practice, and one I follow myself