feat: add dns and TLS info for AWS

content/en/v3/admin/setup/ingress/tls_dns/aws.md

@@ -0,0 +1,124 @@
+---
+title: Amazon Web Services
+linktitle: Amazon
+type: docs
+description: Setting up TLS and DNS on Amazon Web Services
+weight: 100
+---
+
+## Prerequisites
+
+- cluster created using Jenkins X [AWS EKS Terraform getting started](/v3/admin/platform/eks/)
+- own a domain
+- latest Jenkins X CLI, Infrastructure and Cluster git repository updates [upgrade](/v3/guides/upgrade)
+
+### Cloud Infrastructure
+
+Add to your `values.auto.tfvars` the following:
+
+```yaml
+apex_domain = "foo.io"
+```
+
+By default, Jenkins X terraform module configure Route53 for the apex/parent domain.
+If you want Jenkins X not to manage the parent/apex domain, set
+
+```yaml
+manage_apex_domain = false
+```
+
+This is for the cases where you are managing the apex domain outside of AWS or outside of Jenkins X installation.
+
+Most people prefer to use a subdomain for a specific installation rather than purchasing one domain per cluster. For example in a multi cluster setup you will probably want all using the same parent domain but two clusters using a different subdomain like development.foo.io, staging.foo.io leaving production using just the parent domain foo.io.
+
+To use a subdomain for this cluster add the following configuration:
+
+```yaml
+subdomain     = "dev"
+```
+
+We will now add details that will be passed to Jenkins X as requirements when booting the cluster.
+
+Add these to `values.auto.tfvars`
+
+```yaml
+production_letsencrypt  = true
+tls_email               = your_email_address@googlegroups.com
+```
+
+Now apply these changes:
+
+```bash
+git add values.auto.tfvars
+git commit -m 'feat: enable DNS cloud resources'
+git push
+```
+
+You may want to set two environment variables here so that Terraform does not prompt for values
+
+```bash
+export TF_VAR_jx_bot_username=
+export TF_VAR_jx_bot_token=
+```
+
+now run
+
+```bash
+terraform plan
+terraform apply
+```
+
+If using a subdomain you will now see your managed zone in Route53.
+
+**Once terraform has finished for now there is a manual trigger of the Jenkins X cluster repository required. This will not be needed in the future but for now please make a dummy commit on your cluster git repository and follow the boot job as in applies the updates to your cluster.**
+
+To follow the jx boot installation using the instructions given in the terraform output, connect to the cluster and run:
+
+```bash
+jx admin logs
+```
+
+There is a timing issue with cert-manager and the admission controller so the first boot job may fail but second will run automatically and succeed.
+
+It can take a short while for DNS to propagate so you may need to wait for 5 - 10 minutes. https://dnschecker.org/ is a useful way to check the status of DNS propagating.
+
+To verify using the CLI run:
+
+```bash
+kubectl get ingress -n jx
+```
+
+and use the hook URL
+
+```bash
+jx verify tls hook-jx.dev.foo.io  --production=false --timeout 20m
+```
+
+You should be able to verify the TLS certificate from Lets Encrypt in your browser (beware of browser caching if you don't see any changes)
+
+![Working TLS](/images/v3/working_tls.png)
+
+Once this is working you can switch any of the configuration using your cluster git repository and change the jx-requirements.yaml, e.g. toggling the cert-manager production service or editing the email address used:
+
+```yaml
+ingress:
+  domain: dev.foo.io
+  externalDNS: true
+  namespaceSubDomain: -jx.
+  tls:
+    email: "joe@gmail.com"
+    enabled: true
+    production: true
+```
+
+Git commit and push the change back to your remote git repository and follow the installation:
+
+```bash
+jx admin logs
+```
+
+You will now be issued a valid TLS certificate
+
+```bash
+jx verify tls hook-jx.dev.foo.io  --production=true --timeout 20m
+```