mike/feat-TELEMTRAF-7944: add arm-supporting AZ VPC export#48
Merged
michael-mbox merged 1 commit intomasterfrom May 5, 2026
Merged
Conversation
ryndaniels
approved these changes
May 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a new
DefaultVpcoutput property:FargateArm64PrivateSubnets.This output is an array of private subnet IDs from the default VPC, excluding physical availability zones where AWS Fargate ARM64 is not supported. Today the known unsupported case is
use1-az3inus-east-1, per AWS ECS ARM64 documentation.This does not change any existing
DefaultVpcoutputs such asPrivateSubnets,PublicSubnets,AzIndexedPrivateSubnets, orAzIndexedPublicSubnets. Existing stacks will continue to receive the same attributes they use today; this PR only adds a new attribute for stacks that explicitly opt into it.Why
live-traffic-engineis migrating Fargate tasks to ARM64 for cost savings. Its legacy CloudFormation/cloudfriend service stack currently uses the sharedvpc-private-subnetsexport, which includessubnet-276c8319(us-east-1c/ physical AZuse1-az3). Fargate ARM64 does not supportuse1-az3, so ARM64 task placement needs a private subnet set that excludes that AZ while preserving multi-AZ placement.CDK consumers can filter subnets by AZ, but cloudfriend/raw CFN stacks need either hardcoded subnet IDs or a custom-resource/exported value. This adds a reusable custom-resource attribute so LTE and similar legacy CFN stacks can avoid hardcoding subnet IDs.
Usage example
A CloudFormation/cloudfriend stack can define the existing custom resource:
Then use the new attribute for Fargate ARM64 subnet placement:
For LTE in
us-east-1, this should resolve to the ARM-safe private subnet set equivalent to A/D/E, excluding the private subnet inuse1-az3.Testing
test/default-vpc.test.jsto verifyFargateArm64PrivateSubnetsexcludes a private subnet withAvailabilityZoneId: use1-az3while preserving existing DefaultVpc outputs.