This terraform module allow you create AWS VPC peering connect between two different VPCs.
This example will created VPC Peering from dev to qa VPC.
Note: To use this module you have to have owner and accepter profile name configured in you ~/.aws/credentials and ~/.aws/config
module "vpc_peering_qa" {
source = "git::https://github.com/dmytro-dorofeiev/modules/terraform-aws-vpc-peering-module"
owner_profile = "dev"
accepter_profile = "qa"
owner_vpc_id = var.owner_vpc_id
owner_route_names = ["mgm"]
accepter_vpc_id = var.accepter_vpc_id
accepter_route_names = ["web", "db"]
}
No requirements.
Name | Version |
---|---|
aws | 3.54.0 |
aws.accepter | 3.54.0 |
No modules.
Name | Type |
---|---|
aws_route.accepter | resource |
aws_route.owner | resource |
aws_vpc_peering_connection.owner | resource |
aws_vpc_peering_connection_accepter.accepter | resource |
aws_caller_identity.accepter | data source |
aws_route_tables.accepter | data source |
aws_route_tables.owner | data source |
aws_vpc.accepter | data source |
aws_vpc.owner | data source |
Name | Description | Type | Default | Required |
---|---|---|---|---|
accepter_profile | AWS Profile | any |
n/a | yes |
accepter_region | AWS region for accepter vpc | string |
"eu-west-1" |
no |
accepter_route_names | Accepter subnet names that should be routed | set(string) |
n/a | yes |
accepter_vpc_id | Accepter VPC Id | any |
n/a | yes |
owner_profile | AWS Profile | any |
n/a | yes |
owner_region | AWS region for owner vpc | string |
"eu-west-1" |
no |
owner_route_names | Owner subnet names that should be routed | set(string) |
n/a | yes |
owner_vpc_id | Owner VPC Id | any |
n/a | yes |
No outputs.