This page lists the skills, AWS permissions and DNS arrangements needed to deploy and operate Personalisation Hub in your own AWS account.

Skills and knowledge

The installation itself is guided step by step and needs no AWS expertise. Ongoing operation assumes the following baseline knowledge.

AreaKnowledge assumed
IAMManaging user roles and permissions
EC2Locating instances, viewing logs, basic restart actions
S3Accessing uploaded media and configuration
VPC and networkingReading subnet, routing and gateway set-ups
CloudFormationReviewing stack outputs and troubleshooting stacks
AWS MarketplaceSubscribing to a product; finding its deployment documentation and release notes; monitoring usage, updates and support options
Domains and SSLConfiguring DNS for a custom domain; how SSL/TLS certificates and DNS propagation work

AWS account access and permissions

No AWS root user credentials are required. Deploy with an IAM user or role that can:

  • Subscribe to AWS Marketplace products and start provisioning
  • Deploy infrastructure with AWS CloudFormation
  • Request service quota increases through AWS Support
  • View billing and usage information (optional; used for cost monitoring)
  • Create and manage the components in the following table
ServiceRequired components
Identity and Access Management (IAM)Roles, policies, instance profiles, OIDC provider
Elastic Kubernetes Service (EKS)Cluster, node groups, add-ons (VPC CNI, CSI)
Elastic Compute Cloud (EC2)Launch templates, Auto Scaling groups, Elastic IPs
Virtual Private Cloud (VPC)VPC, subnets, route tables, NAT, internet gateway, NACLs, DHCP options
Amazon RDSDB instances, subnet and parameter groups, security groups
Amazon ElastiCacheRedis cluster, subnet group, security group
Amazon MSKKafka cluster, security group
OpenSearch ServiceDomains, security groups
S3Buckets, ACLs, CORS, ownership controls
Elastic Load Balancing (ELB)Load balancers, target groups
AWS Certificate Manager (ACM)Certificates
AWS Key Management Service (KMS)Keys, aliases
Systems Manager (SSM)SSM parameters (for example, the AMI)

The AWS documentation covers each of these services.

DNS mapping

ItemValue
Record targetThe platform's load balancer or public endpoint
Recommended hostA subdomain of your primary domain, for example ph.yourdomain.com
Record typeCNAME (or A/ALIAS)
DNS providerAny — your existing provider, Cloudflare or Route 53
PurposeMakes the platform reachable from the internet and allows the SSL/TLS certificate to be issued for HTTPS
PropagationDNS changes can take time to propagate globally

The records to add are emailed to the Master Admin when installation finishes — see Step 3 — Set up DNS after installation.