Blog articles tagged "terraform"

Setting up a WireGuard VPN at AWS using Terraform December 27th 2021

Most of our resources at AWS aren’t publicly accessible via the Internet. Instead we placed them in a separate VPC to isolate them from any malicious access by an attacker or even accidental access by ourselves.

However from time to time we do want to access the resources directly:

• During local development it may save us an enormous amount of time not having to build complex tunneling solutions within our application.
• Certain systems should never be exposed via the public Internet but should only be reachable for dedicated and authenticated users.

My first approach was to use AWS’s internal VPN solution which turned out to be both complex to setup as well as pretty expensive to use.

So while looking for alternatives my colleague Lukas pointed me towards WireGuard which turned out to be exactly what I was looking for.

In this posting I will describe how to setup a WireGuard VPN at AWS completely from scratch, using Terraform as infrastructure as code framework.

Setting up a NAT gateway on AWS using Terraform February 4th 2020

We’re in the middle of migrating a lot of our infrastructure components to AWS. One thing that took me a while to wrap my head around is how to setup a VPC (Virtual Private Cloud) at AWS in a way that all our outgoing traffic is routed via a fixed IP address. In this article I will demonstrate how this can be done, using Terraform to setup all required resources at AWS.

Using Terraform to provision infrastructure resources December 17th 2019

As we create more and more new service and require more and more infrastructure resources to support those services, we have started to use Terraform to manage our infrastructure.

In this article, I would like to give an overview of how we structure our Terraform setup.

It’s designed to build up a common vocabulary and understanding of why we do things the way we do them and provide a little bit of background information how and why we made the decisions that lead to the current setup.

As we’re using AWS to deploy our cloud infrastructure, most of the examples will relate to AWS but in principle should be provider-agnostic and can apply to other providers as well.