Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Blocked from Route 53 since last week - anyone else?

0

I am logging in to the AWS console as the root user. Since last week, I now see an error when I try to access Route 53. That is all we have in our AWS account, just some hosted zones for DNS and now I cannot access them to make DNS changes. Under DNS Management there is the word Error in red and an option pops up to refresh the page but the same error comes up every time. I need DNS access, please help!

  • JZ
    a year ago

    I am also blocked from opening a support case - it gets stuck in a loop, which is why I am asking here.

Topics
Networking & Content Delivery
Tags
Amazon Route 53
Language
English
asked a year ago289 views
2 Answers
1
Accepted Answer

Hello.

What kind of error is being output specifically?
Is it possible to check detailed errors using the browser's developer mode?
For example, if the problem is with your browser, why not try clearing your cache and cookies, or accessing in incognito mode?
Why not try accessing from another PC or another network?

EXPERT
answered a year ago
EXPERT
reviewed a year ago
  • JZ
    a year ago

    There is just the word error. I tried logging in on Chrome in incognito mode and Firefox and saw the same issue.

  • Riku_Kobayashi EXPERT
    a year ago

    Does anything appear when you click the "API error message" toggle shown in the image?

  • JZ
    a year ago

    We have never written an access policy; I am the only user. Not sure why I see these errors:

    User: arn:aws:iam::023004061344:user/jamiez is not authorized to perform: route53:GetHostedZoneCount with an explicit deny in an identity-based policy

    User: arn:aws:iam::023004061344:user/jamiez is not authorized to perform: route53:GetTrafficPolicyInstanceCount with an explicit deny in an identity-based policy

    User: arn:aws:iam::023004061344:user/jamiez is not authorized to perform: route53:GetHealthCheckCount with an explicit deny in an identity-based policy

    User: arn:aws:iam::023004061344:user/jamiez is not authorized to perform: route53domains:ListDomains on resource: * with an explicit deny in an identity-based policy

    User: arn:aws:iam::023004061344:user/jamiez is not authorized to perform: route53domains:ListOperations on resource: * with an explicit deny in an identity-based policy

  • Riku_Kobayashi EXPERT
    a year ago

    I am logging in to the AWS console as the root user.

    You said you were signed in as the root user, but from the error message it appears you are signed in as the IAM user. You are currently signed in using the IAM user "jamiez" instead of the root user. I think there is a problem with the IAM policy set for the IAM user. That error message indicates that the signed-in IAM user is missing a Route53 policy. The AWS account root user is the user who signs in using their email address. You can sign in as the root user by following the steps in the document below. https://docs.aws.amazon.com/signin/latest/userguide/introduction-to-root-user-sign-in-tutorial.html

  • JZ
    a year ago

    Now I feel like an idiot. I did not realize I was in the IAM account. Now I am in the root. I think when I flushed my browser cache, it booted me from the normal root login, but I did not realize it. Thank you for the quick reply.

0

Enter image description here

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content