I am trying to configure ip access restrictions to my public aurora serverless v2 cluster with IAM authentication (postgres). After applying the policy below, I cannot connect to the cluster with the generated token. { "Version": "2012-10-17", "Statement": [ {…
The following procedure is run on a table with 20M records. It stopped at ~560000 and I don't know why. I'm still learning DB monitoring/troubleshooting. This is on Aurora Postgres Serverless v2 with 6 ACUs (12 GB mem). The content…
Just wondering if there are any native AWS options to Orchestrate database scripts which are stored in AWS aurora serverless(postgresql). ex: lets say if we have below three database scripts(functions) that we want to execute in sequence select get_data(); select…
Aurora Serverless V1 was particularly interesting given it offered a relational database that could scale down to 0 units thereby costing nothing if unused - great for development and low traffic services. Aurora Serverless V2 cannot scale down to 0…
My connection handshake times out when trying to connect to my RDS Aurora Serverless (v1) MySQL Cluster from an external source. I'm specifying the cluster and its security group in terraform, and leveraging the default AWS VPC for the account/region.…
I do not see option to have a cluster with two writers in serverless v2 for both Amazon Aurora MySQL-Compatible Edition Amazon Aurora PostgreSQL-Compatible Edition Now UI propose us to create a read replica for faster failover. But is it…
I'm following terraform documentation to create Aurora serverless v2 by terraform. https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/rds_cluster#rds-serverless-v2-cluster In terraform documentation, they have not mentioned how to create Aurora serverless v2 with multi AZ (read replica in other region for failover). Although, by aws console, I…
I am using RDS Aurora Postgres Cluster with only one writer instance of type Serverless v2 and the capacity is set to 1 -16 ACUs. I tried to perform "restore point in time" on this cluster, however I get this…