1 Answer
- Newest
- Most votes
- Most comments
1
Hello Atefeh,
It sounds like you're dealing with a mismatch between your RDS engine version and parameter group family after an unsuccessful upgrade attempt. This is a common issue when upgrading database engines, especially when the parameter group was created via a template. Try the following via the AWS Console to see if we can get you back up and running quickly:
Solution Steps
-
Create a new parameter group matching the upgraded engine version:
- Navigate to the RDS console parameter groups section: https://us-east-1.console.aws.amazon.com/rds/home?region=us-east-1#parameter-group-list: (assuming us-east-1, change as needed)
- Click "Create parameter group"
- Select the appropriate engine type (e.g., PostgreSQL)
- For Parameter group family, select the version that matches your upgraded engine (e.g., postgres17)
- Provide a name and description
- Click "Create"
-
Configure the new parameter group with your custom settings:
- You'll need to copy any custom parameters from your original parameter group to the new one
- You can view your current parameter group settings and replicate them
-
Modify your RDS instance to use the new parameter group:
- Select your RDS instance in the console
- Click "Modify"
- Under "Additional configuration", find "Database options"
- Select your newly created parameter group from the dropdown
- Choose an appropriate apply method (immediately or during maintenance window)
- Click "Continue" and confirm the changes
-
Reboot the instance if necessary:
- Some parameter changes require a reboot to take effect
- Monitor the instance after modification to ensure it's functioning correctly
Let us know if this realigns the parameter group with the upgraded engine version.
answered 24 days ago