Amplify-cli: Aurora serverless Postgresql not supported

Created on 26 Dec 2019 · 14Comments · Source: aws-amplify/amplify-cli

Running amplify api add-graphql-datasource will fetch my Aurora PostgreSQL cluster, then the secret, and then crashes:

? Select the secret used to access your Aurora Serverless cluster: RDSRootSecret
⠼ Fetching Aurora Serverless cluster...BadRequestException: FATAL: database "root" does not exist
    at Object.extractError (/usr/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/protocol/json.js:51:27)
    at Request.extractError (/usr/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/protocol/rest_json.js:55:8)
    at Request.callListeners (/usr/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
    at Request.emit (/usr/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
    at Request.emit (/usr/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:683:14)
    at Request.transition (/usr/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/usr/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /usr/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/usr/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/usr/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:685:12)
There was an error adding the datasource

The reason is my database user is called root and there is no database root, it just has a different name.

What I would expect is that it does not switch to the postgresql default database (which is the name of the user), and continues to show me all my databases.

Desktop

Amplify cli: 4.7.0
- Ubuntu 19.10
- Node Version: 10.18.0

feature-request pending-review

Source

berenddeboer

👍5

Most helpful comment

Dear Amplify devs,
This issue (along with the one allowing the addition of multiple AWS resources arbitrarily) was one of the factors by which our company determined that Amplify was simply too immature (and opinionated) to be ready soon enough for our enterprise-scale apps...

We'd love to see this one day become production ready. Until then we will be consuming our AppSync graph with core/vanilla Apollo. ^_^

Genkilabs on 6 May 2020

👍8

All 14 comments

Are you sure your db is active? Can you use the Online Query Editor to send requests and works?
I had a simular issue and then I realised that amplify cannot wake up the database if it is inactive.

Ricardo1980 on 26 Dec 2019

Have changed the title, the issue is that Aurora Postgresql is not supported. Look at appSync-rds-walkthrough.js, method selectDatabase(), mysql is hard-coded.

berenddeboer on 26 Dec 2019

Had a bit of a look to see if I could support Postgres, but I would need to determine what kind of cluster this is, i.e. its engine. Couldn't see this easily. Anyway, for Postgres instead of show databases you want SELECT datname FROM pg_database.

berenddeboer on 26 Dec 2019

See #1914 as well.

berenddeboer on 27 Dec 2019

@berenddeboer I will mark this as a feature request, our PR will review it.

UnleashedMind on 27 Dec 2019

👍4 👀1

+1 for feature

See more history on this issue/desire as well here: https://github.com/aws-amplify/amplify-cli/issues/2423#issuecomment-536077162

Genkilabs on 27 Feb 2020

Any progress in this feature?

azatoth on 6 Mar 2020

any new updates? a must needed feature for my application

jameelgrand on 13 Mar 2020

How can I upvote this, I'd LOVE this ability in postgres, it could change the whole project I'm working on.

deanthemachine2 on 22 Apr 2020

👍6

We'd love to see this one day become production ready. Until then we will be consuming our AppSync graph with core/vanilla Apollo. ^_^

Genkilabs on 6 May 2020

👍8

+1 for support

I'll acknowledge the following:

Amplify is a toolkit to help automate as much of the full stack development process as possible.

Having used AppSync for managed GraphQL, we decided to use the Amplify CLI since it appears to be a great tool for managing / creating multiple environments. Since we're leveraging multiple types of data sources, you might think that the Amplify CLI should support data model management for those data sources (since Amplify is meant to manage everything for you, mostly...). However, we've actually used an Aurora Serverless Postgres database as a source of data (zipcodes, distance, etc.). We don't mind keeping the data model and resolvers for Queries/Mutations in sync ourselves, but functionality would be very nice to mark a data source as "self-managed" so when our resolvers are replicated for new environment creation they will work automatically (since the resolvers are stored to /amplify/backend/api/NAME/resolvers/).

I would propose something like amplify api add-graphql-datasource --managed=false to create the data source via the CLI which would allow environment creation for data sources managed outside of Amplify. You might need to have a decorator for certain schema types, but this seems like it could be a solution to help with onboarding of existing applications that might not leverage the Amplify CLI, and are looking to.

curtismorte on 23 Sep 2020

👍1

+1 for the feature.

The debate about using Amplify in our team largely revolves around having Postgres as an option.

Dizzzmas on 25 Sep 2020

👍3

Just ran into this issue and certainly agree with many of the comments, Aurora Serverless Postgres + AppSync GraphQL would make for an awesome stack!

sar on 8 Nov 2020

There's actually another graphql api generator that already supports Aurora Postgres serverless called "Postgraphile". The graphql server layer can also be deployed as lambdas behind an API gateway. If there was an Amplify option to add another graphql endpoint as a datasource it could also achieve the same goal. Is that possible?