ECS, AutoScaling: public clusters not being registered

Note: for support questions, please first reference our documentation, then use Stackoverflow. This repository’s issues are intended for feature requests and bug reports.

• I’m submitting a …

  • 🪲 bug report
  • 🚀 feature request
  • 📚 construct library gap
  • ☎️ security issue or vulnerability => Please see policy
  • ❓ support request => Please see note at the top of this template.

• What is the current behavior? If the current behavior is a 🪲bug🪲: Please provide the steps to reproduce I would like to deploy the following public ECS cluster, with an IP address associated with the instances:

const vpc = new Vpc(this, "vpc", {
  cidr: "10.0.0.0/16",
  natGateways: 0,
  subnetConfiguration: [
    { cidrMask: 24, name: "ingress", subnetType: SubnetType.PUBLIC }
  ]
});

const cluster = new Cluster(this, "cluster", { vpc });

const scalingGroup = cluster.addCapacity("scalingGroup", {
  desiredCapacity: 1,
  instanceType,
  spotPrice,
  associatePublicIpAddress: true,
  machineImage: EcsOptimizedImage.amazonLinux2(),
  vpcSubnets: {
    onePerAz: true,
    subnetType: SubnetType.PUBLIC
  },
});

The stack is deployed and I have an instance started in my ASG. However, no container instances are associated to my ECS cluster. The problem disappears when I switch a classic public/private VPC with a NAT Gateway.

I haven’t pinpointed where the issue is, whether the CloudFormation that is being generated in invalid, or if what I want is unavailable.

• What is the expected behavior (or behavior of feature suggested)? Fix that behavior if it is supported by AWS, otherwise prevent setting associatePublicIpAddress in ECS clusters.

• What is the motivation / use case for changing the behavior or adding this feature? Fix this use case, or clarify it’s impossibility

• Please tell us about your environment:

  • CDK CLI Version: 1.3.0
  • Module Version: 1.3.0
  • OS: all
  • Language: all

• Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc)

[nmussy]

@SomayaB Thanks for the reminder, I’ll check it out

[SomayaB]

@nmussy Did you ever get a chance to get back to this?