| ... | ... | @@ -34,6 +34,7 @@ Next you'll create 2 users accounts, one that will manage the infrastructure and |
|
|
|
|
|
|
|
5. [Create an AWS S3 bucket](https://s3.console.aws.amazon.com/s3/home) in the **region you intend to launch machines**.
|
|
|
|
- The bucket **does not** need to have public access.
|
|
|
|
|
|
|
|
- Assign the name to `aws_bucket_name`.
|
|
|
|
`variable "aws_bucket_name" { default = "your_bucket_name"}`
|
|
|
|
|
| ... | ... | @@ -45,7 +46,6 @@ Next you'll create 2 users accounts, one that will manage the infrastructure and |
|
|
|
`aws route53 create-reusable-delegation-set --caller-reference="unique" --hosted-zone-id="YOUR_ZONE_ID"`
|
|
|
|
|
|
|
|
- Finally, get the ID created from the command and place it in `envs/your_env_folder/vars.tf` assigning it to `placeholder_reusable_delegationset_id`.
|
|
|
|
|
|
|
|
`variable "placeholder_reusable_delegationset_id" { default = "ID_CREATED_FROM_COMMAND" }`
|
|
|
|
|
|
|
|
Now a placeholder hosted zone with 4 nameservers will be "saved" in route53 that we can point any domain in our registrars to (which is covered in the [next step](domain)) and not worry about changing them again. Its rather convoluted compared to digital oceans `ns1.digitalocean.com...` convention but it gets the job done.
|
| ... | ... | |
