Hey everyone,
I've been using the Amazon Connect console for my deployments so far, and while it's worked fine for my simpler solutions, I'm starting to feel it's not going to cut it as I move towards more complex projects. I'm aware that Infrastructure as Code (IaC) is the way to go in cloud environments because of all the cool benefits like version control and automated deployments. However, I've been struggling quite a bit figuring out how to manage this using AWS CDK since it feels like there's not much support for Amazon Connect.
So I'm curious, how are you all deploying your Amazon Connect solutions? Are you sticking with the console or going with IaC? If you're using IaC, which tool do you prefer—AWS CDK, Terraform, or CloudFormation? I'd love to hear what you think!
4 Answers
I’ve got loads of experience in contact center tech but am new to Amazon Connect. I’m curious, how much ongoing work is required after the initial setup? Things like setting up users, queues, IVR flows, audio resources, and digital channel configurations? I mean, once everything is established, who typically handles configuration updates in Connect? Is it all done through CloudFormation?
I always stick to Infrastructure as Code for anything AWS-related, no matter the complexity. It just keeps everything documented and repeatable, which is super important to me.
We primarily use CDK for our setups, and it's the standard choice for our AWS solutions architects as well. We break our core infrastructure and the flow setups into separate repos to keep changes manageable. Plus, we developed our own tooling to handle user management better, which makes things a lot easier.
Just a heads up, a lot of AWS Connect Solutions Architects tend to prefer CloudFormation over CDK since the support for Connect in CDK is pretty limited. I've noticed that many users find reading CloudFormation examples easier too than diving into CDK.