|« PreviousNext »|
|Did this page help you? Yes | No | Tell us about it...|
AWS provides flexible services, and there are many variations you can use to host your static website. In this section, we'll discuss using Amazon Route 53 with your static website.
Amazon Route 53 is a scalable Domain Name System (DNS) web service. It provides secure and reliable routing to your infrastructure that uses Amazon Web Services, such as Amazon Simple Storage Service (Amazon S3). You can also use Amazon Route 53 to route users to your infrastructure outside of AWS.
Amazon Route 53 automatically routes queries to the nearest DNS server in a global network of DNS servers, resulting in low latency.
It is an authoritative DNS service, meaning it translates friendly domain names like
into IP addresses such as
You can manage your DNS records through the Amazon Route 53 API, or set account-level user and access management through the AWS Identity and Access Management (IAM) API. Like other AWS products, there are no contracts or minimum commitments for using Amazon Route 53. You pay only for the domains you configure and the number of queries that the service answers. For more information about Amazon Route 53 pricing, go to Amazon Route 53 Pricing.
The following procedure explains the high-level steps you need to take to use Route 53 for this example. For more information on how to use Amazon Route 53, go to the Amazon Route 53 Getting Started Guide. For instructions on how to route queries to a website that is hosted in an Amazon S3 bucket (not using Amazon CloudFront), go to Routing Queries to a Website That Is Hosted in an Amazon S3 Bucket in the Amazon Route 53 Developer Guide.
To use Amazon Route 53
Create a hosted zone for
Create a new DNS record for your website (e.g.,
points to your Amazon CloudFront distribution (e.g.,
d18k4jybr69gw2.cloudfront.net). Check with your domain name
registrar for instructions on creating a new DNS record.
Confirm your requests are complete.
Update the registrar's name server records.
Make sure you update the CNAME for the Amazon CloudFront distribution if you haven’t already set it.