Running CoreOS Container Linux on EC2

We will be launching three instances, with a few parameters in the User Data, and selecting our security group.

1. Open the quick launch wizard to boot ami-0c1eaf56b1bebcaa8.
2. On the second page of the wizard, launch 3 servers to test our clustering
   • Number of instances: 3
   • Click "Continue"
3. Next, we need to specify a discovery URL, which contains a unique token that allows us to find other hosts in our cluster. If you're launching your first machine, generate one at https://discovery.etcd.io/new?size=3, configure the `?size=` to your initial cluster size and add it to the metadata. You should re-use this key for each machine in the cluster.
4. Use ct to convert the following configuration into an Ignition config, and back in the EC2 dashboard, paste it into the "User Data" field.
   • Container Linux Config
   • Ignition Config
   This is the human-readable config file. This should not be immediately passed to Container Linux. Learn more.

   # This config is meant to be consumed by the config transpiler, which will
   # generate the corresponding Ignition config. Do not pass this config directly
   # to instances of Container Linux.
   
   etcd:
     # All options get passed as command line flags to etcd.
     # Any information inside curly braces comes from the machine at boot time.
   
   # multi\_region and multi\_cloud deployments need to use {PUBLIC\_IPV4}
   
   advertise\_client\_urls:       "http://{PRIVATE\_IPV4}:2379"
   initial\_advertise\_peer\_urls: "http://{PRIVATE\_IPV4}:2380"
   
   # listen on both the official ports and the legacy ports
   
   # legacy ports can be omitted if your application doesn't depend on them
   
   listen\_client\_urls:          "http://0.0.0.0:2379"
   listen\_peer\_urls:            "http://{PRIVATE\_IPV4}:2380"
   
   # generate a new token for each unique cluster from https://discovery.etcd.io/new?size=3
   
   # specify the initial size of your cluster with ?size=X
   
   discovery:                   "https://discovery.etcd.io/<token>"
   

   This is the raw machine configuration, which is not intended for editing. Learn more. Validate the config here.

   {
     "ignition": {
       "config": {},
       "timeouts": {},
       "version": "2.1.0"
     },
     "networkd": {},
     "passwd": {},
     "storage": {},
     "systemd": {}
   }
   

   `
   • Paste configuration into "User Data"
   • "Continue"
5. Storage Configuration
   • "Continue"
6. Tags
   • "Continue"
7. Create Key Pair
   • Choose a key of your choice, it will be added in addition to the one in the gist.
   • "Continue"
8. Choose one or more of your existing Security Groups
   • "coreos-testing" as above.
   • "Continue"
9. Launch!

We will be launching three instances, with a few parameters in the User Data, and selecting our security group.

1. Open the quick launch wizard to boot ami-08ca65b75f87b8cec.
2. On the second page of the wizard, launch 3 servers to test our clustering
   • Number of instances: 3
   • Click "Continue"
3. Next, we need to specify a discovery URL, which contains a unique token that allows us to find other hosts in our cluster. If you're launching your first machine, generate one at https://discovery.etcd.io/new?size=3, configure the `?size=` to your initial cluster size and add it to the metadata. You should re-use this key for each machine in the cluster.
4. Use ct to convert the following configuration into an Ignition config, and back in the EC2 dashboard, paste it into the "User Data" field.
   • Container Linux Config
   • Ignition Config
   This is the human-readable config file. This should not be immediately passed to Container Linux. Learn more.

   # This config is meant to be consumed by the config transpiler, which will
   # generate the corresponding Ignition config. Do not pass this config directly
   # to instances of Container Linux.
   
   etcd:
     # All options get passed as command line flags to etcd.
     # Any information inside curly braces comes from the machine at boot time.
   
     # multi_region and multi_cloud deployments need to use {PUBLIC_IPV4}
     advertise_client_urls:       "http://{PRIVATE_IPV4}:2379"
     initial_advertise_peer_urls: "http://{PRIVATE_IPV4}:2380"
     # listen on both the official ports and the legacy ports
     # legacy ports can be omitted if your application doesn't depend on them
     listen_client_urls:          "http://0.0.0.0:2379"
     listen_peer_urls:            "http://{PRIVATE_IPV4}:2380"
     # generate a new token for each unique cluster from https://discovery.etcd.io/new?size=3
     # specify the initial size of your cluster with ?size=X
     discovery:                   "https://discovery.etcd.io/<token>"
   

   This is the raw machine configuration, which is not intended for editing. Learn more. Validate the config here.

   {
     "ignition": {
       "config": {},
       "timeouts": {},
       "version": "2.1.0"
     },
     "networkd": {},
     "passwd": {},
     "storage": {},
     "systemd": {
       "units": [
         {
           "dropins": [
             {
               "contents": "[Unit]\nRequires=coreos-metadata.service\nAfter=coreos-metadata.service\n\n[Service]\nEnvironmentFile=/run/metadata/coreos\nExecStart=\nExecStart=/usr/lib/coreos/etcd-wrapper $ETCD_OPTS \\\n  --listen-peer-urls=\"http://${COREOS_EC2_IPV4_LOCAL}:2380\" \\\n  --listen-client-urls=\"http://0.0.0.0:2379\" \\\n  --initial-advertise-peer-urls=\"http://${COREOS_EC2_IPV4_LOCAL}:2380\" \\\n  --advertise-client-urls=\"http://${COREOS_EC2_IPV4_LOCAL}:2379\" \\\n  --discovery=\"https://discovery.etcd.io/\u003ctoken\u003e\"",
               "name": "20-clct-etcd-member.conf"
             }
           ],
           "enable": true,
           "name": "etcd-member.service"
         }
       ]
     }
   }
   

   ` ```
   • Paste configuration into "User Data"
   • "Continue"
5. Storage Configuration
   • "Continue"
6. Tags
   • "Continue"
7. Create Key Pair
   • Choose a key of your choice, it will be added in addition to the one in the gist.
   • "Continue"
8. Choose one or more of your existing Security Groups
   • "coreos-testing" as above.
   • "Continue"
9. Launch!