This message was deleted.

This is how I’m exporting the id from the first stack:

const cluster = new awsx.ecs.Cluster(...);

export const clusterId = cluster.id;

Take a look at Stack references: https://www.pulumi.com/docs/intro/concepts/stack/#stackreferences This means you can access the outputs from one stack in another

I’m already using

StackReference

. This is how I’m importing the id and trying to create an ECS FargateService:

const services = new pulumi.StackReference("stack");
const clusterId = services.getOutput("clusterId");
const cluster = aws.ecs.Cluster.get("name", clusterId);

const server = new awsx.ecs.FargateService("resourceName", {
  cluster, // This doesn't work
});

That's what I mean. They're not interchangeable.

Got it, thanks! do I need to switch to using the AWS core package in this case? Is there an easier way to accomplish the same result? I tried to search for a cluster method in AWSX similar to the one for

awsx.ec2.Vpc

fromExistingIds that returns

Vpc

of type AWSX, but couldn’t find something similar for the cluster

do I need to switch to using the AWS core package in this case?

Sorry to say this, but "it depends". There are some cases where it's going to be fine to use AWSX - like if you're using it all within the same stack, if you're not building anything particularly complicated etc and if you can stay within the resources that the package provides.

I guess in our case we need to use AWS core package for some resources (resources that need the above cluster). Thanks again!

Have you tried cluster.arn instead of cluster.id?

No, what will be the advantage in this case? creating a fargate service in AWSX requires passing the entire cluster not only the id/arn

Was thinking about this last night. Since this is just a typescript object, you could create the object yourself and pass it in

hmm, that’s a good idea, but I don’t think this would work because cluster properties are read-only so I can’t do something like this:

const cluster = aws.ecs.Cluster.get(`${stackName}-cluster`, config.appClusterId);

const appCluster: awsx.ecs.Cluster;
appCluster.id = cluster.id;

But you could do something like:

const cluster = aws.ecs.Cluster.get(`${stackName}-cluster`, config.appClusterId);

let appCluster = {
    id: cluster.id
    ...
}

It's the shape that's important (or at least that's my understanding)

Thanks again! I think this should work but it requires filling out other properties like security groups that need to be exported from the first stack. Back to your first point, luckily, I found out that I only need to replace two resources to use the AWS core package instead of AWSX and i’m not seeing any issue with this approach so far. So, I think I will go with it

I would advise going with the base provider rather than AWSX in this case, but you know how to move on if you wanted to use AWSX