TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

AWS Amplify Console

12 pointsby lfxover 6 years ago

1 comment

talawahtechover 6 years ago
This is useful, and long overdue. Trying to deploy a single page app or static site using S3 + CloudFront is way more complex than it should be. Trying to automate deployment using CodePipeline is a real pain. By the time you start to think about cache invalidation, most people have already given up and started looking at Netlify or Firebase hosting. The fact that they handle things like atomic deploys and password protection for dev branches is icing on the cake.<p>I do wish the data transfer pricing ($0.15&#x2F;GB) were a little lower, though it is the same as Firebase hosting who I guess they are positioning themselves against. The pricing is simpler that CloudFront pricing which varies by region, but ends up being a worse deal for those whose customers are primarily in North America ($0.085&#x2F;GB on CloudFront) and a better deal for those in India ($0.17&#x2F;GB) and South America ($0.25&#x2F;GB). Push come to shove, if you need to reduce costs I guess you can always try sticking Cloudflare in front of it and seeing what the performance looks like.<p>They are still not doing a great job on the product marketing side of things though. Why is it called Amplify Console instead of Amplify Hosting? In my opinion they should really just take a look at how Firebase positions their suite of products. Amplify Framework, amplify-cli and Amplify Console is a confusing and counter-intuitive mix.