Senior DevOps Engineer with 8.5+ years of experience. Otherwise an avid artist, reader, cinephile & football fan. Looking forward to connecting with everyone :)
Great analysis Lou! Had a question if you could please weigh in,
Could selecting a cheaper faraway region subsequently prove expensive due to:
a. increased latency affecting the website's speed/functionality?
b. add upto data transfer costs?
c. affect compliance processes that may require data to be stored locally?
Re-thinking developer experience • Product @Gitpod 🍊 Helping folks get their start in cloud • @openupthecloud ☁️ AWS Community Builder 🛠 Replies in GIFS 😃
a. yep, definitely could see some increased latencies, that's your trade-off!
b. I'm no expert in data-transfer costs, but it depends on what, and how much you're transferring and between where, the cost calculator has options for data transfer, so you can get a ball park: calculator.aws/#/createCalculator/... my experience has been that estimating costs is difficult, and the best bet is to run some hands-on tests as soon as possible to see what results you get, but that's always skewed by economies of scale (cheaper, yay!) and also when you bust through free tier amounts (more expensive, boo!).
c. definitely, a victim of the compliance here, gotta do what they say...
Senior DevOps Engineer with 8.5+ years of experience. Otherwise an avid artist, reader, cinephile & football fan. Looking forward to connecting with everyone :)
This does help, Lou. I figured point a would be a trade-off but now I'm more certain.
Point b is indeed tough to estimate but AWS cost explorer helps navigate it. Data transfers can be reduced within VPC & similarly for S3 (where significant data flows in/out). This should help more on the latter.
Being compliant as per point c is tough, remaining so is even more. :D
The infographic/your blog to find the optimum AWS region is the proverbial cherry on the cake, cheers 🍒 🍻
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great analysis Lou! Had a question if you could please weigh in,
Could selecting a cheaper faraway region subsequently prove expensive due to:
a. increased latency affecting the website's speed/functionality?
b. add upto data transfer costs?
c. affect compliance processes that may require data to be stored locally?
Hey Vinay!
a. yep, definitely could see some increased latencies, that's your trade-off!
b. I'm no expert in data-transfer costs, but it depends on what, and how much you're transferring and between where, the cost calculator has options for data transfer, so you can get a ball park: calculator.aws/#/createCalculator/... my experience has been that estimating costs is difficult, and the best bet is to run some hands-on tests as soon as possible to see what results you get, but that's always skewed by economies of scale (cheaper, yay!) and also when you bust through free tier amounts (more expensive, boo!).
c. definitely, a victim of the compliance here, gotta do what they say...
I also published this recently, which might also be useful to you dev.to/aws-builders/how-to-find-wh...
You might also find this infographic useful as a high-level: lastweekinaws.com/wp-content/uploa...
This does help, Lou. I figured point a would be a trade-off but now I'm more certain.
Point b is indeed tough to estimate but AWS cost explorer helps navigate it. Data transfers can be reduced within VPC & similarly for S3 (where significant data flows in/out). This should help more on the latter.
Being compliant as per point c is tough, remaining so is even more. :D
The infographic/your blog to find the optimum AWS region is the proverbial cherry on the cake, cheers 🍒 🍻