This configuration is suitable for production environments
NAT Gateways, public, database,intra and Private subnets will be created in each availability zone. Additionally by default, an EC2 instance which will act as a VPN server will be created.
To run this example you need to execute:
$ terraform init
$ terraform plan
$ terraform applyNote that this example may create resources which can cost money (AWS Elastic IP, for example). Run terraform destroy when you don't need these resources.
No requirements.
| Name | Version |
|---|---|
| aws | n/a |
| Name | Source | Version |
|---|---|---|
| key_pair_vpn | squareops/keypair/aws | 1.0.2 |
| kms | terraform-aws-modules/kms/aws | 3.1.0 |
| vpc | squareops/vpc/aws | 3.3.5 |
| Name | Type |
|---|---|
| aws_caller_identity.current | data source |
No inputs.
| Name | Description |
|---|---|
| database_subnets | List of IDs of database subnets |
| intra_subnets | List of IDs of Intra subnets |
| private_subnets | List of IDs of private subnets |
| public_subnets | List of IDs of public subnets |
| region | AWS Region |
| vpc_cidr_block | AWS Region |
| vpc_id | The ID of the VPC |
| vpn_host_public_ip | IP Adress of VPN Server |
| vpn_security_group | Security Group ID of VPN Server |