RDS Clock Syncing - Aurora PostgreSQL

Question

Hi,
We have encounter a situation with out RDS instances where the clock time appears to be 5 minutes behind the actual time.
i.e. call `select now()` returns a time that is 5 minutes behind a time provided by time.is for our region. Moreover, the fetch time of the query matches the expected time, however the select now() has mentioned earlier is 5 minutes behind.
Does anyone know what could cause this? Is there a way to sync the clocks, or does someone know something to look at to see what my be causing this issue. I have had a look around and I cannot find something, so not sure if I am looking in the wrong place.
Note, we use the default configuration options.

Giovanni Lauria · Answer

In terms of syncing the clocks, the time on an Amazon RDS instance is managed by AWS and cannot be changed by users. This is because time synchronization is critical for the proper operation of replication and other RDS features. If the time drift on your RDS instance is consistently around 5 minutes, it might be worth bringing this to the attention of AWS Support or you work with that offset in mind.

RDS Clock Syncing - Aurora PostgreSQL

Relevant content