This message was deleted.
# aws
s
This message was deleted.
b
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
A good practice is to have a separate, distinct project that manages service linked roles
c
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:
Copy code
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
b
that's good practice, and one I follow myself
👍 1