Settings

Theme

How YipitData slashed $2.5M, or 50%, off our AWS bill

medium.com

29 points by jmaccabee 6 years ago · 7 comments

Reader

jmaccabeeOP 6 years ago

We're also happy to try and answer any questions the HN community has on how we did this or why it worked for us

sherlock_h 6 years ago

Did the switch to Ohio change anything with regard to performance?

  • jmaccabeeOP 6 years ago

    We took an initial performance hit as a result of not moving everything to Ohio at once. We moved our EC2 machines first but then saw increased latency between other services like ECR (where we store our Docker images) and Kinesis Firehose that were still in Virginia, so ultimately we moved those too.

    So it wasn't so much that Ohio has worse performance, but that talking to services across region does.

    One note on Firehose specifically for the curious - we make requests to Firehose in Ohio, and then Firehose sends the data to S3 back in Virginia (which we didn't want to move). Normally sending data across regions is expensive, but Firehose actually absorbs the cost in sending the streams to S3. We're honestly not quite sure why, but it worked out great for our costs!

tlevy9 6 years ago

Was there any response from AWS after this?

  • jmaccabeeOP 6 years ago

    Yeah, we found AWS to be helpful throughout the cost optimization process. If you think about it, AWS probably also benefits from happier customers with more sustainable bills since it makes them less likely to look for more cost effective alternatives. It's better for both sides from a long-term perspective

  • stethers 6 years ago

    Nope.

Keyboard Shortcuts

j
Next item
k
Previous item
o / Enter
Open selected item
?
Show this help
Esc
Close modal / clear selection