Nov 19, 20:17 UTC
This incident has been resolved.
Nov 18, 03:03 UTC
Reverting the code change has been complete and we are observing successful syncs again. All Postgres connectors running WAL replication may have been affected.
We are investigating possible data integrity issues as a result of this incident.
Nov 17, 21:08 UTC
A recent code change in the Aurora Postgres connector has been identified as the root case.
This is being reverted now and will be complete by 2pm PDT.
Nov 17, 19:59 UTC
Users may see the following error in the connector logs:
"ERROR: Function pg_current_xlog_location() is currently not supported for Aurora"
We are currently investigating the root cause. An ETA for a fix will be posted as soon as possible.
Nov 17, 19:18 UTC