Skip to content

Embracing infrastructure as code and automating the deployment of my mail server to AWS with Terraform and Chef.

Notifications You must be signed in to change notification settings

hryatgit/email-infra-terraform

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Mail Server Infrastructure

Objective

I'm currently running Mail-in-a-box and hosting this single server on DigitalOcean. The goal of this project is to migrate this mail server to AWS and manage the infrastructure with Terraform. Ideally, this will enable me to easily create and destroy the environment, move between regions or add regional redundancy for the servers.

This will also provide an opportunity to break out Mail-in-a-box components into different servers (instances).

Proposed environment:

aws infra

Source: (Amazon) Scenario 2: VPC with public and private subnets

Getting Started

You will need to create a file called terraform.tfvars to store some variables. The file should look like this:

aws_access_key = ""
aws_secret_key = ""
aws_key_path = "~/path/to/keys.pem"
aws_key_name = "aws-keypair-name"

Then you can run the following commands to get started:

$ terraform plan
$ terraform apply

Tools

  • Terraform
  • Chef
  • AWS
  • Ubuntu Linux

About

Embracing infrastructure as code and automating the deployment of my mail server to AWS with Terraform and Chef.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages