aws.md

AWS

WARNING: When running this quickstart, you might experience some issues with cloud resource limits. Please, verify your quotas before proceeding.

Install AWS CLI

Make sure to have previously installed AWS CLI.

Setup access

First, you will need to retrieve your AWS credentials. The default location is $HOME/.aws/credentials on Linux and OS X, or "%USERPROFILE%\.aws\credentials" for Windows users.

Before proceeding, we recommend you create a file with your AWS credentials, exposed as (the commonly) recognized environment variables, so you can source it later, in between shell sessions:

$ cat << EOF > ~/.aws/my_credentials
export AWS_ACCESS_KEY_ID=<YOUR ACCESS KEY>
export AWS_SECRET_ACCESS_KEY=<YOUR SECRET KEY>
EOF

Last, set-up SSH keys as detailed in the official documentation.

Don't forget to add your new SSH private key to your session:

$ ssh-add ~/.ssh/path_to_your_new_key.pem

Prepare infrastructure configuration

Make sure Terraform knows where to find your AWS credentials:

$ source ~/.aws/my_credentials

Now, let's generate the default infrastructure configuration:

$ make aws

This will output sane defaults to .deploy/terraform.tfvars. Now, edit said file and set ssh_public_key_file, the public SSH key you will use to log-in into your new VMs later.

WARNING: Please, do not set a smaller instance (VM) type on the risk of failing to install Kubernetes.

cluster_name = "dcos-kubernetes"
cluster_name_random_string = true

dcos_version = "1.12.3"
dcos_security = "strict" # valid values are strict, permissive, disabled

num_of_masters = "1"
num_of_private_agents = "4"
num_of_public_agents = "1"

instance_os = "centos_7.5"
bootstrap_instance_type = "m5.large"
master_instance_type = "m5.2xlarge"
private_agent_instance_type = "m5.2xlarge"
public_agent_instance_type = "m5.2xlarge"

aws_region = "us-west-2"
# ssh_public_key_file = ""
# aws_key_name = "default" # uncomment to use an already defined AWS key
# admin_ips = "0.0.0.0/0" # uncomment to access master from any IP

Kubernetes configuration

Highly Available cluster

NOTE: By default, it will provision a Kubernetes cluster with one (1) worker node, and a single instance of every control plane component.

To deploy a highly-available cluster with three (3) private Kubernetes nodes update .deploy/options.json:

{
  "service": {
    "name": "dev/kubernetes01"
  },
  "kubernetes": {
    "high_availability": true,
    "private_node_count": 3
  }
}

Let's continue with Kubernetes cluster configuration.