## Description This architecture allows you to create an AWS networking landing zone including VPC, subnets, route tables in different availability zones. It accepts incoming traffic from internet through the internet gateway and route it to the subnets. **N.B:** - The Terraform code is automatically generated with best practices and contains variables that you can customize to fir your needs. - You have full control to change, add, delete resources or their configuration. The newly generated code will reflect these changes. - You can replace some resources with Terraform modules. > terraform apply status: successful ## Architecture components Here are all the components of this architecture: - VPC - Subnets - Internet gateway - Route table and route table associations in every subnet - EIPs - NAT gateways ## Requirements | Name | Configuration | | --- | --- | | Terraform | all versions | | Provider | AWS | | Provider version | >= 5.52.0 | | Access | Admin access | ## How to use the architecture Clone the architecture and modify the following variables according to your needs: | Variable | Description | | --- | --- | | subnets | Public subnets with their configuration | | private_subnets | Private subnets with their configuration | | tags | Tags that are added to all resources | | vpc_cidr | The CIDR of the VPC | **N.B:** - Feel free to remove the resources that are not relevant to your use-case. - Some variables have default values, please change it if it doesn't fit your deployment. ## Maintainer(s) You can reach out to these maintainers if you need help or assistance: - [Brainboard team](mailto:support@brainboard.co)