Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Apr 19, 2021 - 12:00 PDT
Update
There is a change in the configuration for the Postgres 2.0 Service in the US-West environment. After this change you will be required to choose encryption-at-rest option and set it to true when creating a new Service Instance.
Please note that depending on your workload, enabling encryption-at-rest can impact the performance of your Postgres 2.0 instance anywhere between 0% to 8%. Also, note that enabling encryption-at-rest doesn't require any code or configuration change in your applications connecting to the Service Instance.
Existing Postgres 2.0 Instances that are not currently encrypted-at-rest will be modified to enable encryption-at-rest. This modification will be performed between Apr 19, 2021 12:00 PM PT and May 2, 2021 12 PM PT during a weekly maintenance-window of the respective Postgres 2.0 Instance, usually it is 30 Min. The DB Instance will be unavailable for application connections during this modification.
Example command to create a Postgres 2.0 Service Instance with encryption-at-rest enabled:
To see whether your Postgres 2.0 Instance is encrypted-at-rest and what is the DB Instance’s maintenance-window, please see the section “Credentials” at the following link.
There is a change in the configuration for the Postgres 2.0 Service in the US-West environment. After this change you will be required to choose encryption-at-rest option and set it to true when creating a new Service Instance.
Please note that depending on your workload, enabling encryption-at-rest can impact the performance of your Postgres 2.0 instance anywhere between 0% to 8%. Also, note that enabling encryption-at-rest doesn't require any code or configuration change in your applications connecting to the Service Instance.
Existing Postgres 2.0 Instances that are not currently encrypted-at-rest will be modified to enable encryption-at-rest. This modification will be performed between Apr 19, 2021 12:00 PM PT and May 2, 2021 12 PM PT during a weekly maintenance-window of the respective Postgres 2.0 Instance, usually it is 30 Min. The DB Instance will be unavailable for application connections during this modification.
Example command to create a Postgres 2.0 Service Instance with encryption-at-rest enabled:
To see whether your Postgres 2.0 Instance is encrypted-at-rest and what is the DB Instance’s maintenance-window, please see the section “Credentials” at the following link.