aws-secure-environment-accelerator icon indicating copy to clipboard operation
aws-secure-environment-accelerator copied to clipboard

[FEATURE] Add support for IPAM as an optional feature in ASEA

Open joeldesaulniers opened this issue 3 years ago • 0 comments

Required Basic Info To properly assess the enhancement request, we require information on the version of the Accelerator you based this request upon:

  • Accelerator Version: latest release

Is your feature request related to a problem? Please describe. No.

Describe the solution you'd like To allow ASEA customers to OPTIONALLY choose to use the IPAM feature we launched in Dec 2021, we need to add IPAM support to ASEA. This includes:

  • adding the capability to define new AWS::EC2::IPAM resources in the ASEA configuration file
  • allocating VPC CIDR ranges from the IPAM-allocated pools (versus the current manually inputed IP ranges)
  • publishing a NEW sample configuration file that defines the IPAM pools in the Shared Network account and allocates CIDR ranges to all of the VPCs throughout ASEA from these pools

Describe alternatives you've considered The alternative to IPAM is to allow customers to continue to use the IP address management solution currently included with ASEA, whereas all of the CIDR ranges are defined and managed in the configuration file and/or in DynamoDB tables.

Additional context Add any other context or screenshots about the feature request here.

joeldesaulniers avatar Jan 25 '22 19:01 joeldesaulniers