This message was deleted.

I assume you are basing your code on this: https://www.pulumi.com/docs/guides/crosswalk/aws/ecs/#using-an-existing-ecs-cluster?

that’s correct. Even when I do it that way, it creates a few security groups + rules

And the security groups it creates are no good in some way? The opinionated nature of awsx means it will create resources it needs to provide the lower-friction experience. If those security groups are problematic, then you’ll want to use the base

aws

provider and for reusability purposes, probably do so with a custom resource based on

aws

that sets things up the way you want them to be set up.

Yeah, I think it was a mistake to use

awsx

if I already had an existing cluster that was created by

aws

. But I would have expected

.get()

not to modify the existing cluster config. Though it makes sense why it does that…