Skip to content

ExistingVPCDeployment.md

Latest commit

 

History

History
42 lines (30 loc) · 2.35 KB

ExistingVPCDeployment.md

File metadata and controls

42 lines (30 loc) · 2.35 KB

Existing VPC Deployment Guide

CDK Deployment for Existing VPC

This section outlines the steps to deploy the application with a Pre-existing VPC. If you do not have an existing VPC, proceed to 3b: CDK Deployment in the Deployment Guide.

Prerequisites

Ensure you have access to the aws-controltower-VPC and the name of your AWSControlTowerStackSet.

Step-by-Step Instructions

  1. Modify the VPC Stack:

    • Navigate to the vpc-stack.ts file located at cdk/lib/vpc-stack.ts.

    • Replace line 13 with your existing VPC ID:

      const existingVpcId: string = 'your-vpc-id'; //CHANGE IF DEPLOYING WITH EXISTING VPC

      You can find your VPC ID by navigating to the VPC dashboard in the AWS Management Console and locating the VPC in the Your VPCs section.

      VPC ID Image

  2. Update the AWS Control Tower Stack Set:

    • Replace line 21 with your AWS Control Tower Stack Set name:

      const AWSControlTowerStackSet = "your-stackset-name"; //CHANGE TO YOUR CONTROL TOWER STACK SET

      You can find this name by navigating to the CloudFormation dashboard in AWS, under Stacks. Look for a stack name that starts with StackSet-AWSControlTowerBP-VPC-ACCOUNT-FACTORY.

      AWS Control Tower Stack Image

Deployment Changes

In this deployment, the following have been modified:

  • VPC Identification: Instead of creating a new VPC, an existing VPC is now utilized by passing its ID into the VpcStack configuration.
  • Private and Isolated Subnets: Private and isolated subnet IDs and their associated route table IDs are imported using AWS Control Tower.
  • Interface Endpoints: Multiple AWS service endpoints (SSM, Secrets Manager, RDS, Glue) are added within isolated subnets to maintain secure access with existing VPC.
  • Public Subnet and Internet Gateway: A public subnet and an internet gateway are created, which are essential for NAT Gateway operations.
  • NAT Gateway: A NAT gateway is created in the public subnet.
  • Private Subnet Route Tables: For each private subnet's route table, a route to the NAT gateway is added to provide internet access to resources in private subnets

These changes ensure the application seamlessly integrates into the existing VPC.