diff --git a/os/booting-on-ec2.md b/os/booting-on-ec2.md index d8f14b50b..5e93dd9aa 100644 --- a/os/booting-on-ec2.md +++ b/os/booting-on-ec2.md @@ -265,22 +265,22 @@ First we need to create a security group to allow Container Linux instances to c
  • Use ct to convert the following configuration into an Ignition config, and back in the EC2 dashboard, paste it into the "User Data" field. - ```yaml container-linux-config:ec2 - 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/" - ``` +```yaml container-linux-config:ec2 +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/" +```
    • Paste configuration into "User Data"
    • "Continue"
    • @@ -339,22 +339,22 @@ First we need to create a security group to allow Container Linux instances to c
    • Use ct to convert the following configuration into an Ignition config, and back in the EC2 dashboard, paste it into the "User Data" field. - ```yaml container-linux-config:ec2 - 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/" - ``` +```yaml container-linux-config:ec2 +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/" +```
      • Paste configuration into "User Data"
      • "Continue"
      • @@ -413,22 +413,22 @@ First we need to create a security group to allow Container Linux instances to c
      • Use ct to convert the following configuration into an Ignition config, and back in the EC2 dashboard, paste it into the "User Data" field. - ```yaml container-linux-config:ec2 - 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/" - ``` +```yaml container-linux-config:ec2 +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/" +```
        • Paste configuration into "User Data"
        • "Continue"