
The “Source” column shows how the value for a parameter is determined: “engine-default” will inherit the default value based on that version of the PostgreSQL engine, while “system” indicates that the value of this parameter varies by instance class.

In the example below, we are inspecting the default parameter group for version 9.6 of PostgreSQL: default.postgres9.6). You can learn more about each parameter in your database instance’s parameter group by navigating to “Parameter groups” in the RDS Console. You can either use a default version-specific parameter group, or you can create a custom parameter group that is based on a default parameter group. Many of these settings can be modified, while others (such as wal_sync_method) cannot. In RDS, the PostgreSQL primary server is known as a source/primary instance, and configuration settings are called parameters.Įach RDS database instance is assigned to a parameter group, which is a collection of settings that you would normally specify in your nf configuration file. In RDS, you can launch one or more database instances, each of which manages/hosts one or more databases. Amazon RDS PostgreSQL overviewīefore diving into the key metrics for monitoring PostgreSQL on RDS, let’s briefly walk through some terminology, as it relates to PostgreSQL and RDS. It also provides the option to set up automated database snapshots and point-in-time recovery if you should ever need to restore a database instance to an earlier state.


RDS enables PostgreSQL users to easily implement high-availability deployments, which we’ll explore in further detail later in this post. This article will focus on monitoring Amazon RDS PostgreSQL database instances. RDS provides users with six database engines to choose from: PostgreSQL, MySQL, Oracle, SQL Server, MariaDB, and Amazon Aurora. Amazon Relational Database Service (RDS) is a managed service that helps users easily deploy and scale relational databases in the AWS cloud.
