- Newest
- Most votes
- Most comments
Dear AWS Customer,
Aurora PostgreSQL versions 17.4, 16.8, 15.12, 14.17, and 13.20 completed deployment in all commercial regions on April 7. An issue was introduced in these versions which can result in database restarts and/or failovers. We have decided to disallow the creation of new clusters and upgrade of existing clusters to these versions while we work on a fix, and they are no longer selectable as creation or upgrade targets. We are going to rollout a new patch release which is expected to complete in all commercial regions by approximately the beginning of May.
Sincerely, The Amazon RDS Team
Based on the information provided, it appears that Aurora PostgreSQL version 16.8 is indeed no longer available in the af-south-1 and eu-west-1 regions, while it remains available in us-east-1. This situation is unusual and could be due to several factors:
-
Regional rollout: AWS sometimes rolls out new versions to different regions at different times. It's possible that version 16.8 was temporarily available in your regions but has been pulled back for some reason.
-
Version deprecation: In rare cases, AWS might deprecate a specific version if critical issues are discovered. However, this is unlikely for a recent version like 16.8.
-
Regional differences: AWS occasionally has different version availability across regions due to various factors such as regional infrastructure or compliance requirements.
For your existing clusters that were upgraded to 16.8, they should continue to function normally. AWS typically doesn't force downgrades of running instances even if a version is no longer available for new deployments.
Regarding your Terraform (or OpenTofu) code, you'll need to update it to use a version that's available in your target regions. Based on the output you provided, version 16.6 is the latest available version in both af-south-1 and eu-west-1.
To resolve your immediate issue, you could modify your data source to use version 16.6:
data "aws_rds_engine_version" "postgresql" { engine = "aurora-postgresql" version = "16.6" }
It's recommended to check the AWS documentation or contact AWS support for the most up-to-date information on version availability and any potential issues with version 16.8. They may be able to provide more specific information about why this version is no longer available in your regions and when (or if) it will be re-introduced.
In the meantime, for new cluster creations, you'll need to use version 16.6 or another available version in your target regions. Keep monitoring AWS announcements and documentation for updates on Aurora PostgreSQL version availability in your regions.
Sources
Getting a list of available versions in your AWS Region - Amazon Aurora
Amazon Aurora versioning - Amazon Aurora
Relevant content
- asked 3 months ago
- asked 7 months ago
- asked 2 years ago
- asked 3 months ago
Ah, great, thank you
@Koushik_D can you elaborate on this issue please? Is the issue the same for all of the versions you've listed? Under what conditions were databases using these newer versions restarting and failing over?