Aurora PostgreSQL Major Upgrade 12 to 16 - Do we need to create a new option group before upgrading or one will be created

Question

Hi,

Reading on [https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html]()

It mentions the following:

```
Before upgrading your production Aurora PostgreSQL DB clusters to a new major version, we strongly recommend that you test the upgrade to verify that all your applications work correctly:

Have a version-compatible parameter group ready.

If you are using a custom DB instance or DB cluster parameter group, you can choose from two options:

Specify the default DB instance, DB cluster parameter group, or both for the new DB engine version.

Create your own custom parameter group for the new DB engine version.

If you associate a new DB instance or DB cluster parameter group as a part of the upgrade request, make sure to reboot the database after the upgrade completes to apply the parameters. If a DB instance needs to be rebooted to apply the parameter group changes, the instance's parameter group status shows pending-reboot. You can view an instance's parameter group status in the console or by using a CLI command such as describe-db-instances or describe-db-clusters.
```
SO, we created the DB instance and DB cluster parameter group that for Version 16. Now, we just remember the options group. There is one for 12 named default:aurora-postgresql-12 and we didn't create one for V15, will one be created during the upgrade process for Version 16?

We checked default:aurora-postgresql-12 and it is empty anyway. 
Any feedback will be much appreciated. Thanks in advance.

re:Post Agent · Answer

For Aurora PostgreSQL major version upgrades, you typically don't need to create a new option group before upgrading, and one will not be automatically created during the upgrade process. This is because Aurora PostgreSQL doesn't use option groups in the same way that some other database engines do.

The focus for Aurora PostgreSQL upgrades is primarily on parameter groups, not option groups. You've already taken the correct step by creating new DB instance and DB cluster parameter groups for version 16, which is the recommended approach.

The "default:aurora-postgresql-12" option group you mentioned is likely a default option group, and as you've observed, it's empty. This is normal for Aurora PostgreSQL, as most customizations are handled through parameter groups rather than option groups.

For your upgrade from PostgreSQL 12 to 16, you should continue to focus on ensuring your new parameter groups (both DB instance and DB cluster) for version 16 are properly configured. These parameter groups will be crucial for controlling the behavior of your upgraded database.

After the upgrade, make sure to associate your new parameter groups with the upgraded cluster and instances. You may need to reboot the instances to apply any pending parameter changes, as mentioned in the documentation you cited.

Remember to thoroughly test the upgrade process in a non-production environment before applying it to your production database to ensure all your applications work correctly with the new version.  
**Sources**  
[Upgrading Amazon Aurora PostgreSQL DB clusters - Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.html)  
[Upgrading Aurora PostgreSQL  with Read Replicas from 12 to 16 | AWS re:Post](https://repost.aws/questions/QU4BgALlaDSYqE8ouXwu1f6g/upgrading-aurora-postgresql-with-read-replicas-from-12-to-16)

Aurora PostgreSQL Major Upgrade 12 to 16 - Do we need to create a new option group before upgrading or one will be created

Relevant content