Jeff Dickman - Blog There's something to this...

Terraform OpenVPN Marketplace AMI and Multiple VPCs

Recently, I was working on configuring an OpenVPN server that existing in a services VPC. The services that VPN clients needed to access were located in a peered VPC. For what it’s worth, the OpenVPN AMI in the AWS Marketplace only configures its internal routing permissions for the VPC CIDR block that the instance comes online for. You can manually configure additonal CIDR blocks via the web console, but ugh… every time a new OpenVPN instance is set up… tedius and prone to issues. Automation is the way to go here…

Terraform and Scheduling AutoScaling Groups

I often advocate the idea that, if done right, using AWS can lower your costs for infrastructure. One great way to accomplish this is to us AutoScaling groups wherever possible. As a most basic feature, AutoScaling Groups allow you to dial up and dial down instances based on driving metrics. Metrics like CPU, RAM and Network can allow your services to expaand when needed and drop down to minimal levels during quiet times. AutoScaling Groups also allow you to set a schedule for increasing or decreasing your capacity. The scheduling feature can come in very handy for managing the availability of resources in a development environment.

Sharing Private DNS between VPCs with Route53

I recently ran into a configuration that had multiple accounts and VPCs that needed to share Route53 Private Private Hosted Zone records between them. Each account had it’s own Route53 private DNS, but in some cases services in each account needed to access hosts by name in other Accounts/VPCs.

Blogging with Jekyll and S3

I did a fair bit of research before I moved my blog off it’s fancy WordPress site to a static site that could be hosted in S3. There are a lot of ways you could go with this one, some of them are pretty complex - like writing my own HTML and managing content that way - yuck. I wanted something simple, that I could easily update.

AWS Workspaces Keyboard on Mac

Recently, I set up an AWS Workspace configuration for a client. I ran into an interestingly frustrating issue. When I launched the Workspace client from my Mac (macOS Sierra) the mouse would work just fine, but no keyboard input would be sent across. I spent a bit of time Googling and reading the developer forums, which selected quite a few possibilities, which I tried. Like many folks out there, none of the fixes presented solved my problem.