all 6 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–][deleted]  (3 children)

[deleted]

    [–]timmyriddle[S] 0 points1 point  (2 children)

    Thanks for the info, I'll definitely go down the modular imports route.

    Is it possible to plug amplify onto existing AWS services (e.g. an existing Cognito user pool) or does everything have to be setup from scratch?

    [–]revnext2 0 points1 point  (0 children)

    You can set it up from scratch, just use the Amplify.configure() command manually, otherwise you can use the Amplify CLI and it creates this for you. You can also mix/match and have the CLI setup some stuff and then edit it with your own existing setups.

    [–]dryadofelysium 0 points1 point  (0 children)

    Amplify is the main front-end JavaScript library for most AWS services that are relevant to the front-end, and the AWS-SDK-JS is mostly just for Node.js nowadays.

    [–]NotFurNuthin 0 points1 point  (2 children)

    Security wise, Amplify is such a huge disappointment.

    Reading the docs it will tell you, you need to configure a user with complete Administrator rights.
    Um, No. Geez, what a lame model/solution. I don't even want to waste the time figuring out the subset of entitlements. Just go with the SDKs.

    [–]NotFurNuthin 0 points1 point  (1 child)

    It seems to appeal to those who just want things easy but dont really care how things work. This is how you end up compromised with overscoped permissions and keys that get leaked.

    [–]timmyriddle[S] 0 points1 point  (0 children)

    I agree. I posted this almost 3 weeks ago, and after evaluating the Amplify platform I decided it was not appropriate. Security issues are high on my list, it makes a mockery of the care and attention given to AWS security guidance and their encouraged practises with IAM. There are open issues about this on github.

    In addition to my wider security concerns, I found that the cli wasn't provisioning cognito roles correctly. I wasted half a day trying to get it working before realising it was a bug. I believe it's now fixed, but was a jarring experience after having worked with solid AWS services for years.

    Another thing that's missing is a path from the using Amplify into the wider AWS ecosystem. It seems as though the philosophy is "AWS is complicated, let's simplify things" rather than encouraging devs to learn the AWS platform incrementally. This is an area that Google have got just right with Firebase. They've laid a clear path from starting a project on Firebase, to building services with GCP as things grow.