Questions tagged with Aurora PostgreSQL

Content language: English

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Hello, Since a Sunday maintenance window, we began to receive ``` ERROR: unexpected pageaddr ``` for all logical replication apps (AWS DMS and Debezium on Kafka Connect). This error is somehow recoverable and periodic: ![DB write instance logs](/media/postImages/original/IMS7FwUZkkRxebe1LNGNEKeA) Otherwise DMS shows no error on this but Debezium kind of fails and recovered by connecting Postgres again. We are wondering if this could be related to Aurora DB minor version update? Or more like we are wrongly using some DB parameters (reboot actually activate the changes). Thanks a lot in advance :). Best regards, David
0
answers
0
votes
4
views
David
asked 14 hours ago
I felt there was a lot of hype around https://aws.amazon.com/about-aws/whats-new/2022/11/amazon-aurora-zero-etl-integration-redshift during the re:Invent and shortly afterward. However, the announcement says that it is only for the Aurora MySQL certain versions, in the US East (N. Virginia) Region, and only a limited preview. The limited preview link is no longer working. I am looking for Aurora PostgreSQL zero-ETL integration into Redshift. Are there any news at all since re:invent? Have I missed anything?
0
answers
0
votes
15
views
asked a day ago
## Issue We have an Aurora PostgreSQL version 14.5 RDS cluster. We have a secret in SecretsManager with credentials for a user we want to rotate the password for. When rotating the secret, the Lambda gets stuck at the `setSecret` step with the error `Unable to log into database with previous, current, or pending secret`. We have determined that this relates to the `password_encryption` option in the cluster parameter group. If we set it to `md5` (whereas the default is, I believe, `scram-sha-256`) the rotation will work again _after_ we update it manually. We can then rotate it as many times as we want. ### Question How can we get the secret rotation to work while using the default cluster parameter group for an Aurora PostgreSQL cluster? ### To reproduce 1. Have a secret [formatted as expected](https://docs.aws.amazon.com/secretsmanager/latest/userguide/reference_secret_json_structure.html#reference_secret_json_structure_rds-postgres). 2. Have a Lambda running the [python code provided by AWS](https://github.com/aws-samples/aws-secrets-manager-rotation-lambdas/blob/master/SecretsManagerRDSPostgreSQLRotationSingleUser/lambda_function.py). 3. Have a version 14.5 Aurora PostgreSQL cluster using the `default.aurora-postgresql14` cluster parameter group. 4. Click the "Rotate secret immediately" button in the console 5. In Lambda logs, see the error `setSecret: Unable to log into database with previous, current, or pending secret of secret arn arn:aws:secretsmanager:....` ### How to Recover 1. Create a new cluster parameter group that is a copy of `default.aurora-postgresql14` 2. Change the `password_encryption` to be `md5` 3. Apply this new parameter group to the cluster 3. Cancel the secret rotation: `aws secretsmanager cancel-rotate-secret --secret-id ....` 4. Manually change the password on the user to a new one 5. Update the secret with the new password 6. click the "Rotate secret immediately" button in the console
2
answers
0
votes
19
views
asked 4 days ago
I have an Aurora Serverless database, which I like to be notified whenever it scales. I've been using a band to do this, and it's fine 99% of the time. But sometimes, it triggers, and the database capacity hasn't changed. Digging into it in cloudwatch, I see this: ![Enter image description here](/media/postImages/original/IMDcxKod5rRkK4UMS1WVNFuw) It looks like the band itself bounces around instead of remaining stable. Can anyone explain this? For now I've switched to a static alarm, so i stop getting 5 messages every night, but this isn't sufficient for longer term and our high load periods.
3
answers
0
votes
31
views
asked 4 days ago
I have created AWS Aurora Read Replica from RDS PostgreSQL Primary database. After creating Aurora Read Replica I have enabled Performance Insights for it, once it is enabled I started using Aurora Read Replica connection string in several places of my application. I was able to see that my application got connected to Aurora Read Replica and all the queries are also getting executed successfully, but while navigating to Performance Insights Tab for Aurora Read Replica I am unable to see anything like Top Users, Top SQL Queries etc. P.S. I have disabled and re-enabled Performance Insights several times to check weather it resolves the issue or not, but no luck.
0
answers
0
votes
22
views
asked 4 days ago
Hi Team, We created Postgres Aurora read replica for Postgres RDS and enabled performance insights for Aurora read replica. In performance insights for this read replica, it is not tracking DB CPU, SQLs, etc. Can you please help how we can track the metrics correctly through performance insights? Thanks, Tushar
0
answers
0
votes
21
views
asked 5 days ago
Hi AWS expert, I have a code read data from AWS aurora PostgreSQL, I want to bookmark the table with custom column named 'ceres_mono_index'. But it seems like the bookmark is still uses the primary key as the bookmark key instead of column 'ceres_mono_index'. Here is the code ```python cb_ceres = glueContext.create_dynamic_frame.from_options( connection_type="postgresql", connection_options={ "url": f"jdbc:postgresql://{ENDPOINT}:5432/{DBNAME}", "dbtable": "xxxxx_raw_ceres", "user": username, "password": password, }, additional_options={"jobBookmarkKeys": ["ceres_mono_index"], "jobBookmarkKeysSortOrder": "asc"}, transformation_ctx="cb_ceres_bookmark", ) ``` How could I fix the issue? Thank you
1
answers
0
votes
36
views
asked 14 days ago
Newer versions of Amazon Aurora PostgreSQL-compatible edition are now available and database cluster(s) running Aurora PostgreSQL minor versions 11.13, 11.14, 11.15, 12.8, 12.10, 13.4, 13.5, and 13.6 need to be upgraded by September 15, 2023. These newer minor versions include important updates that will improve the operations of your Aurora PostgreSQL instances and workloads. We strongly encourage you to upgrade to at least a recommended minimum minor version at your earliest convenience. * For PostgreSQL Minor Version 11.13, 11.14, and 11.15, the recommended minimum minor version is 11.18. * For PostgreSQL Minor Version 12.8 and 12.10, the recommended minimum minor version is 12.13. * For PostgreSQL Minor Version 13.4, 13.5 and 13.6, the recommended minimum minor version is 13.9. Starting on or after 12:00 PM PDT on September 15, 2023, if your Amazon Aurora PostgreSQL cluster has not been upgraded to a newer minor version, we will schedule the relevant recommended minimum minor version to be automatically applied during your next maintenance window. Changes will apply to your cluster during your next maintenance window even if auto minor version upgrade is disabled. Restoration of Amazon Aurora PostgreSQL 11.13, 11.14, 11.15, 12.8, 12.10, 13.4, 13.5, and 13.6 database snapshots after September 15, 2023 will result in an automatic upgrade of the restored database to a supported version at the time. How to Determine Which Instances are Running These Minor Versions? * In the Amazon RDS console, you can see details about a database cluster, including the Aurora PostgreSQL version of instances in the cluster, by choosing Databases from the console's navigation pane. * To view DB cluster information by using the AWS CLI, use the describe-db-clusters command. * To view DB cluster information using the Amazon RDS API, use the DescribeDBClusters operation. You can also query a database directly to get the version number by querying the aurora_version() system function i.e., "SELECT * FROM aurora_version();". How to Apply a New Minor Version You can apply a new minor version in the AWS Management Console, via the AWS CLI, or via the RDS API. Customers using CloudFormation are advised to apply updates in CloudFormation. We advise you to take a manual snapshot before upgrading. For detailed upgrade procedures, please see the available User Guide [1]. Please be aware that your cluster will experience a short period of downtime when the update is applied. Visit the Aurora Version Policy [2] and the documentation [3] for more information and detailed release notes about minor versions, including existing supported versions. If you have any questions or concerns, the AWS Support Team is available on AWS re:Post and via Premium Support [4]. [1] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.html [2] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.VersionPolicy.html [3] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraPostgreSQL.Updates.20180305.html [4] https://aws.amazon.com/support
0
answers
0
votes
65
views
AWS
EXPERT
asked 17 days ago
We are streaming the CDC data using DMS and clients are consuming it. While consuming the DMS event, clients are unable to identify primary key in a DMS event. Do we have any transformation rule of DMS which can add primary key automatically to the DMS event?
3
answers
0
votes
16
views
Sarath
asked 19 days ago
Is there a way we can refresh a limited set of data from Prod AWS account to Dev AWS account PostgreSQL database? For e.g., I have to refresh few rows from couple of tables of Prod to Dev DB. I don't want to do a full refresh of the data using snapshots. Database: AWS Aurora PostgreSQL
2
answers
0
votes
24
views
asked 22 days ago
Hi, I'm trying to create a copy of an Aurora PostgreSQL cluster snapshot in a different region using the aws cli, I was able to do it five times, but now I'm getting the error message **Cannot copy more than 5 snapshots concurrently to the same region**. I suspect that the problem was that I deleted those snapshots while they were being copied and for some reason the status was never updated. ##### Question: do I have to contact the technical support so that they can update the status of the snapshots in the region or is there a way to clean up the snapshots that were deleted before copy them?
0
answers
0
votes
23
views
asked 23 days ago
Would it be possible to setup an Aurora serverless v2 in us-east-1 and have a read replica in another region (us-west-2)? How could we do this via console?
1
answers
0
votes
20
views
asked 24 days ago