Peering

Create and accept VPC Peering

Requirements

• Ansible 2.5

Additional variables

Additional variables that can be used (either as host_vars/group_vars or via command line args):

Example definition

With sane defaults

When using the sane defaults, the only thing to configure for each peering is:

• the peering name
• the name or filter of the peering requester
• the name or filter of the peering accepter

aws_vpc_peering:
  - name: my-peering-1
    req_filter:
      - key: "tag:Name"
        val: vpc-1
      - key: "tag:Env"
        val: production
    acc_filter:
      - key: "tag:Name"
        val: vpc-2
      - key: "tag:Env"
        val: production
  - name: my-peering-2
    req_name: vpc-1
    acc_name: vpc-2

Customized array

Instead of using somebody's sane defaults, you can also fully customize your peering.

# Ensure VPC filter (name or filter) includes that the VPC is created already
# (not pending nor deleted)
aws_vpc_peering_vpc_filter_additional:
  - key: state
    val: available

aws_vpc_peering:
  - name: my-peering-1
    req_filter:
      - key: "tag:Name"
        val: vpc-1
      - key: "tag:Env"
        val: production
    acc_filter:
      - key: "tag:Name"
        val: vpc-2
      - key: "tag:Env"
        val: production
    region: eu-central-1
    tags:
      - key: env
        val: production
      - key: department
        val: devops

  - name: my-peering-2
    req_name: vpc-1
    acc_name: vpc-2
    region: eu-central-1
    tags:
      - key: env
        val: production
      - key: department
        val: devops

Testing

Requirements

• Docker
• yamllint

Run tests

# Lint the source files
make lint

# Run integration tests with default Ansible version
make test

# Run integration tests with custom Ansible version
make test ANSIBLE_VERSION=2.4