Skip to content

vpc: PRIVATE_WITH_EGRESS not getting applied with route to TransitGateway #25626

@bruecktech

Description

@bruecktech

Describe the bug

When I do Vpc.fromLookup in a VPC that has subnets with a default route to a TransitGateway the subnet is detected as PRIVATE_ISOLATED instead of PRIVATE_WITH_EGRESS

This PR that introduced it talks about TransitGateway too but it doesn't seem to get applied.

Expected Behavior

Detect subnet with a default route to a TransitGateway as PRIVATE_WITH_EGRESS

Current Behavior

Subnets with a default route to a TransitGateway are detected as PRIVATE_ISOLATED

Reproduction Steps

Use Vpc.fromLookup in a VPC that has subnets with a default route to a TransitGateway

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.66

Framework Version

No response

Node.js Version

16.16

OS

MacOS

Language

Typescript

Language Version

No response

Other information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    @aws-cdk/aws-ec2Related to Amazon Elastic Compute CloudbugThis issue is a bug.effort/mediumMedium work item – several days of effortp1

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions