AppSync connection to Aurora Serverless V2 via Data API not working

Based on the information provided, it seems you've taken several correct steps in upgrading your Aurora MySQL-based Serverless v1 to v2 and enabling the Data API. However, there are a few additional points to consider that might help resolve your AppSync connection issue:

1. Verify Data API Configuration: After upgrading to Aurora Serverless v2, ensure that the Data API is properly configured. You can do this by using the AWS CLI command 'aws rds-data execute-statement' to test if the Data API is working correctly with your new cluster.

2. Check Database and Schema: Make sure that the database and schema you're trying to access still exist after the upgrade. You might need to recreate them or update your AppSync API to point to the correct database and schema.

3. Update AppSync Resolvers: Your AppSync resolvers may need to be updated to work with Aurora Serverless v2. Review and possibly modify your resolver mappings to ensure they're compatible with the new setup.

4. Verify Secrets Manager: Confirm that the new secret in AWS Secrets Manager contains the correct credentials for accessing your Aurora Serverless v2 cluster.

5. IAM Permissions: Double-check that your IAM roles and policies are correctly set up to allow AppSync to access both the new Aurora Serverless v2 cluster and the associated Secrets Manager secret.

6. Data API Limits: Be aware that there's a limit on the size of each returned row (64 KB) when using the Data API. Ensure your queries don't exceed this limit.

7. CloudWatch Logs: Enable and check CloudWatch logs for both AppSync and Aurora Serverless v2 to see if there are any error messages that could provide more insight into the connection issue.

If after verifying these points you're still experiencing issues, you may want to try creating a new AppSync API data source specifically for the Aurora Serverless v2 cluster to rule out any configuration issues with the existing data source.

Remember, when designing your application to use the Data API with AppSync, it's important to consider the limitations and best practices specific to this setup.

If the problem persists, you may need to reach out to AWS support for further assistance, as there could be specific details about your setup that require more in-depth troubleshooting.

Sources
Introducing the Data API for Amazon Aurora Serverless v2 and Amazon Aurora provisioned clusters | AWS Database Blog
Using Aurora Serverless with AWS AppSync - AWS AppSync

With reference to above response i would like add few more details as below

Dear customer,

I understood the issue you're experiencing with connecting your existing AppSync API to your newly upgraded Aurora MySQL-based Serverless v2 cluster.

I'd like to offer some suggestions that might help resolve your connection issue.

1. Data API Configuration Verification:

It's great that you've enabled the Data API for your Aurora Serverless v2 cluster. To ensure it's working correctly, I recommend testing it using the AWS CLI command:

aws rds-data execute-statement --resource-arn <your-cluster-arn> --secret-arn <your-secret-arn> --database <your-database-name> --sql "SELECT 1"

This will help verify if the Data API is functioning as expected with your new cluster [1].

2. Database and Schema Check:

Please confirm that the database and schema you're trying to access still exist after the upgrade. You might need to recreate them or update your AppSync API to point to the correct database and schema.

3. AppSync Resolver Update:

Your AppSync resolvers may need adjustments to work with Aurora Serverless v2. I suggest reviewing and possibly modifying your resolver mappings to ensure compatibility with the new setup [2].

4. Secrets Manager Verification:

Double-check that the new secret in AWS Secrets Manager contains the correct credentials for accessing your Aurora Serverless v2 cluster.

5. IAM Permissions:

Ensure that your IAM roles and policies are correctly set up to allow AppSync to access both the new Aurora Serverless v2 cluster and the associated Secrets Manager secret.

6. Data API Limits:

Keep in mind that there's a 64 KB limit on the size of each returned row when using the Data API. Make sure your queries don't exceed this limit [3].

7. CloudWatch Logs:

Enable and review CloudWatch logs for both AppSync and Aurora Serverless v2. This can provide valuable insights into any error messages or issues that might be occurring.

If you've verified all these points and are still experiencing issues, you might want to try creating a new AppSync API data source specifically for the Aurora Serverless v2 cluster. This can help rule out any configuration issues with the existing data source.

If you continue to face difficulties after trying these suggestions, please don't hesitate to reach out again. We may need to dive deeper into your specific setup to troubleshoot further.

References:

[1] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/data-api.html [2] https://docs.aws.amazon.com/appsync/latest/devguide/tutorial-rds-resolvers.html [3] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/data-api.html#data-api.limits

Ensure Aurora Serverless V2 has Data API enabled and correct IAM permissions are set for AppSync to access it.