Questions tagged with Amazon Route 53

I purchased a domain name via AWS route 53 that is similar to example.co.uk Is it possible for me to route any traffic from example.co.uk to www.example.co.uk and if so, how do I do so? Or would I need to purchase the www.example.co.uk url from elsewhere.lg...

Hi, I was trying to register a domain name for my association but unfortunately I have received an email says "We weren't able to register the domain name." we can't finish registering your domain. Contact AWS Support at this link Did anybody have the same problem? Kindly help to solve this issue!.lg...

Hello, I'm trying to create a distribution on Cloudfront and S3 and use a domain outside of AWS, with route 53 I can use my domain without problems, but my question is whether it would be possible to use my domain without using Route 53. on the site that hosts my domain, since I don't have ns, it's like something is missing. I can manage to configure the cname from the certificate generated in ACM, the txt and the alias that points to the cloudFront, but I could not configure the ns. So, is Route 53 fundamental in this process?lg...

******J**ust got the following message from AWS. Not sure what to do. As per this notice it says " ChangeResourceRecordSets" in route 53 affects this change. How and and where to upgrade TLS version for it? ******** AWS is updating the TLS configuration for all AWS API endpoints to a minimum of version TLS 1.2. In preparation for this update, we have identified TLS 1.0 or TLS 1.1 connections to AWS APIs from your account that must be updated to maintain AWS connectivity. Please update your client software as soon as possible to use TLS 1.2 or higher to avoid the risk of an availability impact. We are making this change so our customers can benefit from the enforcement and simplification of only modern TLS encryption protocols. This update will remove the ability to use TLS versions 1.0 and 1.1 with all AWS APIs in all AWS Regions by June 28, 2023. Therefore, we recommend considering the time needed to verify your changes in a staging environment before introducing them into production. How can I determine the client(s) I need to update? We have provided the connection details following this messaging to help you pinpoint your client software that is responsible for using TLS 1.0 or TLS 1.1, so you can update it accordingly. Additionally, our related AWS Security blog post [1] provides information on how you can use TLS information in the CloudTrail tlsDetails field. Please see the following for further details on the TLS 1.0 or TLS 1.1 connections detected from your account between February 25, 2023 and March 13, 2023 (the UserAgent may be truncated due to a limit in the number of characters that can be displayed): Region | Endpoint | API Event Name | TLS Version | Connection Count | UserAgent us-east-1 | route53.amazonaws.com | ChangeResourceRecordSets | TLSv1 | 1 | AWSPowerShell/3.1.36.1 .NET_Runtime/4.0 .NET_Framework/4.0 OS/Microsoft_Windows_NT_10.0.14393.0 WindowsPowerShell/5.0 ClientSync us-east-1 | route53.amazonaws.com | ListResourceRecordSets | TLSv1 | 1 | AWSPowerShell/3.1.36.1 .NET_Runtime/4.0 .NET_Framework/4.0 OS/Microsoft_Windows_NT_10.0.14393.0 WindowsPowerShell/5.0 ClientSynclg...

I have a S3 bucket that I have been using to serve up static web pages for a couple of years. I finally decided to get a domain to make it easier to share the location. Following the documentation I tried to create a Simple Record: Record Type: A Value/Route traffic to: Alias to website S3 endpoint Region: US-East (Ohio) [us-east-2] It should then show me available S3 endpoints, but it says "No resources found". The static site is https://kghhome.s3.us-east-2.amazonaws.com/index.html What I have tried so far: - Entering variations of the S3 address in the search bar. - Logging off and back in again. - Waiting 48 hours in case the database mapping the endpoint and user was slow to update. - Logging off and back in a second time. The next thing that I can think of to try is to rebuild the static website in another bucket, but I'm hoping that there is something a little less obnoxious to try first. Thanks, Kailg...

