Skip to content
Terraform module to create a peering connection between two VPCs in the same AWS account.
HCL Makefile
Branch: master
Clone or download
Pull request Compare This branch is even with cloudposse:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs
images
.gitignore
.travis.yml
LICENSE
Makefile
README.md
README.yaml
main.tf
outputs.tf
variables.tf

README.md

README Header

Cloud Posse

terraform-aws-vpc-peering Build Status Latest Release Slack Community

Terraform module to create a peering connection between two VPCs


This project is part of our comprehensive "SweetOps" approach towards DevOps.

Terraform Open Source Modules

It's 100% Open Source and licensed under the APACHE2.

We literally have hundreds of terraform modules that are Open Source and well-maintained. Check them out!

Screenshots

vpc-peering VPC Peering Connection in the AWS Web Console

Usage

IMPORTANT: Using the master branch is just an example. Do not pin to master in your code because there may be breaking changes between releases. Instead pin to the release tag (e.g. ?ref=tags/x.y.z) of one of our latest releases.

Using VPC IDs

module "vpc_peering" {
  source           = "git::https://github.com/cloudposse/terraform-aws-vpc-peering.git?ref=master"
  namespace        = "cp"
  stage            = "dev"
  name             = "cluster"
  requestor_vpc_id = "vpc-XXXXXXXX"
  acceptor_vpc_id  = "vpc-YYYYYYYY"
}

Using VPC tags

module "vpc_peering" {
  source             = "git::https://github.com/cloudposse/terraform-aws-vpc-peering.git?ref=master"
  namespace          = "cp"
  stage              = "dev"
  name               = "cluster"
  requestor_vpc_tags = {
    "kubernetes.io/cluster/my-k8s" = "owned"
  }
  acceptor_vpc_tags  = {
    Name = "legacy-vpc"
  }
}

Makefile Targets

Available targets:

  help                                Help screen
  help/all                            Display help for all targets
  help/short                          This help short screen
  lint                                Lint terraform code

Inputs

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 string true no
acceptor_vpc_id Acceptor VPC ID string `` no
acceptor_vpc_tags Acceptor VPC tags map <map> no
attributes Additional attributes (e.g. policy or role) list <list> no
auto_accept Automatically accept the peering (both VPCs need to be in the same AWS account) string true no
delimiter Delimiter to be used between namespace, stage, name, and attributes string - no
enabled Set to false to prevent the module from creating or accessing any resources string true no
name Name (e.g. app or cluster) string - yes
namespace Namespace (e.g. cp or cloudposse) string - yes
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 string true no
requestor_vpc_id Requestor VPC ID string `` no
requestor_vpc_tags Requestor VPC tags map <map> no
stage Stage (e.g. prod, dev, staging) string - yes
tags Additional tags (e.g. map('BusinessUnit,XYZ`) map <map> no

Outputs

Name Description
accept_status The status of the VPC peering connection request
connection_id VPC peering connection ID

Share the Love

Like this project? Please give it a ★ on our GitHub! (it helps us a lot)

Are you using this project or any of our other projects? Consider leaving a testimonial. =)

Related Projects

Check out these related projects.

References

For additional context, refer to some of these links.

Help

Got a question?

File a GitHub issue, send us an email or join our Slack Community.

README Commercial Support

Commercial Support

Work directly with our team of DevOps experts via email, slack, and video conferencing.

We provide commercial support for all of our Open Source projects. As a Dedicated Support customer, you have access to our team of subject matter experts at a fraction of the cost of a full-time engineer.

E-Mail

  • Questions. We'll use a Shared Slack channel between your team and ours.
  • Troubleshooting. We'll help you triage why things aren't working.
  • Code Reviews. We'll review your Pull Requests and provide constructive feedback.
  • Bug Fixes. We'll rapidly work to fix any bugs in our projects.
  • Build New Terraform Modules. We'll develop original modules to provision infrastructure.
  • Cloud Architecture. We'll assist with your cloud strategy and design.
  • Implementation. We'll provide hands-on support to implement our reference architectures.

Terraform Module Development

Are you interested in custom Terraform module development? Submit your inquiry using our form today and we'll get back to you ASAP.

Slack Community

Join our Open Source Community on Slack. It's FREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally sweet infrastructure.

Newsletter

Signup for our newsletter that covers everything on our technology radar. Receive updates on what we're up to on GitHub as well as awesome new projects we discover.

Contributing

Bug Reports & Feature Requests

Please use the issue tracker to report any bugs or file feature requests.

Developing

If you are interested in being a contributor and want to get involved in developing this project or help out with our other projects, we would love to hear from you! Shoot us an email.

In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.

  1. Fork the repo on GitHub
  2. Clone the project to your own machine
  3. Commit changes to your own branch
  4. Push your work back up to your fork
  5. Submit a Pull Request so that we can review your changes

NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!

Copyright

Copyright © 2017-2019 Cloud Posse, LLC

License

License

See LICENSE for full details.

Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

  https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.

Trademarks

All other trademarks referenced herein are the property of their respective owners.

About

This project is maintained and funded by Cloud Posse, LLC. Like it? Please let us know by leaving a testimonial!

Cloud Posse

We're a DevOps Professional Services company based in Los Angeles, CA. We ❤️ Open Source Software.

We offer paid support on all of our projects.

Check out our other projects, follow us on twitter, apply for a job, or hire us to help with your cloud strategy and implementation.

Contributors

Andriy Knysh
Andriy Knysh
Vladimir
Vladimir

README Footer Beacon

You can’t perform that action at this time.