#AURORA POSTGRES VERSIONS UPGRADE#
#AURORA POSTGRES VERSIONS CODE#

#AURORA POSTGRES VERSIONS UPGRADE#

If the IsMajorVersionUpgrade value is true, you can do a major version upgrade to the associated EngineVersion. It shows the value of the ValidUpgradeTarget array containing the target versions. The following screenshot shows the output from the preceding command in a Linux-based operating system. To get a list of all valid upgrade targets for a current source version, use the describe-db-engine-versions CLI command.įor Linux, macOS, or Unix, use the following code:Īws rds describe-db-engine-versions -engine aurora-postgresql -engine-version 9.6.16 -query 'DBEngineVersions.ValidUpgradeTarget' If your database isn’t at a version that is supported by Graviton2, you need to upgrade to a supported version.

The following table shows the supported versions for Graviton2 as of this post these are the versions of the database that were compiled or developed and tested to be compatible with Graviton2.įor our use case in this post, we use Aurora PostgreSQL version 9.6.16, which is lower than the version required to move to Graviton2.įor the latest updates of this information, see Supported DB engines for DB instance classes (Amazon RDS) and Supported DB engines for DB instance classes (Aurora). This is an optional step and only required if the current database version does not meet the minimum required version for moving to Graviton2, so we start by determining if we need to upgrade the database version. Validate and confirm that the application works correctly.Modify the instance class of your instances to the appropriate Graviton2 instance.Determine your strategy and the order in which to modify your instances.Upgrade the database engine to the required minimum version.

Determine if the current database version meets the minimum required version for moving to Graviton2.

The high-level steps in the process are as follows: Then modify your non-production instance to Graviton2 followed by validation tests to make sure everything is configured and operating as per your expectations. You can start by using a snapshot of your production database and restoring it into an instance in your non-production environment, which has a similar configuration (instance class, parameter group settings, encryption) as the current production instance. The steps that you take for modifying your instance type is similar for both Amazon RDS ( Amazon RDS for MySQL, Amazon RDS for PostgreSQL, Amazon RDS for MariaDB) and Aurora ( Aurora MySQL and Aurora PostgreSQL).įor this post, let’s consider a use case in which we have a Multi-AZ Aurora database cluster at PostgreSQL version 9.6.16 with three instances: one writer and two readers.Īs a general best practice, it’s recommended to test the process in a non-production environment.

#AURORA POSTGRES VERSIONS CODE#

No porting or code changes are required when migrating from Intel to Graviton2 instances on Amazon RDS and Aurora.Graviton2 processors feature always-on fully encrypted DDR4 memory and 50% faster per core encryption performance.Graviton2 instances provide seven times the performance, four times the number of compute cores, two times larger private caches per core, five times faster memory, and two times faster floating-point performance per core over the first-generation AWS Graviton processors.They also provide up to 35% price/performance improvement for Aurora depending on database size. Graviton2 instances provide up to 52% price/performance improvement for RDS open-source databases depending on database engine, version, and workload.The following are some of the reasons for moving to Graviton2 for Amazon RDS and Amazon Aurora:

We discuss the prerequisites and different strategies that you can take to reduce downtime. In this post, we discuss key considerations when modifying existing RDS and Aurora DB instances to Graviton2 based instance types. You can move Multi-AZ databases to Graviton2 with minimal downtime, suspending I/O for the duration of a failover. You can launch new Graviton2 M6g and R6g database instances via the Amazon RDS console or the AWS Command Line Interface (AWS CLI). Graviton2 processors are custom built by AWS using 64-bit Arm Neoverse cores, and deliver several optimizations over first-generation AWS Graviton processors. In 2020, AWS announced Amazon M6g and R6g instance types for Amazon RDS and recently announced the general availability of R6g instance type for Aurora powered by AWS Graviton2 processors, which offers a better cost-performance ratio compared to their x86 counterparts. Amazon Relational Database Service (Amazon RDS) and Amazon Aurora support a multitude of instance types for you to scale your database workloads based on your needs (see Amazon RDS DB instance classes and Aurora DB instance classes, respectively).

Aurora postgres versions