Versions Compared

Old Version 3

changes.mady.by.user Ameer Izwan

Saved on

compared with

New Version 4

changes.mady.by.user Ameer Izwan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Ensure that you have these CLI tools installed:
  • Configured AWS CLI with Access Keys or assumed role with sufficient permissions
  • You have downloaded the Terraform IaC from here

 

Configuring Terraform Remote Backend

Disclaimer: The Terraform code provisions the minimum required infrastructure. You may have to modify some of the parameters to ensure that it is working works in your environment.   You may refer to the official AWS and Hashicorp documentation for more details

  1. Create a terraform.tfvars file in the backend directory and ensure the following variables are included
...
  1. app_name=”<your-app-name>”

  2. Run  terraform init
  3. Run  terraform plan  to observe the resources that will be deployed (optional)
  4. Once verified, run  terraform apply -auto-approve
  5. Once the backend has been deployed, go to the  infrastructure  directory and open  main.tf
  6. Find the block:
...
  1. backend "s3" {
...
  1. 
    bucket         = "xxx"
...
  1. 
    key            = "terraform.infrastructure.tfstate"
...
  1. 
    region         = "xxx"
...
  1. 
    dynamodb_table = "xxx"
...
  1. 
}

  2. Fill in the marked with xxx  with the ones service details that you have created on step 1 - 5
...
Note: This process will create a local Terraform state. The remote state will only apply for infrastructure infrastructure.

Deploying AWS Infrastructure
  1. Create a  terraform.tfvars file and ensure the following variables are included
    app_name=”<your-app-name>”
...
  1. 
cluster_name=”<your-eks-cluster-name>”
...
  1. 
rds_username=”<your-rds-username>”
...
  1. 
rds_password=”<your-rds-password>”

  2. Run terraform init
  3. Run terraform plan to observe the resources that will be deployed (optional)
  4. Once verified, run terraform apply -auto-approve

Note: This step will take some time, around 20-30 minutes.

Deploying Joget DX 8
  1. Download the Kubernetes manifest here.
  2. Run  kubectl apply -f joget-dx8-tomcat9-deployment.yaml
  3. Wait for the containers to initialize. Run  kubectl get pods -A  to obtain the status of the pods.

Accessing Joget through Load Balancer
  1. Run  kubectl get ingress -A . You should see the DNS under Address column  like soas follows:
    k8s-namespace-RANDOM-STRING.REGION.elb.amazonaws.com

  2. Use the Address and go to  /jw . It will redirect you to the database setup.
  3. Input Enter your database information on the above page
Note: The Terraform IaC has RDS Aurora Serverless included in the Infrastructure, and as such, it will be deployed alongside the EKS. You may use the RDS to better synergize with the VPC configuration.
  1. Click Save. Wait for the database to be setup
  2. Once the setup is complete, click Done. It will redirect you to the Joget main page
...
  • Unable to locate credentials. You can configure credentials by running "aws configure".
    • You may have not setup your AWS Credentials yet, or if you are assuming role, your session may have expire
    • Solution: Run aws configure and input the Access Keys  or  export the Access Keys into your terminal environment  or  assume the previous role once again to get new session credentials
  • You must be logged in to the server (Unauthorized)
    • This happens when you are using different credentials - different users or roles to access the cluster. If you are the cluster creator, you should be able to access the cluster
    • Solution: 
      1. In the Terraform Iac, go to infrastructure/compute/eks/eks.tf 
      2. Under the module “eks”, add the following
        1. If you are using users credential:
          aws_auth_users= [
...
        1. 
    {
...
        1. 
      userarn  = "arn:aws:iam::<account-id>:user/<username>"
...
        1. 
      username = "<username>"
...
        1. 
      groups   = ["system:masters"]
...
        1. 
    }
...
        1. 
 ]

        2. If you are using roles, you may append the aws_auth_roles block like so:
          {
...
        1. 
      rolearn  = “arn:aws:iam::<account-id>:role/<role-name>”
...
        1. 
      username = "<role-name>"
...
        1. 
      groups   = ["system:masters"]
}

...