You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that you have the hostname of your load balancer we can use the `nip.io`
19
-
DNS service to route arbitrary hostnames to the Deis Workflow edge router. This
20
-
lets us point the Workflow CLI at your cluster without having to either use
21
-
your own domain or update DNS!
19
+
### Using DNS
20
+
21
+
Now that we have the hostname of the load balancer, let's create the wildcard DNS record that
22
+
directs requests from your machine to the application.
23
+
24
+
First, if you haven't already done so, register your domain name. The Internet Corporation for
25
+
Assigned Names and Numbers (ICANN) manages domain names on the Internet. You register a domain name
26
+
using a domain name registrar, an ICANN-accredited organization that manages the registry of domain
27
+
names. The website for your registrar will provide detailed instructions and pricing information
28
+
for registering your domain name. For more information, see the following resources:
29
+
30
+
- To use Amazon Route 53 to register a domain name, see [Registering Domain Names Using Amazon Route 53](http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/registrar.html).
31
+
- For a list of accredited registrars, see the [Accredited Registrar Directory](www.internic.net/regist.html).
32
+
33
+
Next, use your DNS service, such as your domain registrar, to create a wildcard CNAME record to
34
+
route queries to your load balancer. For more information, see the documentation for your DNS
35
+
service.
36
+
37
+
Alternatively, you can use Amazon Route 53 as your DNS service. You create a hosted zone, which
38
+
contains information about how to route traffic on the Internet for your domain, and an alias
39
+
resource record set, which routes queries for your domain name to your load balancer.
40
+
41
+
To create a hosted zone and an alias record set for your domain using Amazon Route 53:
42
+
43
+
1. Open the Amazon Route 53 console at https://console.aws.amazon.com/route53/.
44
+
2. Create a Public Hosted Zone with your domain name.
45
+
3. Select the hosted zone that you just created for your domain.
46
+
4. Click Go to Record Sets.
47
+
5. Create a Record Set with the name as `*`, the type as `CNAME - Canonical Name`, and as an alias
48
+
of the Load Balancer created from the router.
49
+
50
+
### Using nip.io
51
+
52
+
If you do not have registered a domain name and just want to try out Workflow on AWS, we can use
53
+
the `nip.io` wildcard DNS service to route arbitrary hostnames to the Deis Workflow edge router.
54
+
This lets us point the Workflow CLI at your cluster without having to either use your own domain or
55
+
update DNS!
56
+
57
+
!!! note
58
+
this is **not** how you should connect to your cluster after the quickstart. This is
59
+
for demonstration purposes only. Instead, you will want to use your own domain name routed to
60
+
the ELB through your domain registrar. AWS actively manages the ELB IPv4 addresses, so what may
61
+
be an IP address associated with your ELB today will be something else later on.
22
62
23
63
First, pick one of the IP addresses allocated to your ELB:
abce0d48217d311e69a470643b4d9062-2074277678.us-west-1.elb.amazonaws.com has address 52.8.166.233
27
68
abce0d48217d311e69a470643b4d9062-2074277678.us-west-1.elb.amazonaws.com has address 54.193.5.73
28
69
```
29
70
30
-
Note that this is **not** how you should connect to your cluster after the quickstart. Instead you will want to use your
31
-
own domain name routed to the ELB CNAME. AWS actively manages the ELB addresses so what may be an ip address associated
32
-
with your ELB today will be something else later on.
33
-
34
-
For now though, grab either address for the next step. We'll use `52.8.166.233` for this example.
71
+
Grab either address for the next step. We'll use `52.8.166.233` for this example.
35
72
36
73
To verify the Workflow API server and nip.io, construct your hostname by taking
37
74
the ip address for your load balancer and adding `nip.io`. For our example
38
75
above, the address would be: `52.8.166.233.nip.io`.
39
76
40
77
Nip answers with the ip address no matter the hostname:
78
+
41
79
```
42
80
$ host 52.8.166.233.nip.io
43
81
52.8.166.233.nip.io has address 52.8.166.233
44
82
$ host something-random.52.8.166.233.nip.io
45
83
something-random.52.8.166.233.nip.io has address 52.8.166.233
46
84
```
47
85
48
-
By default, any HTTP traffic for the hostname `deis` will be sent to the Workflow API service. To test that everything is connected properly you may validate connectivity using `curl`:
86
+
By default, any HTTP traffic for the hostname `deis` will be sent to the Workflow API service. To
87
+
test that everything is connected properly you may validate connectivity using `curl`:
0 commit comments