• 1. Cost overview
  • 1.1 Licensing and Cost Model
  • 1.2 Billable AWS Services
• 2. Resource Sizing and Cost Control Options
  • 2.1 Environment Size Presets
  • 2.2 Scheduled Uptime Optimization
• 3. AWS Service Limits Management
  • Guidance
• 4. License Management
• 5. Maintenance
  • 5.1 Credential and Key rotation
    • 5.2 Fault Handling Procedures
      • Prescriptive Guidance:
• 6. Software Patches and Upgrades
• 7. Backup and recovery
  • 7.1 Amazon RDS (PostgreSQL)
  • 7.2 Amazon OpenSearch Service
  • 7.3 Amazon ElastiCache (Redis)
  • 7.4 Amazon S3

1. Cost overview

1.1 Licensing and Cost Model

The PersonalisationHub solution is available via the AWS Marketplace product page, which includes detailed license pricing and billing terms.

Refer to the Pricing section on the Marketplace page for the most accurate and up-to-date license cost, billing dimensions (e.g., hourly or annual) and any included support entitlements.

Notes:

• The license fee covers access to the software.

• AWS infrastructure costs are billed separately by AWS and are not included in the license price.

1.2 Billable AWS Services

The following AWS services will be provisioned as part of a standard Personalisation Hub deployment. The actual usage (and thus incurred cost) depends on your selected region, instance sizing, retention periods and usage scale.

⚙️ Note: During & after the installation process, customers can configure cost-control options such as instance types, autoscaling thresholds, log retention periods, and scheduled shutdowns — all of which significantly impact operating costs.

2. Resource Sizing and Cost Control Options

The Personalisation Hub deployment guide provides configurable sizing and cost optimization options through the Cost Control page of Installation Wizard.

2.1 Environment Size Presets

Users can choose from four predefined environment sizes, which automatically adjust the instance type for EKS Worker Nodes:

Note: If the selected instance type is unavailable in your region, a comparable alternative will be selected automatically.

2.2 Scheduled Uptime Optimization

To reduce infrastructure costs, users can configure automated shutdown schedules for non-critical environments (i.e. development and staging environments):

• Define Scale Down and Scale Up times by local timezone

• Optionally Scale Down the environment over weekends

• Primarily applies to EC2-based services

These options allow for dynamic resource usage aligned with operational needs.

3. AWS Service Limits Management

The Personalisation Hub stack relies on several AWS services, some of which may have default quota limits (such as EC2 instances, EBS volumes, VPCs, or KMS keys) that vary by region and account.

During the installation process, quota checks are automatically performed. If any limit is reached, the stack will pause with a descriptive error message.

Guidance

• Customers should review and request quota increases in advance using the Service Quotas Console.

• Common services to review:

  • Amazon EC2 (instances, EIPs, volumes)

  • Amazon RDS (instances, storage)

  • Amazon EKS (node groups)

  • Amazon ElastiCache

  • Amazon OpenSearch

  • NAT Gateways and VPC components

Once the required quota has been increased, you may simply return to the Installation Wizard and click the "Try Again" button to resume.

If you encounter any issues during this step, please contact us.

4. License Management

The licensing model for Personalisation Hub is managed through AWS Marketplace.

Customers can view license terms, pricing, and usage instructions on the AWS Marketplace listing. Any updates to licensing terms or entitlements will also be reflected there.

License consumption is tied to the AWS account that provisions the stack, and no additional license keys or manual activation steps are required.

For license-related questions or special deployment needs (e.g., bring-your-own-license or enterprise agreements), please contact us.

5. Maintenance

5.1 Credential and Key rotation

The deployment provisions both IAM access credentials and encryption keys, which are created and managed within the customer’s AWS account.

• IAM users such as TerraformPermissionIAMUser include access keys used during installation. Customers are responsible for managing and rotating these credentials in accordance with AWS security best practices.

• AWS KMS customer-managed keys are provisioned for encrypting resources such as RDS, S3 and EBS.

Note:

• These resources are automatically created and managed by the stack. You do not need to manually create or rotate these keys.

• However, we recommend enabling automatic key rotation for KMS keys and following IAM credential hygiene best practices as part of your routine maintenance.

If you need support configuring credential or key rotation for your environment, please contact us

5.2 Fault Handling Procedures

In the event of unexpected faults (e.g., deployment failure, service unavailability, or component crash), the Installation Wizard and PersonalisationHub stack are designed to provide visibility and guided recovery.

Prescriptive Guidance:

• During installation:
  If any error occurs, a detailed message will be shown in the Installation Wizard UI. In most cases, a "Try Again" button will be available once the underlying issue (e.g., IAM permission, quota limit, networking setup) is resolved.

• Post-deployment service issues:

  • Use the AWS Console to verify the status of key services:

    • EC2 instance health

    • EKS workloads

    • RDS/ElastiCache availability

    • OpenSearch domain status

  • Reboot or redeploy failed components if necessary.

  • Review VPC, DNS, or IAM settings if service endpoints are not reachable.

If the fault is not self-resolvable or not clearly identified, please contact us with details of your issue and environment. Our support team will guide you through recovery.

6. Software Patches and Upgrades

At this time, updates to the Personalisation Hub stack are not delivered through an automated pipeline or CLI process.

Customers will be notified of any critical software patches or new release availability via the AWS Marketplace product detail page. These updates will include instructions, version notes, and any relevant migration guidance in the "Release Notes" or "Usage Instructions" section.

For additional support during patching or upgrade operations, please contact us.

7. Backup and recovery

Since backup and recovery needs can vary significantly between customer environments based on compliance requirements, cost preferences and operational policies, we do not publish a one-size-fits-all recovery guide. Please contact our support team for tailored guidance based on your current deployment and use case.

In general, the following data stores are provisioned as part of the Personalisation Hub deployment and should be reviewed and incorporated into your own backup plan:

7.1 Amazon RDS (PostgreSQL)

• Purpose: Core application database

• Backup: Automated backups are enabled by default and configurable via RDS Console

• Recovery: Supports point-in-time restore and snapshot-based recovery

7.2 Amazon OpenSearch Service

• Purpose: Stores logs and analytics data

• Backup: Manual and automated snapshots can be configured to S3

• Recovery: Snapshots can be restored into a new domain or existing environment

7.3 Amazon ElastiCache (Redis)

• Purpose: Caches user/session data and temporary workloads

• Backup: Snapshots are available depending on Redis version and configuration

• Recovery: Restore from backup or snapshot into a new cluster

7.4 Amazon S3

• Purpose: Stores user-uploaded assets and media

• Backup: Versioning and replication options are available

• Recovery: Recover through object versioning or from replication targets