- Newest
- Most votes
- Most comments
Thank you for reaching out us regarding the above query. I would like to share that, AWS Amplify CLI currently supports importing serverless Amazon Aurora MySQL 5.6 databases. The detailed approach of integrating the same with Amplify is mentioned in the below article:
[+] https://docs.amplify.aws/cli-legacy/graphql-transformer/relational/
It is also worth noting that AWS AppSync is completely GraphQL based and supports the data sources mentioned in the below article :
[+] https://docs.aws.amazon.com/appsync/latest/APIReference/API_DataSource.html
Hence if you are manually able to configure AppSync to use the VQL datasource by writing custom resolvers, in that scenario you would be able to use the same API in amplify as :
However I assume the VQL datasource is hosted outside of AWS (or not), the best approach to retrieve data from the VQL source with Amplify using AppSync API would be to use AWS Lambda as a datasource. Kindly refer to below diagram :
Amplify generated AppSync API ===> AWS Lambda Function as datasource ===> Lambda retrieves data from VQL source .
Please refer to the below articles to setup the above architecture :
- Creating AWS Lambda datasource with AppSync in Amplify : https://docs.amplify.aws/cli/graphql/custom-business-logic/#lambda-function-resolver
- Using Lambda with Appsync to get data from RDS datasource : https://aws.amazon.com/blogs/mobile/connect-amplify-datastore-with-existing-sql-datasources-adding-offline-and-sync-features-in-your-application/
- Connecting Lambda to VQL source: https://community.denodo.com/kb/en/view/document/How%20to%20connect%20from%20an%20AWS%20Lambda%20Function%20to%20Denodo%20using%20the%20JDBC%20Driver?tag=Consumers
The third article describes creating Lambda functions to access VQL sources. Please note that, the article is a third party knowledge item and AWS does not endorse any solutions mentioned in the article, the same has been recommended on best effort basis for reference purposes only.
Having said that, in case you face further challenges, please feel free to open a support case with AWS using the following link.
Relevant content
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 6 months ago