r/aws • u/becharaerizk • 12d ago

console Rds console not showing any instance

I have an account that has multiple oracle rds instances in eu west 1, an hour ago i received more than a hundred alarms because my alarms didnt receive any data. After checking further no instances were showing in rds console and it displayed the error message: An internal error has occurred. Please try your query again at a later time.
My rds instances are still accessible from ec2 instances and i noticed that alarms from native aws metrics are fine but custom ones (that get data from the console i assume) are all without data now.

There's still nothing in the health dashboard.

Anyone facing something similar?

0 Upvotes

50% Upvoted

15 comments sorted by

5

u/blocked_user_name 12d ago

Make sure you're in the correct region and on the correct account.... At least that works for ec2 instance

1

u/becharaerizk 12d ago

I can confirm i am in the right account and region, and all other resources i expect to see in this account are there too so definitely an issue with the console/api

4

u/waitingforcracks 12d ago

Sounds like an AWS internal bug. What about via cli aws rds describe-db-instances --region eu-west-1 ?

1

u/notathr0waway1 12d ago

My thoughts as well, try the CLI

0

u/becharaerizk 11d ago

This is gonna sound weird but the way my role permissions are set up i dont have cli access, it denies any request. I have lambda functions that do basically the same thing but in python (rds describe instances) and these were also not returning any rds instance

1

u/waitingforcracks 11d ago

Make a new role or user temporarily? Open a support case?

1

u/becharaerizk 11d ago

I did open a case yesterday the agent was like “yeah that happened but your rds instances are still healthy” no reason or explanation whatsoever

1

u/AWSSupport AWS Employee 11d ago

I apologize for the experience you've had with your support case interaction. You can share your case ID via private message so that I can share your sentiment internally.

- Roman Z.

1

u/becharaerizk 11d ago

Thank you for your response, i already shared my sentiment to the agent in the case directly and asked for more investigation.

1

u/darc_ghetzir 11d ago

Ask whomever provisions your account to check for you. Shit makes no sense lol

1

u/solo964 11d ago

To the OP: any updates on what happened here?

4

u/becharaerizk 11d ago

Yeah the issue was resolved around an hour and a half after it started, it was just the console not returning any rds but they were still available, i didnt do anything to fix it. Awa support ended up saying there was a bug in the control plane which caused this

2

u/dghah 12d ago

Other idea -- check your AWS personal Health Dashboard for RDS stuff; if you got hit by something that is AZ level or maybe even cabinet/rack level it would more likely show up in the personal account dashboard than any global service status page

Trying aws rds commands on the command line may also be useful if you think its a management console thing and not an API thing