feat(appsync): add support for data source integrations

[kwwendt]

Issue # (if applicable)

Closes #34264

Reason for this change

This change is to support the release of data source integrations for AWS AppSync Events. The implementation is almost an exact replica of the existing data sources for AppSync GraphQL APIs.

Description of changes

• New data-source-common.ts file which contains the data source implementation. This new file was needed given the previous data-source.ts implementation only works for the IGraphqlApi Interface. The common implementation makes it to the new generic IApi type is used.
• Changes to eventapi.ts to support adding data sources to the API.
• Changes to channel-namespace.ts to support adding event handler configuration with the data sources configured for the API.
• New unit tests to validate functionality for data sources.
• New integration tests to validate end-to-end functionality across all data source types and the different configurations for the Lambda data source type including direct Lambda invoke and sync/async invoke type.

Describe any new or updated permissions being added

There are no new permissions being added. The data source implementation was a copy/paste from the GraphQL implementation and the grant methods used in those have not changed in this implementation.

Description of how you validated changes

• New unit tests to validate functionality for data sources.
• New integration tests to validate end-to-end functionality across all data source types and the different configurations for the Lambda data source type including direct Lambda invoke and sync/async invoke type.
• integ.appsync-eventapi-dynamodb.ts
• integ.appsync-eventapi-eventbridge.ts
• integ.appsync-eventapi-http.ts
• integ.appsync-eventapi-lambda-direct-async.ts
• integ.appsync-eventapi-lambda-direct.ts
• integ.appsync-eventapi-lambda.ts
• integ.appsync-eventapi-opensearch.ts
• integ.appsync-eventapi-rds.ts

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[garysassano]

I just wanted to note that I have an open issue for this PR (#34264) in case you want to update the original message. Also, the Bedrock data source is missing, as it's currently absent from GraphqlApi as well (see #34265).

[kwwendt]

Hi @garysassano - thanks for your comment. I've updated the PR comment to include your issue number for tracking.

The Bedrock data source is something we can explore in a separate PR. I had reviewed it for this one but there are some gaps currently into the Bedrock module like short-hand syntax for cross-region inference profiles. The Bedrock data source in AppSync for both GraphQL and EventAPI is very simple - it's the type as AMAZON_BEDROCK_RUNTIME and the serviceRole filled in granting AppSync access to invoke the specific models.

Once this PR is merged and approved, I can start working on the other one for the bedrock method for both GraphQL and Event APIs.

[paulhcsun]

@Mergifyio update

[mergify]

update

✅ Branch has been successfully updated

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 1970752
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.