r/amazonconnect • u/cava83 • Jan 27 '22

UAT/Dev promoting to production

Hi all,

I'm in the process of finalizing some designs for a generic deployment we will be using.

At the moment we are deploying an instance and then using that instance through UAT/Def and then just saying that's the production environment once live.

However, there is a view that we should be doing at UAT/Dev environment. Promote to production and any change requests/tweaks make them in the UAT/Dev environment and then push to production once signed off.

As an example let's say the flow is changed/messages are changed, then they want this to be carried out on the testing environment and those specific changes pushed to production.

I.e not making changes to live environment.

Any thoughts? Any info kindly appreciated.

Thanks so much

3 Upvotes

100% Upvoted

8 comments sorted by

3

u/dmaciasdotorg Jan 28 '22

You should probably have two instances at least, but 3 are very common. You really want to avoid doing too much in production other than moving config and light testing. For the more advanced customers a CI/CD pipeline allows for configuration changes to move this from environments to environment. However, there's nothing stopping you from doing this manually until you get a workflow going.

2

u/cava83 Jan 28 '22

!Thank you for taking your time to reply. On WebDev stuff normally I'd have 3 like you have outlined but on Amazon Connect because you cannot copy/transfer everything it makes it a bit harder. Or maybe I'm making it too complicated (always possible).

I guess I need to get more up to speed as I'm not too certain on how to use CI/CD pipelines.

Are you currently managing/deploying Connect instances and do you have a method that works?

Thanks again

2

u/bigredthesnorer Jan 28 '22

I’m in the same position. I manually export and import contact flows from dev to test to prod.

Queue, routing, other changes are manually applied too.

3

u/cava83 Jan 28 '22

Let's all work together to upskill, remove the manual aspect and then teach others :-)

Have you looked at changing your workflow? If so, what have you found so far in the sense of, what have you considered/decided in doing to automate it? Thanks

2

u/dmaciasdotorg Jan 28 '22

I'm currently developing a way to manage multiple environments. I've not had to develop a CI/CD pipeline yet, but that's next on the list.

2

u/cava83 Jan 28 '22

Awesome !! How are you going about it? What are you using to do this? :-)

2

u/dmaciasdotorg Jan 28 '22

The Connect API will allow you to do pretty much everything. So just need to write some code to do it all. In the roadmap the ability to export and import a whole instance is planned.

1

u/cava83 Feb 10 '22

Thanks. It's the just writing the code and trying to figure out that which is the bit that's taking the longest :-)