If that's not a large node for you, well you're living in a different world from me. Yes to using EBS.
If that's not a large node for you, well you're living in a different world from me. Yes to using EBS.
You would just have to setup replication for backups, but this could just be rsync to EBS or some other replication solution depending on your database.
Then there’s the x-family, which can go up to bonkers levels, like 4 TiB of RAM (and local NVMe).
As a sibling comment mentioned, though, if you can fit the data into local storage, that’s the way to do it. EBS latency, even with io2.blockexpress, simply cannot compete.
That said, if I did the math correctly based on the 71 GB/31 days footnote, you’re looking at about 2.15 PB to load the entire thing, so, uh, good luck.
At my last job, I switched a large-ish (100K QPS at peak) m5 MySQL instance to a smaller (in AWS numbering) r6i that was cheaper, despite having the same amount of RAM and being generation newer. That, combined with careful tuning and testing, resulted in queries speeding up 20-40%, AND we then had plenty of room for vertical scaling again if necessary.
EDIT: only newer C instances have comparable uplink to EBS, C5 or C4 (and some C6) starts from ~4.7gbps. just compare the EBS bandwidth column in https://aws.amazon.com/ec2/instance-types/
This rarely matters until it does, like if you’re setting up an active-active DB across regions. Then it’s a fun surprise.