Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Enable users to provide custom VPC subnets in CDK context

Description

Recently a customer opened a Github issue #1430 where they deployed MA in their existing VPC by providing a VpcId field in their cdk.context.json and failed with an error.

Error Message:


Reason for failure:

  • AWS ECS (Fargate) has a hard limit of 16 subnets per service.

  • Current behavior of CDK with existing VPC is to deploy services on all available private subnets (for the customer, this number exceeded 16, hence error)

Acceptance Criteria

  • If users want to use their existing VPC, users should be able to specify a list of subnets with SubnetId on which they want to deploy MA, within their cdk.context.json

  • All service stacks for Migration Assistant’s components should also get deployed only within these provided subnets.

Environment

None

Activity

Pro tip: press M to comment
Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Approvers

Tanner Lewis

Story Points

Sprint

Fix versions

Priority

Parent

Created April 7, 2025 at 11:32 PM
Updated April 16, 2025 at 2:08 AM
Resolved April 16, 2025 at 2:08 AM