Aurora PostgreSQL Replica Pricing

0

Hey guys, I'm wondering what I need to pay for a new on-demand replica instance in the same AZ as the primary instance.

  1. I know I need to pay instance pricing by the hour.
  2. Do I need to pay for the storage of an additional copy of the data?
  3. Do I need to pay for data replication operation? Does data replication to the replica instance count as i/o operations?
jr5043
질문됨 4년 전1544회 조회
2개 답변
0

With Aurora (PostgreSQL and MySQL), when you add a read replica instance to an existing cluster, you are billed for the instance hours based on the instance type you choose for the replica instance. You are NOT billed for additional storage - there is no additional storage for read replica instances in Aurora, as the read replica instances share access to the same Aurora storage volume as the primary read-write instance; as such, data is not replicated to the replica instances.

Thanks for being an Aurora PostgreSQL customer!

-Kevin J, PM for Aurora PostgreSQL

답변함 4년 전
  • Hi! I am not able to find this in AWS documentation. Can you please point me to the relevant link?

0

Here is the conceptual info about how Aurora storage works:

https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Overview.StorageReliability.html

You can think of the writer and reader instances as multiple servers all hooked up to the same hard drive. All the writes happen from one server. The reader instances only transfer data off the shared storage as needed to process queries. The shared storage does 6x duplication behind the scenes for durability. But you are only charged for the one copy of the data.

It's a very different setup than what you find with "traditional" database replication. In "old-style" architecture, all the data gets transferred and stored in duplicate format on multiple servers. There's overhead on the original server to transmit the data everywhere. There's overhead on each replica to process and write out a full extra copy of the data.

With Aurora, the reader instances basically determine which pages need to be evicted from the memory cache due to updates to the underlying storage. That results in less CPU overhead, less network I/O, and less disk writing. The fact that the reader instances are not doing "replication" per se is why the terminology was changed to "writer and reader instances", instead of "Aurora Replicas".

johrss
답변함 2달 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