Copyright (c) 2006-2014 MindTouch Inc.
This file and accompanying files are licensed under the MindTouch Master Subscription Agreement (MSA).
At any time, you shall not, directly or indirectly: (i) sublicense, resell, rent, lease, distribute, market, commercialize or otherwise transfer rights or usage to: (a) the Software, (b) any modified version or derivative work of the Software created by you or for you, or (c) MindTouch Open Source (which includes all non-supported versions of MindTouch-developed software), for any purpose including timesharing or service bureau purposes; (ii) remove or alter any copyright, trademark or proprietary notice in the Software; (iii) transfer, use or export the Software in violation of any applicable laws or regulations of any government or governmental agency; (iv) use or run on any of your hardware, or have deployed for use, any production version of MindTouch Open Source; (v) use any of the Support Services, Error corrections, Updates or Upgrades, for the MindTouch Open Source software or for any Server for which Support Services are not then purchased as provided hereunder; or (vi) reverse engineer, decompile or modify any encrypted or encoded portion of the Software.
A complete copy of the MSA is available at http://www.mindtouch.com/msa
To set up DNS hostnames for a deployment's load balancing and database tiers using Amazon Route 53 as the DNS provider.
Table of Contents
Manage AWS more efficiently with RightScale. Try it free.
Amazon offers their own DNS service for handling dynamic DNS hostnames on EC2. Their same pay-as-you-go model applies to Route 53. This service requires that you sign-up for the service before your AWS account is activated to use this feature.
If you are using dedicated cloud servers for load balancing purposes (e.g. RightScale's "Load Balancer with HAProxy" or "RightScale Load Balancer with Apache/HAProxy - 11H1" ServerTemplates), create a hostname for each frontend, load balancer server. Typically, you will have at least two load balancer servers for redundancy and failover purposes. You can either use Route 53 or another DNS provider of your choice since dynamic DNS is not required for the DNS records of the frontend load balancer servers.
If you are using dedicated cloud servers for load balancing purposes (e.g. RightScale's "Load Balancer with HAProxy" or "RightScale Load Balancer with Apache/HAProxy - 11H1" ServerTemplates), create an A record for each load balancer server. Typically, you will have at least two load balancer servers for redundancy and failover purposes. You can either use Route 53 or another DNS provider of your choice since dynamic DNS is not required for the DNS records of the frontend load balancer servers.
The next step is to create hostnames for the database tier. Since the "master" database server can potentially change over time during an upgrade or failover scenario, it's important that the IP address associated with a database hostname be modifiable. Application servers connect to the "master" database server at boot time by using the hostname that points to the current "master" database server. (e.g. db-master.example.com)
For the 11H1 RightScript-based ServerTemplates, you will need to create a minimum of two (2) DNS hostnames, one for the Master-DB and one for the Slave-DB, where the TTLs are set to 60 (sec).
For the v12.11 Chef-based ServerTemplates, you will only need to create a DNS hostname for the Master-DB with a TTL set to 60 (sec).
The diagram below shows a common three tier setup with DNS records.
If you are using RightScale's Load Balancer with HAProxy ServerTemplates to launch dedicated load balancers in EC2, assign Elastic IPs to the load balancer servers and create four DNS records.
If you are using Amazon's Elastic Load Balancing (ELB) service, create a CNAME for the elastic load balancer and A records for the database tier.
Log into your AWS account and sign-up for Amazon's Route 53 DNS service. (http://aws.amazon.com/route53)
See Amazon's Getting Started Guide: http://aws.amazon.com/documentation/route53/
Contact the company where you registered the domain name and update their Name Server Records so that they point to the domain name servers for Route 53.
When you configure the deployment's inputs, specify the following information so that the scripts will be able to update the DNS hostnames inside Route 53. The names of the inputs are slightly different depending on whether you're using RightScale's RightScript-based (11H1) or Chef-based ServerTemplates.
|Input Name - 11H1 (RightScripts)||Input Name - v12, v13 (Chef)||Example Value|
DNS Service Provider
|DNS_PASSWORD||DNS Password||cred: AWS_SECRET_ACCESS_KEY|
|DNS_USER||DNS User||cred: AWS_ACCESS_KEY_ID|
|MASTER_DB_DNSNAME||Database Master FQDN||text:db-master.example.com|
Database Master DNS Record ID
|SLAVE_DB_DNSID||Database Slave DNS Record ID (Optional)|| |
|Glossary | 用語 | 용어||Site Map | Site Help||Community||Corporate Site||Get Support||Dashboard Login|
|Doc Feedback||Product Feedback||Resources||MultiCloud Marketplace||Forums|
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.