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 Simon, what does your code look like? The API has changed and now we don't need to pass the VPC we can just pass the network configuration 

You can see some examples <https://github.com/pulumi/pulumi-awsx/tree/master/examples/ts-lb-with-subnets|https://github.com/pulumi/pulumi-awsx/tree/master/examples/ts-lb-with-subnets>

The service I'm trying to deploy doesn't have an lb

I'm creating a `awsx.ecs.FargateTaskDefinition`, `awsx.ecs.FargateService` and attaching a classic  `awsx.ecs.Cluster` via `arn`

Ok so your cluster should have the correct network config passed to it right?

Yes, but it's a `awsx/classic` `ecs.Cluster`

So it takes a `vpc` property, and that's always been fine

So that shouldn't matter to us - we just care about the cluster.arn and then you should be able to nap the correct network config

Could the issue be that I'm using `cluster.cluster.arn`?

Should not matter… let me see what I can try here :)

So it's classic vpc and classic ecs cluster with new fargate cluster right?

Yep thats right. I should probably mention I'm using `Vpc.fromExistingIds`

Interesting! But that'll help me try and isolate the issue

Stepping back into work. Did you have any luck here?