I think I was wrong about AWS Amplify

54,028
0
Published 2023-04-26
buckle up, this one is a long rant

00:00 aws amplify complaints
13:03 sst overview
29:32 random rant about vercel
29:58 random rant about OSS

πŸ“˜ T3 Stack Tutorial: 1017897100294.gumroad.com/l/jipjfm
πŸ€– SaaS I'm Building: www.icongeneratorai.com/

πŸ’¬ Discord: discord.gg/4kGbBaa
πŸ”” Newsletter: newsletter.webdevcody.com/
πŸ“ GitHub: github.com/webdevcody
πŸ“Ί Twitch: www.twitch.tv/webdevcody
πŸ€– Website: webdevcody.com/
🐦 Twitter: twitter.com/webdevcody

All Comments (21)
  • @WebDevCody
    I wanted to say that Amplify isn't awful. I made this video after spending hours debugging, and I was a bit pissed off. I'm assuming the developers working at AWS and Amplify are trying their best to make a good product; sometimes internal processes at a corporation get in the way of shipping features, and the bugs and features WE as users find important might not be prioritized inside the company due to various reasons. Amplify is still a good solution to deploy a next application, and my ONLY complaint so far was this cookie cache issue. If I wasn't using google analytics, I would have never thought twice into investigating all of these cloud front misses. This issue made me realize that abstracting away your infrastructure comes with a cost. If you are interested in having more control over your AWS infrastructure, maybe check out SST, CDK, and Terraform. IaC is another really fun aspect of cloud computing I recommend people at least try at some point once they progress in their skills.
  • As a newbie who tries to build full-stack applications, I like your honest, realistic approach and process of thinking with respect to price. I'm learning many things from your channel!
  • You have no idea how valuable your channel is for up and coming junior devs like me. Would love to see a cost-breakdown of AWS costs using SST.
  • @svenhofstede
    This was a brilliant walkthrough of your troubleshooting. Awesome stuff!
  • @TerryDellino
    Really looking forward to future videos on how you are using SST
  • @TheEchinox
    Love this! Didn't even know I wanted to see cloud architecture debugging-style tutorials! Keep it up!
  • Hey Cody! Thanks for bringing this up. Your concerns have been heard by our Amplify team!
  • @kelvinxg6754
    I love you are going through real issues. i learned a lot from your video. anyhow i hope they'll get it fixed soon.
  • @Paul_Aderoju
    Amazing work! Learned new debugging techniques just from this video. Thank you πŸ™
  • @pranav.bhasin
    This was so detailed and in-depth. Loved hearing your insights on AWS Amplify
  • Great video. Nice to see real-life examples and how you think through solving problems. I don't use any AWS services but was thinking of exploring it. Biggest fear is setting things up wrong and being over charged.πŸ˜…
  • @lilililliilil
    This video seems to be very informative and valuable to many developers. Thank you for taking the time to go through all of this and sharing it. It's impossible not to subscribe after watching.
  • @Nurof3n_
    appreciate the amount of hours you put into debugging this and sharing it with us πŸ™Œ
  • @Goyo_MGC
    Great analysis on the all the "easy to use" services. Often times simplicity of use of a services comes with the price of less customizable product. Always great to know what are the limitations of a product. It is exactly what makes a good engineer in my opinion, knowing the limitations and deciding on the better product depending on the need. Always looking forward to your new videos. Cheers
  • @alexiscoding
    I loved your in depth on this video. I think I understand AWS and NextJs a little more, thanks to you
  • @thesobercoder
    SST is one of the coolest tech I've come across recently. Totally democratizing you to host on AWS without being tied to Vercel. I'm seeing numerous videos popup recently about people moving away from Vercel for various reasons, one among them is bandwidth charges after you consume the free tier.
  • @_Aarius_
    Its been a while since I modified the cloudfront dists at my work, but I believe you can set up edge functions to modify inbound and outbound requests? You could use those to strip cookies out at the cf end rather than in amplify