Hi, We registered a domain using AWS and now we are trying to configure ACM and Route53 in order to use it. The certificate is stuck in "Pending Validation" status even if the validation CNAMEs are present the Route53 hosted zone. The hosted zone (and other resources) has been created later (not at the moment of the domain registration) with Terraform using the working code from a previous project. It has been created with different name servers than what I see in the console at the domain details page. Do name servers have to be the same? In order to test the DNS, we added a CNAME record to route test.<domain-name>.com to google.com but it doesn't work. This test works instead with another domain (<domain-name>.live) that is also registered in AWS and managed via Route53. We also tried to run an nslookup on <domain-name>.com and test.<domain-name>.com but it looks like this domain doesn't exist. I already had the same issue with the previous domain because it hasn't been confirmed and then suspended, so my supposition is that there's something wrong with the domain registration process, also because this time the domain has been activate without email confirmation. Is it normal? How can we check if everything is okay with the domain registration, that the domain is active and validate the certificate? Thank you. EDIT: When I run nslookup.io with the root of the *.live domain that is working I can see the name servers:  But when I try with the new one, the name servers don't show up: lg...

The client is from KSA and had to purchase the .sa domain via sahara.net, since AWS does not support it. I want Route 53 to be the DNS service, for convenience and because I want to use the Alias records. I've followed the steps at https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/migrate-dns-domain-in-use.html. I've changed the registrar's NS records to point to the Route 53 hosted zone's servers and, after waiting 24 hours, www.whatsmydns.net tells me the domain points to the correct ones. But the Alias records I added in Route 53 for 2 subdomains pointing to 2 ElasticBeanstalk environments do no work (DNS_PROBE_FINISHED_NXDOMAIN) and I had to add the CNAME for the Amplify main application in the registrar's records before that got validated, even though Amplfy added those records to the hosted zone automatically. It looks like the switch/porting of DNS authority isn't happening. There are records in the registrar's DNS zone that I have yet to add in Route 53. Could those be the reason why it isn't porting over? Can someone give me any advice or tell me what I'm doing wrong?lg...

i want to use all request redirect to https://www.smyro.com.tr My current settings (S3, Route53, Cloudfront) all requested.     | Request Url | Redirect Url | Result | | --- | --- | --- | | http://smyro.com.tr | https://smyro.com.tr | Bad | | https://smyro.com.tr | https://smyro.com.tr | Bad | | http://www.smyro.com.tr | https://www.smyro.com.tr | Good | | https://www.smyro.com.tr | https://www.smyro.com.tr | Good | how can your help me for this problem ? Thanks for all answers.lg...

Hi Route 53 team, I own a domain with the TLD '.app' and would like to transfer it to Route 53. As the TLD is not available for registration/transfer at the moment I request to add the TLD '.app' to Route 53. Thanks in advance.lg...

Now I configured -Route 53 for private hosted zone —add A record with domain name and IP of EC2 -Create EC2 running web-service -vpn client endpoint with split tunnel How Can I use vpn with dns service for call private domain of ec2 ?lg...

Hello, I am trying to use API gateway with a lambda function, but with my own domain (which is on route 53). This is my current config: in API gateway I created a resource with a GET method, and I published it to a stage I called v1. I get an endpoint like ``` https://11111111.execute-api.us-east-1.amazonaws.com/v1 ``` if I call this endpoint I can see the reply from my lambda function. so far so good. Then In API gateway again, I made a custom domain name for api.mydomain.com, and I get something like ``` 22222222.execute-api.us-east-1.amazonaws.com ``` finally in route 53 I created a record type A (api.mydomain.com), marked as ALIAS and with value ``` 22222222.execute-api.us-east-1.amazonaws.com ``` If I try to call https://api.mydomain.com/v1 I get a 403 error. Am I missing something? Also, do I need to enable CORS to allow any browser to call this endpoint?lg...

Hi, When I am creating cloudfront distribution it ask for AWS Certificate , but only in region Virginia, why only in this region? from what I understand cloudfront is global and doesn't have specific region. Thank you lg...