Terraform module to connect two VPC's on AWS.
We eat, drink, sleep and most importantly love DevOps. We are working towards stratergies for standardizing architecture while ensuring security for the infrastructure. We are strong believer of the philosophy Bigger problems are always solved by breaking them into smaller manageable problems. Resonating with microservices architecture, it is considered best-practice to run database, cluster, storage in smaller connected yet manageable pieces within the infrastructure.
This module is basically combination of Terraform open source and includes automatation tests and examples. It also helps to create and improve your infrastructure with minimalistic code instead of maintaining the whole infrastructure code yourself.
We have fifty plus terraform modules. A few of them are comepleted and are available for open source usage while a few others are in progress.
This module has a few dependencies:
- Terraform 0.12
- Go
- github.com/stretchr/testify/assert
- github.com/gruntwork-io/terratest/modules/terraform
IMPORTANT: Since the master branch used in source varies based on new modifications, we suggest that you use the release versions here.
Here is an example of how you can use this module in your inventory structure:
module "vpc-peering" {
source = "git::https://github.com/clouddrove/terraform-aws-vpc-peering.git?ref=tags/0.12.1"
name = "vpc-peering"
application = "clouddrove"
environment = "test"
label_order = ["environment", "name", "application"]
requestor_vpc_id = "vpc-XXXXXXXXXXXXXXXXX"
acceptor_vpc_id = "vpc-XXXXXXXXXXXXXXXXX"
}| Name | Description | Type | Default | Required |
|---|---|---|---|---|
| acceptor_allow_remote_vpc_dns_resolution | Allow acceptor VPC to resolve public DNS hostnames to private IP addresses when queried from instances in the requestor VPC. | bool | true |
no |
| acceptor_vpc_id | Acceptor VPC ID. | string | - | yes |
| application | Application (e.g. cd or clouddrove). |
string | `` | no |
| auto_accept | Automatically accept the peering (both VPCs need to be in the same AWS account). | bool | true |
no |
| environment | Environment (e.g. prod, dev, staging). |
string | `` | no |
| label_order | label order, e.g. name,application. |
list | <list> |
no |
| name | Name (e.g. app or cluster). |
string | `` | no |
| requestor_allow_remote_vpc_dns_resolution | Allow requestor VPC to resolve public DNS hostnames to private IP addresses when queried from instances in the acceptor VPC. | bool | true |
no |
| requestor_vpc_id | Requestor VPC ID. | string | - | yes |
| tags | Additional tags (e.g. map(BusinessUnit,XYZ). |
map(string) | <map> |
no |
| vpc_peering | Set to false to prevent the module from creating or accessing any resources. | bool | true |
no |
| Name | Description |
|---|---|
| accept_status | The status of the VPC peering connection request. |
| connection_id | VPC peering connection ID. |
| tags | A mapping of tags to assign to the resource. |
In this module testing is performed with terratest and it creates a small piece of infrastructure, matches the output like ARN, ID and Tags name etc and destroy infrastructure in your AWS account. This testing is written in GO, so you need a GO environment in your system.
You need to run the following command in the testing folder:
go test -run TestIf you come accross a bug or have any feedback, please log it in our issue tracker, or feel free to drop us an email at hello@clouddrove.com.
If you have found it worth your time, go ahead and give us a ★ on our GitHub!
At CloudDrove, we offer expert guidance, implementation support and services to help organisations accelerate their journey to the cloud. Our services include docker and container orchestration, cloud migration and adoption, infrastructure automation, application modernisation and remediation, and performance engineering.
We are The Cloud Experts!
We ❤️ Open Source and you can check out our other modules to get help with your new Cloud ideas.