I can't find DB cluster parameter group for postgres17

Question

I'm so excited that [RDS finally supports Postgres 17](https://aws.amazon.com/ko/about-aws/whats-new/2024/11/amazon-rds-postgresql-supports-version-17/), so I'm trying to upgrade the existing multi AZ cluster Postgres 16 to 17.

And I'm going to use logical replication, so I need to create a custom parameter group.

Unfortunately, if I try to create a parameter group and select postgres16 I can select *DB cluster parameter group*, but if I select postgres17 *Type* doesn't appear so I can't create a cluster parameter group.

When I go to Modify page of the db cluster and change *Engine version* to *PostgreSQL 17.1-R1*, *DB cluster parameter group* is automatically set to *default.postgres17*. But *Parameter groups* > *Default* shows me that there is only one *default.postgres17* and the type of it is *DB **instance** parameter group*, not *DB cluster parameter group*, which I find confusing.

Does it mean that it's OK to use instance parameter group for postgres17 cluster? Or maybe the cluster parameter group for postres17 is not ready yet?

anish_g · Accepted Answer

Hi,

It could be an UI issue. Please try to create the RDS PostgreSQL 17 DB cluster parameter group through cli command and then you should be able to edit/update in the RDS console

```
$aws rds create-db-cluster-parameter-group   --db-cluster-parameter-group-name mydbclusterparametergroup --db-parameter-group-family postgres17 --description "My new cluster parameter group"             
{
    "DBClusterParameterGroup": {
        "DBClusterParameterGroupName": "mydbclusterparametergroup",
        "DBParameterGroupFamily": "postgres17",
        "Description": "My new cluster parameter group",
        "DBClusterParameterGroupArn": "arn:aws:rds:us-east-1:111111111111:cluster-pg:mydbclusterparametergroup"
    }
}
```
Reference for aws cli command to create custom cluster parameter group,
https://docs.aws.amazon.com/cli/latest/reference/rds/create-db-cluster-parameter-group.html

re:Post Agent · Answer

The situation you're describing is indeed confusing, and it appears there might be a temporary inconsistency or delay in the full rollout of PostgreSQL 17 support for Amazon RDS, particularly regarding DB cluster parameter groups.

In a Multi-AZ DB cluster deployment, typically a DB cluster parameter group is used to apply configuration values to all DB instances in the cluster. However, based on your observation, it seems that for PostgreSQL 17, the system is currently defaulting to a DB instance parameter group instead of a DB cluster parameter group.

This behavior could be due to one of two reasons:

1. There might be a temporary lag in the full implementation of PostgreSQL 17 support, including the creation of DB cluster parameter groups. AWS sometimes rolls out features gradually, and it's possible that the DB cluster parameter group for PostgreSQL 17 is not yet available.

2. There could be a change in how parameter groups are managed for PostgreSQL 17 in Multi-AZ clusters, though this would be unusual given the typical architecture of Multi-AZ DB clusters.

Given that the system is allowing you to proceed with the upgrade and is automatically assigning a default.postgres17 parameter group (even though it's an instance parameter group), it suggests that this configuration should work for your cluster. However, this is not the expected behavior based on how Multi-AZ DB clusters typically operate.

To ensure you're proceeding correctly, I would recommend the following steps:

1. Double-check that you have the latest version of the AWS console, as sometimes updates can resolve such inconsistencies.

2. If the issue persists, it would be advisable to contact AWS Support for clarification. They can provide the most up-to-date and accurate information about the current state of PostgreSQL 17 support and parameter group management for Multi-AZ clusters.

3. If you decide to proceed with the upgrade using the instance parameter group, closely monitor your cluster's behavior after the upgrade to ensure all parameters are applied correctly across all instances in your Multi-AZ setup.

4. Keep an eye out for any AWS announcements or updates regarding PostgreSQL 17 support, as they may address this issue in the near future.

Remember, when dealing with database upgrades, especially to a newly supported version, it's always a good practice to test thoroughly in a non-production environment first.  
**Sources**  
[Amazon RDS for PostgreSQL now supports major version 17 - AWS](https://aws.amazon.com/about-aws/whats-new/2024/11/amazon-rds-postgresql-supports-version-17/)  
[Multi-AZ DB cluster deployments for Amazon RDS - Amazon Relational Database Service](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/multi-az-db-clusters-concepts.html)

I can't find DB cluster parameter group for postgres17

Add your answer

Relevant content