CNE AWS Ready: Prerequisites

Before running the bootstrap scripts to deploy the Liferay Cloud Native Experience (CNE) in your AWS environment, prepare your local machine, cloud accounts, and Git repositories.

Local Command-Line Tools

The bootstrap and deployment scripts require the following DevOps tools. Ensure they are installed and available in your system’s PATH.

Tool	Required Version	Purpose
Git CLI	>= 2.40.1	Manage GitOps repositories and boilerplate templates.
AWS CLI	>= 2.27.25	Authenticate with AWS and manage cloud resources.
OpenTofu	>= 1.11.4	Provision infrastructure resources such as EKS, RDS, and S3.
Terraform	>= 1.7.5	Provision infrastructure resources such as EKS, RDS, and S3.
kubectl CLI	>= 1.25.2	Communicate with the Kubernetes cluster and access Argo CD.

Info

The CNE toolkit uses OpenTofu for infrastructure provisioning. Terraform may also work if it is compatible with the toolkit version.

Info

The CNE toolkit supports standard Git providers such as GitHub, GitLab, and Bitbucket. This guide uses GitHub for examples. If using another provider, ensure your repository structure matches the Liferay GitOps boilerplate.

Required Assets

The CNE toolkit provisions infrastructure using GitOps and infrastructure-as-code workflows. Prepare the following assets before running the bootstrap process.

GitOps Repository and PAT

1. Create a repository using the LiferayCloud/cloud-native-gitops-boilerplate template.

2. Generate a Personal Access Token (PAT) on your Git provider with read and write access to the GitOps repository contents, so the bootstrap process can access the repository.

AWS Configuration

Note

Cloud Native Experience environments can also run in AWS GovCloud regions. Contact your Liferay representative for guidance on deploying CNE in GovCloud.

1. Ensure your IAM credentials include permissions to create infrastructure resources such as VPCs, EKS clusters, RDS instances, and S3 buckets.

2. Create a secret named liferay/credentials/gitops in AWS Secrets Manager to store the Personal Access Token (PAT) used by the bootstrap process.

   Key	Description
   git_machine_user_id	Git username or machine account name
   git_access_token	Personal Access Token (PAT)

   Example:

   Secret name	liferay/credentials/gitops
   Key	Value
   git_machine_user_id	user
   git_access_token	ghp_abc…WxYZ

Tip

To use a different secret name, configure it in config.json. For details, see CNE: AWS Ready – Managing Secrets and Licenses.

Next Steps

After completing these prerequisites, continue to Bootstrapping Your Initial Environment.

How To related to this article

Using Zapier to Sync Object Data with Google Sheets

Published Date: Mar 19, 26 12:02

Integrate Azure AD with Liferay DXP Using SAML

Published Date: Dec 20, 25 22:55

Designing and Displaying Reusable Navigation Menus

Published Date: Dec 20, 25 21:45