This message was deleted.

sparse-intern-71089

02/27/2019, 12:13 PM

This message was deleted.

white-balloon-205

02/27/2019, 4:59 PM

Indeed! This is a really unfortunate ECS limitation. See (and vote on) https://github.com/aws/containers-roadmap/issues/104.

busy-daybreak-68237

02/28/2019, 12:49 PM

Ugh, ah well.

busy-daybreak-68237

02/28/2019, 12:51 PM

What would you recommend for a single container that needs to have one internet-facing port and one private?

busy-daybreak-68237

02/28/2019, 12:52 PM

Is it possible to use Pulumi to manage containers on a regular EC2 instance?

white-balloon-205

02/28/2019, 5:25 PM

Fargate can handle that - you just can't put load balancers on both. The

cloud.Service

abstraction currently puts load balancers on all exposed ports, so you wouldn't be able to use that. But the

awsx.ecs.FargateService

abstraction is meant exactly for this - and should handle your case without problem. See https://github.com/pulumi/pulumi-awsx/tree/master/nodejs/awsx/ecs.

busy-daybreak-68237

03/01/2019, 11:38 AM

Thanks, looks perfect

busy-daybreak-68237

03/01/2019, 11:39 AM

Is there a way to discover the internal DNS name for the fargate service? So services within the VPC can connect?

Open in Slack

Previous Next

Pulumi Community

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.