This Guidance shows how to migrate HCL Commerce Cloud to AWS and maximize the benefits of cloud-native and managed services. HCL Commerce Cloud, a commerce platform from HCLSoftware, has been developed over many years and tested by some of the largest retailers in the world. It is traditionally hosted on premises or used with hosting partners, but many of its users are now looking to migrate it to AWS to achieve the reliability, cost efficiency, scale, and security of the modern cloud. Using containers, HCL Commerce Cloud customers can use the recommended architecture to meet those demands and migrate their applications to AWS efficiently and at scale.

Please note: [Disclaimer]

Architecture Diagram

[Architecture diagram description]

Download the architecture diagram PDF 

Well-Architected Pillars

The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.

The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.

  • Amazon EKS is a fully managed service that removes the burden of managing Kubernetes infrastructure. Your teams can easily deploy, manage, and scale the containerized components for your HCL Commerce Cloud deployment. Additionally, Amazon RDS for Oracle automates database administration tasks like hardware provisioning, software patching, maintaining high availability, and performing backups. This reduces the operational load so that teams can redirect their efforts to innovation.

    Read the Operational Excellence whitepaper 
  • CloudFront improves website security by providing traffic encryption and access controls. It also works with AWS Shield Standard, which defends against distributed denial-of-service attacks at no additional charge, and AWS WAF, which helps protect against common web exploits. Additionally, Amazon Virtual Private Cloud (Amazon VPC) separates your database and compute networks from the internet and protects them with a closed-down network access control list and security groups. It exposes only Application Load Balancer to the public internet. This Guidance also scopes down all AWS Identity and Access Management (IAM) policies to the minimum permissions required for the service to function properly, helping you limit unauthorized access to resources.

    Read the Security whitepaper 
  • Elastic Load Balancing (ELB) routes user traffic to healthy containers in Amazon EKS, which automatically scales containers across multiple AZs for high availability. Similarly, Amazon RDS for Oracle places database instances in two AZs and provides failover support for high availability. Amazon S3, which provides 99.999999999% (11 nines) durability, stores automated backups. By using ELB, Amazon EKS, and Amazon RDS together, you reduce the chance of application failure, so your users can browse HCL Commerce Cloud with virtually zero downtime, and your operation's teams can meet their recovery time objective and recovery point objective requirements.

    Read the Reliability whitepaper 
  • This Guidance helps you sustain peak traffic for your ecommerce website. Amazon EKS scales your HCL Commerce Cloud containers on demand, so only the necessary compute resources are allocated. Amazon RDS for Oracle can scale out the database using read replicas. Additionally, CloudFront serves requests through the edge location closest to the requester to reduce network latencies.

    Read the Performance Efficiency whitepaper 
  • CloudFront helps decrease the frequency of data access or microservice invocations through caching where possible. This means that Amazon EKS, through automatic application scaling and efficient compute resource provisioning, will provision the minimum amount of resources, lowering your compute costs. And as a managed service, Amazon EKS enables you to offload the undifferentiated heavy lifting of operating the Kubernetes control plane. Similarly, Amazon RDS for Oracle helps you avoid the costs of maintaining an underlying database infrastructure. You can also buy Amazon RDS Reserved Instances, which provide maximum cost savings for a long-term commitment.

    Read the Cost Optimization whitepaper 
  • Amazon EKS adapts to demand and scales down during periods of low traffic, making the architecture more sustainable by reducing your carbon footprint. You can also use the latest AWS Graviton Processors for Amazon EKS and Amazon RDS. These processors use up to 60 percent less energy than comparable Amazon Elastic Compute Cloud (Amazon EC2) instances for the same performance.

    Read the Sustainability whitepaper 

Implementation Resources

A detailed guide is provided to experiment and use within your AWS account. Each stage of building the Guidance, including deployment, usage, and cleanup, is examined to prepare it for deployment.

The sample code is a starting point. It is industry validated, prescriptive but not definitive, and a peek under the hood to help you begin.

[Content Type]


This [blog post/e-book/Guidance/sample code] demonstrates how [insert short description].


The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.

References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.

Was this page helpful?