Hi,

I've a question regarding multianswer routing policy as per the document below
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-values-alias.html#rrsets-values-alias-alias

I wanted clarification if at the zone apex , can we create a Non Alias record , if routing policy
is MultiAnswer ?

If we select Non Alias , it does create a record for us but in documentation above
you have mentioned that ONLY ALIAS records can be created at zone apex / naked domain.

Note: This is not for record "type" but for the DNS record itself.

Please clarify .

Thanks
Himanshu

I am trying to route traffic to a cloudfront distribution and i was following the document. As stated i selected the Alias to cloudfront distribution from the dropdown but from there i am not able to selcet my region as N.Virginia is hardcoded in the region dropdown. Is there something i am missing

The documentation for domain-delete contains the following language:

Important
If you delete a domain name registration before the registration was scheduled to expire, we will not refund the registration fee.

This suggests that domain registrations can be refunded. I have, however, confirmed with the AWS Support Team that domain registrations are one of the few Route53-related transactions that cannot be refunded.

The Amazon Route 53 Developer Guide includes oodles of information about how to use Route 53 to register domains, configure DNS, and create health checks. There are bound to be topics that we haven't covered yet, though. Tell us what you'd like to see in the Route 53 documentation, and we'll do our best to add it. Suggest future content by opening a New issue, entering the details of your request, tagging it "Enhancement," and then clicking Submit new issue.

Thanks for the help.

The page for configuring health checks for private zones seems to have a very peculiar recommendation:

"You can configure a health checker to check the health of an external resource that the instance relies on, such as a database server."

You may want to choose a different example, this one could confuse less security focused people and encourage them to do something like expose a database to the internet so that it can be used for a DNS health check.....

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-private-hosted-zones.html

It would be useful to have some details about the nuances of the Health Checker documented.

After enabling compression on our application we had to determine through trial and error that a Health Check with SearchString does not support Brotli encoding but does support Gzip. The only documentation I saw was that the string needed to be in the first 5120 bytes of the response and that headers needed to be RFC compliant. AWS Support tried to be helpful but it seems they were armed with the same documentation I was.

In this particular instance it would have helped if I had known:

• The User-Agent used by Route53 health checks. After googling this I see that it has changed at least once in the past. Knowing the User-Agent I can add some checks to only return Gzip for Route53 while using more efficient Brotli for modern browsers and clients. The current User-Agent looks like Amazon-Route53-Health-Check-Service (ref $GUID; report http://amzn.to/1vsZADi
• What the actual accepted encodings are. My application was receiving Accept-Encoding: *, which is fine for simply checking HTTP response status, but perhaps something like Accept-Encoding: gzip, identity would be more appropriate when StringSearch is enabled.

I'm sure there are other details about the request and response which could be useful to include.

Hi there,

I've followed this tutorial and cannot get it working properly.

Whenever I resolve my url it brings up the url of the eb environment and renders the certificate unsafe. Could you please update the docs to reflect that it is not possible to have a subdomain with an SSL?

Hi

I followed the instructions for creating a static site with a custom domain in an S3 bucket. However, I found some steps confusing and it took some troubleshooting. In particular, step 12 in this topic: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/getting-started-s3.html#getting-started-create-alias

Here are some issues that might benefit some further attention:

• "The bucket name should match the name that appears in the Name box."
  I don't see any "Name" box in the Define simple record dialog. I was confused about what Name box you are referring to here.

• "In the Choose S3 bucket list,..."
  I didn't see any Choose S3 bucket list. There is a text field with the words "Enter S3 endpoint" as placeholder text, perhaps this is the text that should be referenced in the step? I feel like the page was updated but the instructions might be out of date.

• Finally, I missed this note that indicates that your bucket name must be the same as your record name for the two to resolve:
  "The bucket name is the same as the name of the record that you're creating."
  I feel like this should be noted when you are creating the bucket. For example: "Note: The name of your bucket must match the name of the domain you create in step one."
  I created a domain, let's call it my-sample-domain.com. Then I created a bucket and called it: myWebsiteFiles. But when I went to route DNS traffic to the bucket, I found that the bucket has to have the same name as the record. The record will have the same name as the domain. And so I had to delete the bucket and create a new bucket called my-sample-domain.com. Then it worked.

I am happy to fork and create a pull request to work on suggested changes. Please let me know if you can reproduce this or I misunderstood your steps.

Thanks

Ronan

Hi,
I was trying to create a resolver endpoint with the exact policies and actions, and then I face a problem, the required actions as per the docs are given below.
CreateResolverEndpoint
Required Permissions (API Action): route53resolver:CreateResolverEndpoint, ec2:DescribeSubnets, ec2:CreateNetworkInterface, ec2:DescribeNetworkInterfaces, ec2:CreateNetworkInterfacePermission, ec2:DescribeSecurityGroups

But it was not working, it's throwing me a not authorized error, So I search for more actions that require to complete the job, and found that it requires more actions, below are the required actions.

ec2:DescribeNetworkInterfaceAttribute
ec2:DescribeNetworkInterface

This will be very helpful if you verify and add those actions to the docs.

Thank in advance.

The following action is a typo in the aws documentation:
route53:route53resolver:AssociateResolverEndpointIpAddress

The above should be :
route53resolver:AssociateResolverEndpointIpAddress