<@UHTP242EB> You replied to my message on GitHub a...
# aws
q
@broad-dog-22463 You replied to my message on GitHub about awsx and
ephemeralStorage
. I have updated to
@pulumi/awsx:1.0.0-beta.7
so that I can try to leverage support for ephemeral storage. I'm running into an issue when provisioning:
Copy code
error: Error: invocation of aws:ec2/getVpc:getVpc returned an error: invoking aws:ec2/getVpc:getVpc: 1 error occurred:
        * no matching EC2 VPC found

// snipped

Error: failed to register new resource REDACTED [awsx:ecs:FargateService]: 2 UNKNOWN: invocation of aws:ec2/getVpc:getVpc returned an error: invoking aws:ec2/getVpc:getVpc: 1 error occurred:
        * no matching EC2 VPC found
Neither one of
awsx.ecs.FargateService
or
aws.ecs.Cluster
can receive a
vpc
property.
b
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
q
The service I'm trying to deploy doesn't have an lb
I can't really share the code
I'm creating a
awsx.ecs.FargateTaskDefinition
,
awsx.ecs.FargateService
and attaching a classic
awsx.ecs.Cluster
via
arn
b
Ok so your cluster should have the correct network config passed to it right?
q
Yes, but it's a
awsx/classic
ecs.Cluster
So it takes a
vpc
property, and that's always been fine
b
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
q
Could the issue be that I'm using
cluster.cluster.arn
?
b
Should not matter… let me see what I can try here :)
Give me a bit of time to try it
So it's classic vpc and classic ecs cluster with new fargate cluster right?
q
Yep thats right. I should probably mention I'm using
Vpc.fromExistingIds
b
Interesting! But that'll help me try and isolate the issue
q
All good I'm finishing work now
👍 1
b
I'll leave info in this thread :)
❤️ 1
q
Thank you
Stepping back into work. Did you have any luck here?
Following up again. Any update?