CNE AWS Ready: Troubleshooting

Liferay Cloud Native Experience (CNE) deployments involve multiple components, including AWS infrastructure, Kubernetes, GitOps workflows, and Terraform/OpenTofu configurations. Issues can occur if resources become inconsistent or are modified outside the expected workflow.

Below is how to resolve common possible problems with deploying or managing CNE AWS Ready environments.

Terraform Errors After Deleting AWS Resources Manually

Infrastructure managed through infrastructure-as-code (IaC) tools such as Terraform or OpenTofu should remain the source of truth and control for the resources it creates. When resources are modified or deleted manually in the AWS console, the IaC state becomes inconsistent with the actual infrastructure.

When this happens, Terraform/OpenTofu may fail because it still expects those resources to exist.

For example, if an EKS cluster is deleted manually, Terraform may return an error like this:

Error: Get "http://localhost/apis/storage.k8s.io/v1/storageclasses/gp3": dial tcp [::1]:80: connect: connection refused

with kubernetes_storage_class_v1.gp3_storage_class,
on eks.tf line 203, in resource "kubernetes_storage_class_v1" "gp3_storage_class":
203: resource "kubernetes_storage_class_v1" "gp3_storage_class" {

This occurs because the Terraform state still contains references to Kubernetes resources that no longer exist.

1. Navigate to the EKS Terraform directory:

cd liferay-cne-bootstrap/cloud/terraform/aws/eks

1. Authenticate with AWS:

aws sso login

1. Attempt to destroy the infrastructure:

terraform destroy -var-file="../../../cloud/scripts/global_terraform.tfvars"

If the command succeeds, the issue is resolved.

1. If the command fails, check whether Terraform still tracks Kubernetes resources:

terraform state list | grep kubernetes

1. If resources appear, remove them from the Terraform state:

terraform state rm [resource_name]

1. Repeat the same process in the following directories:

bootstrap/cloud/terraform/aws/gitops/platform

bootstrap/cloud/terraform/aws/gitops/resources

After removing the invalid state entries, Terraform should complete successfully.