- Newest
- Most votes
- Most comments
Based on the information available, it appears that AWS has indeed made changes to the Route 53 console URLs, though there doesn't seem to be widely communicated official documentation or announcements about this change.
-
It seems that the old Route 53 console URLs have been deprecated, as they are no longer functional.
-
Unfortunately, there doesn't appear to be readily available documentation or migration guidance for this change. The lack of communication about this update has caused confusion and disruption for users.
-
Given the situation, it's likely that IAM users will need to manually update their bookmarks to the new URL format. This may involve some inconvenience as users adjust to the new system.
-
The new URL format you discovered (https://us-east-1.console.aws.amazon.com/route53/v2/hostedzones?region=us-east-1#/ListRecordSets/[ZONE_ID]) appears to be the current official format for accessing Route 53 resources in the AWS console.
This change seems to have caught many users off guard, as it impacts existing workflows and bookmarked links. The lack of a redirect or notice about the change has added to the confusion. It's possible that AWS intended to provide a smoother transition but encountered issues in the process.
For now, it's advisable to update all your bookmarks and internal documentation to use the new URL format. You may also want to communicate this change to your team members who work with Route 53.
If you need further clarification or assistance, it might be helpful to reach out to AWS Support directly. They may be able to provide more specific information about the change and any plans for improved communication or transition support in the future.
Sources
route53 problem | AWS re:Post
issue with route 53 | AWS re:Post
Route 53 DNS stopped propagating | AWS re:Post
Blocked from Route 53 since last week - anyone else? | AWS re:Post
Hello.
When I access the following URL that you shared with me from my AWS account, it will redirect me to the V2 hosted zone list.
I did a bit of searching, but couldn't find any information that said the old URLs were no longer valid.
# Accsess
https://console.aws.amazon.com/route53/home?#resource-record-sets:Z1EXAMPLEZONEID
# redirect to
https://us-east-1.console.aws.amazon.com/route53/v2/hostedzones
According to the document below, there are instructions to access the v2 URL.
https://docs.aws.amazon.com/pdfs/awsconsolehelpdocs/latest/gsg/console-help-gsg.pdf
If you use Route 53 to configure your DNS, go to https://console.aws.amazon.com/route53/v2/ hostedzones# to verify the DNS setup. For each Private Hosted Zone in Route 53, verify that the following record sets are present.
Relevant content
- asked 2 years ago
- asked a year ago
AWS OFFICIALUpdated 2 years ago
Thank you for your response. ありがとう
However, our question was about why the old Route 53 console URLs have stopped working and whether there is any official announcement or documentation regarding this change.
There is no issue with IAM policies or access permissions—we are able to access everything correctly using the new URLs. The problem is that the old URLs suddenly became non-functional without any prior notice.
If there is any official guidance or recommendation from AWS regarding this, we would appreciate it if you could share it.
Thank you again for the follow-up.
In our case, the legacy URL does not redirect—it simply fails to load, even for IAM users with the correct permissions. Only when we manually reconstructed the v2 URL from the root account were we able to regain access.
It’s helpful to know that redirection may occur for some accounts, but this inconsistent behavior is exactly why we're raising the issue.
We also reviewed the documentation link you shared. While it does mention the v2 format, it doesn’t clarify whether the older URLs are deprecated, redirect automatically, or should still function.
A definitive statement from AWS about the expected behavior of these legacy URLs would really help clear things up—for us and likely many other users.