Setting up your own instance
What it takes to run this workshop against your own Connect instance rather than the sales demo.
The sales demo exists so you can skip this. If you want the same thing in your own account, here is the whole list. It is a setup job rather than a workshop step, so do it before you start rather than partway through.
-
Deploy DFC into your AWS account. The customer template creates the lookup function and its table. Note the function name it creates, which ends in your stage.
-
Import a starting set of entities, so you have something to configure. DFC creates none for you, so either export them from an instance that already has them or build your own. See Import and export.
-
Import the two modules first, then the inbound flow. The flow refers to the modules by id, so they have to exist before it does.
-
Repoint the Lambda in both modules. The exports carry a placeholder ARN,
arn:aws:lambda:<REGION>:<ACCOUNT_ID>:function:dfc-query-by-path-<STAGE>. Replace it with your own before publishing, or the flow will publish and then fail on the first call. -
Repoint the module ids. Open the inbound flow’s two Invoke module blocks and select the modules you imported, since the ids in the export belong to the instance they came from.
-
Associate the function with your Connect instance. Connect refuses to invoke a function that has not been added to the instance, and the error reads like a flow problem rather than a permissions one.
aws connect associate-lambda-function \ --instance-id <INSTANCE_ID> \ --function-arn <LOOKUP_FUNCTION_ARN> \ --region <REGION>The CloudFormation template usually does this for you, associating the function with the instance you name at launch. The command above is for instances where the function arrived some other way.
-
Claim a number and attach the inbound flow.
The inbound flow serves chat too, so you can do the whole workshop from the Connect console’s test chat before claiming a number. Call the demo flow has the chat route and what it hides.