Replies: 1 comment
-
Hi Ghost,
MindsDB under the hood use python+boto3. Maybe you should start from this info. (For example: if you want to access dynamodb thru appsync (graphql), you can create a lambda resolver with boto3, and access to dynamodb. No need to modify @auth directive settings in your .graphql file. You can create lambda resolvers inside "Amplify": with "add function" command / advanced options)) Docs: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to use Mindsdb with AWS Amplify in an app. I'll be creating a Dynamodb database using
amplify add api
, and I'll be configuring authentication using the @auth directive of the Amplify CLI. The command creates a Dynamodb database, and I'll like to use that database with the Mindsdb cloud. I don't know what to do, really. Do I have to make the tables public for Mindsdb to have access to them? Like this. Maybe it's not needed.I also noticed that, to link a Dynamodb table to the Mindsdb cloud, I must generate an access key and a secret AWS key. Should I create another IAM user for Mindsdb and generate those credentials for the user? And that'll work without me changing any setting in my Amplify Graphql schema? Please help.
Also, I would like to know how the Mindsdb integration with DynamoDB works. When I query a model created on Mindsdb cloud, does Mindsdb reach out to Dynamodb to get the most up-to-date data in the database each time or continue using the data it retrieves from Dynamodb at the moment I linked the database to it? I really appreciate any help you can provide.
Beta Was this translation helpful? Give feedback.
All reactions