sethkor/connect-backup

A tool to backup and restore AWS Connect, with some useful other utilities too

connect-backup's Issues

backup/restore as part of ci/cd process?

Hi - first, thanks for creating this super useful tool.

I'm curious if it can be extended to support a traditional deployment model. For example, I would like to create Contact Flow(s) in a 'dev' AWS account ('dev' Connect instance), test/qa, and if approved, deploy the update Contact Flow(s) to another AWS account ('prod' Connect instance). I see the json elements use the ARN which includes the AWS account # and the Connect instance ID. Does the tool change these when doing a restore to another account/instance? If not could that be added?

Hangs when incorrect Connect instance ARN is passed

SSO profile failing

Hello. Thanks for making such a useful tool. Does connect-backup currently support SSO for aws profiles? I'm getting an error, but only when I try to use a profile I've signed in as using "aws configure sso":

2021/05/25 14:52:22 NoCredentialProviders: no valid providers in chain
caused by: EnvAccessKeyNotFound: failed to find credentials in the environment.
SharedCredsLoad: failed to load profile, MySSOProfileName.
EC2RoleRequestError: no EC2 instance role found
caused by: RequestError: send request failed

Unpublished contact flows interrupt the rest of the backup

Hi, thanks for making this tool.

I've encountered an issue when there is an unpublished contact flow. In the logs you get
2021/10/01 18:57:38 Failed to describe flow

when I ran to describe the contact flow manually, I found the reason was
An error occurred (ContactFlowNotPublishedException) when calling the DescribeContactFlow operation: Contact flow not published

Now when it hits this roadblock it doesn't backup the rest of the contact flows and continues to backing up users. Is it possible to skip all the unpublished contactflows and backup the other contact flows?

File Output Issues with Special Characters

During the backup of an instance, object names with certain special characters do not write to the file system properly.

Example:

A connect Instance with a Hours of Operation entry called "24/7" results in a failure as it tries to write out a 24/7.json file and the OS interprets it a as a path.

# connect-backup --instance REDACTED backup --file=ConnectBackup
2023/11/14 13:44:07 Backing up Hours
2023/11/14 13:44:07 open ConnectBackup//REDACTED/hours-of-operation/24/7.json: no such file or directory
2023/11/14 13:44:07 Failed to write to the destination

Suggestion: Escape or Quote the files before writing to disk or strip path characters from the file.
Suggestion 2: Change the name of the argument from --file to --directory or --folder

Tidy up handling of List objects so that it's consistent

Lex API call working but not returning lex bot

Need to check what is wrong here. The API is only in preview so it could be an issue on the AWS end