Confirm that the Installation Wizard and the Personalisation Hub stack deployed correctly by checking 5 points in the AWS Console, and find the cause when one of them fails. This is for the cloud team; it takes about 10 minutes.

Before you begin

  • Access to the AWS Console for the account and Region the platform is deployed in, with read access to CloudFormation, EC2, EKS, OpenSearch, RDS, ElastiCache and MSK.
  • The CloudFormation stack from Step 1 shows CREATE_COMPLETE.

Steps

  1. In CloudFormation, open the stack and select the Outputs tab.
  2. Open the EC2InstancePublicURL value in a browser. Once the EC2 instance is running, the Installation Wizard loads.
  3. After DNS mapping (Step 3), wait for the confirmation email that says installation has finished, then open the sign-in link it contains.
  4. In the EKS Console, open the cluster and select Workloads → Pods. Every pod shows Running.
  5. In the OpenSearch Console, open the domain. Its status is Active and the endpoint responds.
  6. In the RDS, ElastiCache and MSK Consoles, check that the instance, cluster and Kafka cluster are each available.

Verify it worked

All 5 checks pass: the wizard URL loads, the sign-in link from the confirmation email opens the platform, every pod is Running, the OpenSearch domain is Active, and RDS, ElastiCache and MSK all report available.

Troubleshooting

The Installation Wizard URL does not load

Cause. The EC2 instance is not running yet, or has stopped.

Fix. In the EC2 Console, check the instance state; start it if it is stopped, then reload the URL.

The platform domain does not respond

Cause. The load balancer's targets are failing health checks, or a security group blocks the traffic.

Fix. In the EC2 Console under Load Balancers, check the target group health checks and the security groups attached to the load balancer.

Pods fail to launch

Cause. A workload is unhealthy or cannot schedule.

Fix. In the EKS Console, open the failing pod and review its status and events.

OpenSearch is unreachable

Cause. The domain is not active, or its access policy blocks the request.

Fix. In the OpenSearch Console, check the domain status and its access rules.

AWS charges are higher than expected

Cause. The environment size or uptime schedule is larger than the workload needs.

Fix. Review the Cost Control settings — see AWS deployment: lifecycle management.

If a fault cannot be resolved, contact support@personalisationhub.com with the details listed in the AWS deployment and support guide.