Рет қаралды 492
The Vault on AWS GitHub project link - github.com/jco...
So we've done our normal deployment, which is perfectly safe to use if you watch the IP address ranges (or CIDR blocks) that can access it. But, if your infrastructure is already on AWS, we can take security further by running our Vault deployment in "private mode". Doing it this way will make it so your vault is no longer accessible to the public internet. It's pretty locked-down, until you give virtual private networks (VPCs) on AWS access to the Vault VPC.
Now VPCs themselves are a big topic so we don't get into them here. If you'd like to learn more about VPCs, you can check out the link to a guide I wrote about them below.
If this sounds like a lot, don't worry. In this video we're going to set up a couple of example VPCs and servers. This will let us see how to properly connect them to Vault when the project is running in private mode. Let's get started on that now and in the next video we'll get into the private deployment process itself.
Useful Links:
• HashiCorp Vault Releases page - releases.hashi...
• AWS VPC Core Concepts in an Analogy and Guide - start.jcolemor...
• The AwsDevOps.io website - awsdevops.io/
• The AWS EC2 Fundamentals Series KZbin playlist - • The AWS EC2 Fundamenta...
Sign up to my mailing list for exclusive tech guides and thoughts: list.jcolemorr...