CloudFormation Deployment

CloudFormation Deployment Guide

To enable your CornerstoneCX product, you must deploy two CloudFormation stacks included in your registration email. These must be deployed to the AWS account and region of your connect instance:

  1. Management Stack (deployed once per account/region, no parameters required)
  2. Product Stack (deployed for each product, parameters required)

Management Stack

Important: The management stack must be deployed first. This only needs to be done once per AWS account and region. No parameters are required for this stack.

You will receive a download link for the management stack in your registration email. If you have already deployed it for your account and region, you do not need to deploy it again.


Product Stack

After the management stack is deployed, deploy the product stack for your solution. You will receive a download link for this stack in your registration email.

Parameter Descriptions

When deploying the product stack, you will be prompted for several parameters:

  • ConnectInstanceId and ConnectInstanceAlias are always required for every deployment.
  • AgentEventsKinesisStreamName is required for most products (unless your product does not use agent event streaming).
  • Some products may require additional parameters, which will be explained in the CloudFormation template or product documentation.

If you are unsure about any of these values, please refer to your AWS Documentation, product guide, or contact your administrator.

Parameter Description
ConnectInstanceId Amazon Connect Instance ID (format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)
ConnectInstanceAlias Alias for your Amazon Connect Instance
AgentEventsKinesisStreamName Name of your Agent Events Kinesis Stream (required for most products; see Agent Events Stream)
Other product-specific parameters See your product's CloudFormation template or specific product documentation for details.

Deploying the stack

Use these steps for either the Management stack or the Product stack. For the Product stack, provide the parameters listed above.

AWS Console

  1. Sign in to the AWS Management Console and switch to the correct AWS Region for your Amazon Connect instance.
  2. Open the CloudFormation service.
  3. Select Stacks, then Create stack → With new resources (standard).
  4. Specify template:
    • Upload a template file (downloaded from your registration email), or
    • Specify an Amazon S3 URL (the link provided in your email).
  5. Choose Next.
  6. Enter a Stack name (e.g., cornerstonecx-management or cornerstonecx-product).
  7. Choose Next. Optionally add tags or adjust advanced options.
  8. Acknowledge that the template may create IAM resources if prompted.
  9. Create stack, then monitor the Events tab until status is CREATE_COMPLETE.
  10. Review the Outputs tab for any values you’ll need in product setup.

Troubleshooting & Support

  • CREATE_FAILED: Open the Events tab to find the failing resource and message
  • Parameter validation errors: Re-check values (IDs, region, hostnames) and try again
  • Missing permissions: Ask your AWS administrator to grant CloudFormation/IAM/related service permissions
  • Token issues: Ensure the Auth Token is copied exactly from the email; request a new token if expired

If you continue to encounter issues with deployment, please contact support for assistance.

Post Deployment

What Happens Next?

After you complete the CloudFormation deployment, you should expect a confirmation email within 30 minutes.

This email will include: - Confirmation that your deployment was successful - Any next steps or actions required - Support contact details if there are issues

Troubleshooting

  • If you do not receive a confirmation email within 30 minutes, please check your spam/junk folder.
  • If it is still missing, contact Support for assistance.

Next Steps

  • Review the confirmation email for any additional instructions.
  • Follow any further Solution deployment instructions for your product.
  • Begin using your deployed product as described in the documentation.