aws_ec2: assigning of public IP is not disabled

[IllarionovDimitri]

Describe the bug

I want to deploy ec2 instance into public subnet but disable the assignment of public IP.

Since the instances are part of ASG first I tried with

aws_autoscaling.AutoScalingGroup(
    self,
    ...
    associate_public_ip_address=False
    ...
)

But since I define ASG via mixed_instances_policy and launch_template props, I got an error

RuntimeError: Setting 'associatePublicIpAddress' must not be set when 'launchTemplate' or 'mixedInstancesPolicy' is set

There is no prop in ec2.LaunchTemplate to disable the public ip, so I went to the subnet configuration

ec2.SubnetConfiguration(
            name=f"{config.ID}-public",
            subnet_type=ec2.SubnetType.PUBLIC,
            map_public_ip_on_launch=False,
            cidr_mask=24,
        )

After I've re-deployed the stack, Auto-assign public IPv4 address was still set to Yes and the instance was assigned the public IP.

Expected Behavior

1. Setting of map_public_ip_on_launch=False disables auto assignment of public IPs
2. If it is not possible to use associate_public_ip_address in aws_autoscaling.AutoScalingGroup, the property should be available in launch template.

Current Behavior

See section "Describe the bug"

Reproduction Steps

EC2 instance must be deployed in the public subnet, where subnet setting defined as follows

ec2.SubnetConfiguration(
            name=f"{config.ID}-public",
            subnet_type=ec2.SubnetType.PUBLIC,
            map_public_ip_on_launch=False,
            cidr_mask=24,
        )

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.85.0

Framework Version

No response

Node.js Version

18

OS

Ubuntu 20.04

Language

Python

Language Version

3.10.6

Other information

No response

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[lenfree]

Any updates on this?

[IllarionovDimitri]

not an issue, works fine. was re-deploying the wrong stack, therefore closed this issue