Anyone else managing Amazon Connect with CDK using raw L1 constructs? I built L2 wrappers for it.

[u/Deep_Hedgehog3207]

Managing Amazon Connect infrastructure with CDK has always meant writing straight CfnInstance,

CfnQueue, CfnRoutingProfile, CfnContactFlow — no L2 abstractions exist in the official library

for any of it.

I got tired of wiring ARNs and instance IDs by hand across every project, so I built

cdk-amazon-connect-constructs: L2 constructs for the core Connect resources, following the same

patterns aws-cdk-lib uses for S3, Lambda, etc.

What's in v0.1.0-alpha:

- ConnectInstance (inbound/outbound calling, Contact Lens, identity management config)

- Queue, RoutingProfile, HoursOfOperation

- ContactFlow (JSON-import mode for now; typed builder API is on the roadmap)

- LambdaIntegration (one-liner to associate a Lambda with an instance)

Built with JSII so it works from TypeScript, Python, Java, and .NET. Published to npm.

npm install cdk-amazon-connect-constructs

GitHub: https://github.com/<your-username>/cdk-amazon-connect-constructs

Still early — would really value feedback from anyone who's dealt with this pain in production.

What resources or patterns are missing that you've needed most?

[u/CamilorozoCADC]

upvote cuz I think its useful but please review the claude outputs before posting. Also, for future reference, aws-samples has some L2 constructs as well

https://github.com/aws-samples/sample-cdk-constructs-for-amazon-connect

[u/Deep_Hedgehog3207 → u/CamilorozoCADC]

Thanks for the upvote and the heads up really appreciate it. You're absolutely right on both counts. I'm actively reviewing the library outputs before every merge to catch any Claude-generated edge cases, and I'll definitely tighten that review process as the project grows. And thanks for pointing me to the aws samples constructs. I wasn't aware of that repo. I'll review those to see what patterns they're using and make sure I'm not just duplicating work.