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

RDS Query Editor not listing RDS Clusters with Serverless v2 instances anymore

4

Hi,

We've been using the AWS Query Editor with no issues up until today for both our Aurora Serverless v1 clsuters and RDS Clusters with Aurora Serveless v2 instances. The dropdown for "Database instance or cluster" used to list both types and we could run queries without any issues. However as of this morning we can only see the Aurora Serverless v1 clusters. All the RDS clusters running Aurora Serverless v2 instances are not listed in the dropdown anymore. The RDS Data API is enabled on all our clusters and we can run queries via aws rds-data execute-statement (just to confirm that the RDS Data API is working fine)

Any ideas on what could be happening ?

Thanks, N.

  • npvisual
    3 months ago

    Looks like access to the Query Editor has now been fixed. However we see some errors for simple "SELECT * FROM table" which worked fine before :

    The result contains the unsupported data type TIMESTAMPTZ.

Topics
ServerlessDatabaseMigration & ModernizationAnalytics
Tags
ServerlessPostgreSQLAmazon Relational Database ServiceAmazon Aurora
Language
English
npvisual
asked 3 months ago385 views
2 Answers
1

I recommend you open a support case.

Have you tried using Data API directly via AWS CLI or AWS SDK [1].

[1] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/data-api.html#data-api.calling

profile pictureAWS
luchobot
answered 3 months ago
  • npvisual
    3 months ago

    Have you tried using Data API directly via AWS CLI or AWS SDK [1].

    Yes, as indicated in the post :

    The RDS Data API is enabled on all our clusters and we can run queries via aws rds-data execute-statement (just to confirm that the RDS Data API is working fine)

  • npvisual
    3 months ago

    Opened a case.

0

Well... Interesting enough, it looks like support was able to resolve the problem in one account, but we're still unable to access the Aurora Serverless v2 instances from the AWS Query Editor in a second account.

I wonder if there was a service-level permission change that happened and if we can manually overwrite that until they get it fixed. So far not great on the support side as the ticket for our second account has been opened for 6 days now and no one was assigned to it.

npvisual
answered 2 months 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.

Guidelines for Answering Questions

Relevant content