RDS for PostgreSQL supports read replicas.
In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and service performance may be affected. To offload read pressure on the primary DB instance, you can create one or more read replicas in the same region as the primary instance. These read replicas can process a large number of read requests and increase application throughput. You need to separately configure connection addresses of the primary DB instance and each read replica on your applications so that all read requests can be sent to read replicas and write requests to the primary DB instance.
A read replica uses a single-node architecture (with no standby node). RDS synchronizes changes from the primary instance to all read replicas using the native PostgreSQL replication. If network latency on the primary instance is high, data synchronization between the primary instance and the read replicas will be affected. Read replicas and the primary DB instance must be in the same region but can be in different AZs.