Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Peerd: an AWS VPC peering connection management tool

github.com

Post reply on HN
Print view View original

1–10 of 28 posts

Re: Peerd: an AWS VPC peering connection management tool

#2

Post by bmcalary_atl »

Be kind, this is one of my first python projects. :)

peerd is an AWS VPC Peering Connection management tool. It manages the full lifecycle of creation, deletion and route table updates needed to make VPC peerings useful.

Capabilities

    Capable of creating and accepting cross-account VPC peerings.
    Capable of creating and accepting cross-region VPC peerings.
    Capable of creating full-meshes of VPC peerings.
    Injects, repairs and removes routes as needed from VPC routing tables.
    Capable of managing overlapping meshes with the use of an environment name which is used to tag peerings.
    Overlapping meshes supported through the use of different environment names in configuration file.
Yes, Transit Gateway is a valid replacement for this tool. :)

Re: Peerd: an AWS VPC peering connection management tool

#3

Post by JshWright »

bmcalary_atl wrote: post #2

Be kind, this is one of my first python projects. :) peerd is an AWS VPC Peering Connection management tool. It manages the full lifecycle of creation, deletion and route table updates needed to make VPC peerings useful. Capabilities Capable of creating and accepting cross-account VPC peerings. Capable of creating and accepting cross-region VPC peerings. Capable of creating full-meshes of VPC peerings. Injects, repai…

Haven't had an opportunity to look any deeper than the project description, but this is definitely a thing I've wanted in the past...

Re: Peerd: an AWS VPC peering connection management tool

#7

Post by saber6 »

bmcalary_atl wrote: post #2

Be kind, this is one of my first python projects. :) peerd is an AWS VPC Peering Connection management tool. It manages the full lifecycle of creation, deletion and route table updates needed to make VPC peerings useful. Capabilities Capable of creating and accepting cross-account VPC peerings. Capable of creating and accepting cross-region VPC peerings. Capable of creating full-meshes of VPC peerings. Injects, repai…

Interesting concept - is this designed to be used independent of some kind of infrastructure as code tooling?

I do all of my VPC peering and route-table manipulation via terraform repos today, so I am curious what the benefit of using this would be over what I have today (if there is).

Thanks.

Re: Peerd: an AWS VPC peering connection management tool

#9

Post by bmcalary_atl »

saber6 wrote: post #7
bmcalary_atl wrote: post #2

Be kind, this is one of my first python projects. :) peerd is an AWS VPC Peering Connection management tool. It manages the full lifecycle of creation, deletion and route table updates needed to make VPC peerings useful. Capabilities Capable of creating and accepting cross-account VPC peerings. Capable of creating and accepting cross-region VPC peerings. Capable of creating full-meshes of VPC peerings. Injects, repai…

Interesting concept - is this designed to be used independent of some kind of infrastructure as code tooling? I do all of my VPC peering and route-table manipulation via terraform repos today, so I am curious what the benefit of using this would be over what I have today (if there is). Thanks.

Terraform is definitely an option, but we found (the story might be different since 0.12) that creating large full meshes with many VPCs across many accounts with many route tables resulted in Terraform modules and files that were quite complex, long and hard to overlap with other meshes.

This tool can be used alongside terraform, ansible or whatever infra-as-code orchestration tool you like. I encourage you to do so! :)

Re: Peerd: an AWS VPC peering connection management tool

#10

Post by eropple »

bmcalary_atl wrote: post #9
saber6 wrote: post #7

Earlier quoted context omitted.

Interesting concept - is this designed to be used independent of some kind of infrastructure as code tooling? I do all of my VPC peering and route-table manipulation via terraform repos today, so I am curious what the benefit of using this would be over what I have today (if there is). Thanks.

Terraform is definitely an option, but we found (the story might be different since 0.12) that creating large full meshes with many VPCs across many accounts with many route tables resulted in Terraform modules and files that were quite complex, long and hard to overlap with other meshes. This tool can be used alongside terraform, ansible or whatever infra-as-code orchestration tool you like. I encourage you to do so…

FWIW, this problem is significantly alleviated with Pulumi. I've knocked together something internal that's a lot like this, in Pulumi, in something like thirty lines.

That's emphatically not to take anything away from this, as if you're not using Pulumi this is a relatively hard problem to deal with, but it does feel as though a lot of the more annoying aspects of our jobs as infra professionals are made a lot easier with it.

Post reply on HN