Troubleshooting issues

The following table lists some of the issues that you may come across while deploying Terraform on AWS.

Table: List of troubleshooting issues while deployment

Sr.No.	Issue	Description
1	The Terraform supports the Podman-based Cloud Scale Technology deployments which will not support the docker implemented `nbbuilder` script for engineering binary installations.	Resolution: The Podman does not support engineering binary installation as the `nbbuilder` script supports only docker installation.
2	Even after executing the destroy command, if there are any folders that are not removed from the environment.	Resolution: On the AWS console, do the following: Delete EKS cluster Delete IAM roles and Policies Delete EFS Delete Load balancers Delete Volumes/Snapshots Delete RDS Target Groups Delete OIDC Provider If you are using the PostgreSQL database server, do the following: Delete Postgres RDS instance Delete Lambda function Delete Secret Manager For the clean deployment next time, ensure that you have also deleted the following: .tfstate .tfstate.backup .terraform.lock.hcl file.terraform folder from base, addons, and deployment
3	Following warning messages are displayed during the addon deployment: W1002 14:51:24.301599 27385 warnings.go:70] spec.privateKey.rotationPolicy: In cert-manager >= v1.18.0, the default value changed from `Never` to `Always`. null_resource.install_trust_manager (local-exec): :warning: WARNING: Consider increasing the Helm value `replicaCount` to 2 if you require high availability. null_resource.install_trust_manager (local-exec): :warning: WARNING: Consider setting the Helm value `podDisruptionBudget.enabled` to true if you require high availability.	Ignore these warnings and proceed further.

Sr.No.

Issue

Description

The Terraform supports the Podman-based Cloud Scale Technology deployments which will not support the docker implemented nbbuilder script for engineering binary installations.

Resolution: The Podman does not support engineering binary installation as the nbbuilder script supports only docker installation.

Even after executing the destroy command, if there are any folders that are not removed from the environment.

Resolution: On the AWS console, do the following:

Delete EKS cluster
Delete IAM roles and Policies
Delete EFS
Delete Load balancers
Delete Volumes/Snapshots
Delete RDS Target Groups
Delete OIDC Provider

If you are using the PostgreSQL database server, do the following:

Delete Postgres RDS instance
Delete Lambda function
Delete Secret Manager

For the clean deployment next time, ensure that you have also deleted the following:

.tfstate

.tfstate.backup

.terraform.lock.hcl file.terraform folder from base, addons, and deployment

Following warning messages are displayed during the addon deployment:

W1002 14:51:24.301599   27385 warnings.go:70] spec.privateKey.rotationPolicy: In cert-manager >= v1.18.0, the default value changed from `Never` to `Always`.
null_resource.install_trust_manager (local-exec): :warning:  WARNING: Consider increasing the Helm value `replicaCount` to 2 if you require high availability.
null_resource.install_trust_manager (local-exec): :warning:  WARNING: Consider setting the Helm value `podDisruptionBudget.enabled` to true if you require high 
availability.

Ignore these warnings and proceed further.

Troubleshooting issues

Feedback

Feedback