aws-apigateway-kinesisstreams based on an OpenAPI specification

[mattiamatrix]

On the line of #840 and #912 it would be great to get the features also for aws-apigateway-kinesisstreams

Use Case

Be able to create an API Gateway using OpenAPI specifications

Proposed Solution

Create construct aws-openapigateway-kinesisstreams

Other

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[mattiamatrix]

Hello @georgebearden, I see that you are working on #912. Would it be possible to have the same also for API GW + Kinesis?

[biffgaut]

We'll take a look. Fulfilling #912 in a way that works best for client apps is going to be one of our most complex implementations to date, but we are hopeful we've found a way forward.

[mattiamatrix]

Do you accept PRs? Can you share more details about your implementation?
Looking at #912 I couldn't find the real code, only documentation.

[biffgaut]

Our goal is to be able to store your API definition file separate from your CDK app code - the definition will be an asset so can reside locally or in S3. The generated CloudFormation will reference the asset in the CDK staging buckets - this is important, as including the API spec in the generated CloudFormation template can grow your template past the maximum size.

The problem here is referencing the newly launched Lambda functions in the asset. Regular CDK tokens will not be substituted if the file is referenced rather than imported. Our current thought is to write a custom resource that loads the API Spec after the Lambda function is generated and substituting the arn of the new functions in the uri field as the last step. We're running some test code to see if we can make that work.

[biffgaut]

After reading this issue, we're also looking at how the substitution could be general enough that it could be applicable for resources other than Lambda functions - e.g. new Kinesis Streams.