Live data from Hacker News

What is the worst AWS service? I vote for Amplify

blog.astrian.moe

1–10 of 23 posts

Re: What is the worst AWS service? I vote for Amplify

#2
You will face two different methods to create an Amplify project when you use Amplify. This is just the beginning: it will make a bunch of random-named resources on your AWS account, totally untransparent config files in the local or production environment, and the manual (document) that looks so fancy but is split from AWS’s document system and contains almost zero information. You can barely find the config file sample in their document.

Re: What is the worst AWS service? I vote for Amplify

#4
I've used amplify for a thing now, and I wrote a thing to read out the cloud formation they use so I could grab and copy out some of the nice parts while leaving the rest alone and undeployed

It'd be really nice if it was a bunch of CDK constructs you could pull in when you want

I don't know how you actually solve this though, since you don't want to have everything defined across two different languages.

A gql schema defined in CDK maybe would do the trick?

Re: What is the worst AWS service? I vote for Amplify

#8
anecdotally, I'm using it for the studio.

Most of our site is built in react, and hosted on ec2. We use Amplify for the forms. It has a pretty nice UI, and automatically generates dynamo tables and graphQL apis for querying and modifying them. It also integrates with Cognito which is nice.

The best feature though is that you can import Figma components directly. I know Figma generates it's own code, but Amplify packages it up nicely so I can import it via cli.

I wouldn't use it for a personal project, but it is great for allowing non-programmers to contribute components. And the automatic updating dynamo tables is worth using the UI for input forms.

Re: What is the worst AWS service? I vote for Amplify

#10
Yeah, don't use amplify. I once went through the awful experience of less experienced DevOps/devs trying to use it and it was a massive waste. Everything was moved to plain lambda in the end.

Worse even, some parts of Amplify was never published/documented. Reading through just this glue code they were using back then was sufficient to tell that amplify was more of an MVP idea than anything remotely serious.

https://github.com/clushie/aws-amplify-sucks

Post reply on HN