CNE AWS Ready: Configuring the Cloud Native Experience
After bootstrapping the Cloud Native Experience (CNE) environment, configure the platform components required for your deployment.
CNE follows a GitOps approach. Infrastructure and application settings are defined in your GitOps repository, and changes committed to the repository are automatically synchronized to the cluster through Argo CD.
Configuration typically involves defining infrastructure settings, exposing services through domains and TLS certificates, and configuring secrets used by the platform.
Key configuration topics include
- Adding OSGi Modules or Client Extensions with Overlays – Deploy custom OSGi modules, client extensions, and configuration files using overlays managed through S3 and GitOps.
- Cleaning Up the Environment – Safely remove the CNE deployment and reclaim cloud resources, including managed infrastructure, platform components, and the Kubernetes cluster.
- Configuring ArgoCD Domain and TLS – Expose the ArgoCD server through a custom domain and configure TLS certificates for secure access to the GitOps interface.
- Configuring Liferay Domains and TLS – Expose the platform through public endpoints and configure TLS certificates.
- Incremental Backup and Restore – Configure automated backups and restores using AWS Backup and Argo Workflows. Create backup plans, verify resources, and restore RDS and S3 recovery points.
- Managing Secrets and Licenses – Store and structure secrets for GitOps credentials, TLS certificates, and Liferay license files.
- Troubleshooting – Resolve common issues with provisioning, Argo CD synchronization, Terraform/OpenTofu state, and AWS resources.
- Understanding EKS Auto Mode – Learn how Auto Mode manages Kubernetes node scaling for system and general-purpose node pools.
- Using Elasticsearch – Configure Elasticsearch clusters as an alternative to the default OpenSearch setup for Liferay search and analytics.