Cloud computing runs on Cloud networks, when the cheese moves it’s time to hit the maze!
In the previous post we installed Terraform and used it to create a VPC in AWS , subnets, instances and all the necessary elements for a lab with Wireguard.
In this post we’ll install and configure a Wireguard server, a remote client and use it to access an EC2 instance in a private subnet.
In my last post I worked with AWS CLI and Cloudformation to create a simple VPC and find a configuration drift.
In this post I’ll show you how to build a VPC in AWS with all the elements necessary to lab Wireguard. We’ll use Terraform to automate the creation of the VPC.
Today I spent some time working with AWS CLI focusing on Cloudformation and how to deal with configuration drift.
Here’s some notes about the topic.
IPv6 is the evolution that everybody know must be done one day but not today.
Unike the Millenniun Bug that had a clear deadline, IPv6 adoption is a topic that I often discuss with clients but nobody is really willing to do it, even in a test environment.
I studied IPv6 in many Cisco certifications but since they’re focused on the infrastructure side of the network, I plan to do some labs myself in the next months.
My home network is connected to the Internet via radio bridge. The reason is ADSL services were not available a couple of years ago, now it is but since the radio bridge is cheap and works (most of the time) I really don’t care to change.
Some time ago I started to notice downtime of the Internet connection, I sent a few emails to the wisp but the answer was always the same: “we don’t see a problem right now”.