this is what it looks like if I click the Promote

this I received after clicking Update Contact Flow

https://github.com/aws-samples/ac-contactflowapi/blob/master/template.yaml
Calls for connectflows.html
The file that gets compressed and push to the S3 bucket to deploy to cloudfront is called
contactflowapi.html
The manifest file is also wrong
https://github.com/aws-samples/ac-contactflowapi/blob/master/website-creator/web-site-manifest.json
from
https://github.com/aws-samples/ac-contactflowapi/tree/master/website-creator
Lambda cloudwatch exception:

{
"errorType": "Runtime.UnhandledPromiseRejection",
"errorMessage": "Error: ENOENT: no such file or directory, open './connectflows.html'",
"reason": {
"errorType": "Error",
"errorMessage": "ENOENT: no such file or directory, open './connectflows.html'",
"code": "ENOENT",
"errno": -2,
"syscall": "open",
"path": "./connectflows.html",
"stack": [
"Error: ENOENT: no such file or directory, open './connectflows.html'",
" at Object.openSync (fs.js:462:3)",
" at Object.readFileSync (fs.js:364:35)",
" at uploadToS3 (/var/task/website-helper.js:77:31)",
" at /var/task/website-helper.js:43:17",
" at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)"
]
},
"promise": {},
"stack": [
"Runtime.UnhandledPromiseRejection: Error: ENOENT: no such file or directory, open './connectflows.html'",
" at process. (/var/runtime/index.js:35:15)",
" at process.emit (events.js:314:20)",
" at process.EventEmitter.emit (domain.js:483:12)",
" at processPromiseRejections (internal/process/promises.js:209:33)",
" at processTicksAndRejections (internal/process/task_queues.js:98:32)"
]
}

I've deployed this example but the backup flows button doesn't seem to work. I see no DDB entries in either the ARN mapping table or the Contact Flow table. The UI grabs the flows from both instances just fine. Can someone point me in a direction? It looks as if there's a single lambda that performs all the work but see no logs in cloudwatch other than when it was deployed. The only deviation from the documented example is that I'm using two connect instances in the same AWS account versus two instances in separate accounts.

I've deployed the stack in us-east-1 and all my Connect instances are in us-west-2. Not sure if that matters, getting the AWS configuration yields this error.

The browser console shows this:
XHRGEThttps://connect.us-west-2.amazonaws.com/contact-flows-summary/xxx-de96-4dfa-a1a3-xxx?maxResults=100
CORS Missing Allow Origin

GET
https://connect.us-west-2.amazonaws.com/contact-flows-summary/xxx-de96-4dfa-a1a3-xxx?maxResults=100
Status
403
Forbidden
VersionHTTP/2
Transferred397 B (68 B size)
Referrer Policystrict-origin-when-cross-origin

Any ideas?

I'm trying to move Contact Flows from one connect instance to another and am getting 400 Bad Request: InvalidContactFlowException. Is there a size limit on the Contact Flow Content? The smaller ones seem to work fine.