# EKS Clusters tbi-acc-gx & tbi-acc-his - Recreation Reference

**Date:** 2026-04-15
**Account:** 594765360358 | **Region:** ca-central-1
**Purpose:** Reference for recreating services on dev cluster if needed after deletion
**Savings:** ~$597/mo with HST (2 control planes + 3 nodes)

## tbi-acc-gx Cluster

**Nodes:** 2 × m5.large (ASG: tbi-acc-gx-persistent, desired=2, min=1, max=4)

### Deployments

| Service | Image | Replicas | Port | Resources |
|---|---|---|---|---|
| tbi-acc-hotel-service | `594765360358.dkr.ecr.ca-central-1.amazonaws.com/tbi-acc-hotel-service:4.3.2-gimmonix-develop-154` | 1 | 80 | — |
| tbi-acc-hotel-service-connector | `594765360358.dkr.ecr.ca-central-1.amazonaws.com/tbi-acc-hotel-service-connector:3.2.0-gimmonix-develop-29` | 1 | 80 | — |
| tbi-acc-package-service | `594765360358.dkr.ecr.ca-central-1.amazonaws.com/tbi-acc-package-service:1.8.4-gimmonix-develop-265` | 1 | 80 | — |
| tbi-acc-travelbrandsagent | `594765360358.dkr.ecr.ca-central-1.amazonaws.com/tbi-acc-travelbrandsagent:10.0.23-gimmonix-develop-44` | 1 | 80 | cpu: 500m, mem: 1Gi |
| tbi-package-travelbrands | `594765360358.dkr.ecr.ca-central-1.amazonaws.com/tbi-package-travelbrands:7.4.0-gimmonix-develop-240` | 1 | 80 | — |
| tbi-travelbrands-dashboard | `594765360358.dkr.ecr.ca-central-1.amazonaws.com/tbi-travelbrands-dashboard:7.9.16-gimmonix-develop-24` | 1 | 80 | — |

### Ingresses

| Hostname | Ingress Class | Service |
|---|---|---|
| tbi-hotel-service.gimmonix.tbidevelopment.ca | nginx (external) | tbi-acc-hotel-service |
| tbi-hotel-service-connector.gimmonix.tbidevelopment.ca | internal-nginx | tbi-acc-hotel-service-connector |
| tbi-package-service.gimmonix.tbidevelopment.ca | internal-nginx | tbi-acc-package-service |
| access.gimmonix.tbidevelopment.ca | internal-nginx | tbi-acc-travelbrandsagent |
| package.gimmonix.tbidevelopment.ca | internal-nginx | tbi-package-travelbrands |
| dashboard.gimmonix.tbidevelopment.ca | internal-nginx | tbi-travelbrands-dashboard |

All ingresses have: `ssl-redirect: true`, `force-ssl-redirect: true`, `proxy-read-timeout: 120`, `proxy-send-timeout: 120`

### Load Balancers

| Name | Type | Scheme | DNS |
|---|---|---|---|
| a277f71892a774b9fbd19c8f19081e49 | NLB | internet-facing | a277f71892a774b9fbd19c8f19081e49-c614534b13b21377.elb.ca-central-1.amazonaws.com |
| a4690b0a208db498c8e3b76211c6cc3c | NLB | internal | internal-a4690b0a208db498c8e3b76211c6cc3c-1547894596.ca-central-1.elb.amazonaws.com |

### Secrets (Opaque)

- tbi-acc-hotel-service-secrets
- tbi-acc-hotel-service-connector-secrets
- tbi-acc-package-service-secrets
- tbi-acc-travelbrandsagent-secrets (+ TLS)
- tbi-package-travelbrands-secrets (+ TLS)
- tbi-travelbrands-dashboard-secrets

### ConfigMaps

- tbi-acc-hotel-service-config
- tbi-acc-hotel-service-connector-config
- tbi-acc-package-service-config
- tbi-acc-travelbrandsagent-config
- tbi-package-travelbrands-config
- tbi-travelbrands-dashboard-config

---

## tbi-acc-his Cluster

**Nodes:** 1 × m5.xlarge (ASG: tbi-acc-his-persistent, desired=1, min=1, max=5)

### Deployments

| Service | Image | Replicas | Port | Resources |
|---|---|---|---|---|
| tbi-acc-hotel-service | `594765360358.dkr.ecr.ca-central-1.amazonaws.com/tbi-acc-hotel-service:3.5.0-his-develop-7` | 1 | 80 | — |
| tbi-acc-hotel-service-connector | `594765360358.dkr.ecr.ca-central-1.amazonaws.com/tbi-acc-hotel-service-connector:3.1.2-his-develop-1` | 1 | 80 | — |
| tbi-acc-package-service | `594765360358.dkr.ecr.ca-central-1.amazonaws.com/tbi-acc-package-service:0.8.1-his-develop-12` | 1 | 80 | — |
| tbi-acc-profile-service | `594765360358.dkr.ecr.ca-central-1.amazonaws.com/tbi-acc-profile-service:3.6.2-his-develop-4` | 1 | 80 | — |
| tbi-acc-travelbrandsagent | `594765360358.dkr.ecr.ca-central-1.amazonaws.com/tbi-acc-travelbrandsagent:10.1.3-his-develop-13` | 1 | 80 | cpu: 500m, mem: 1Gi |
| tbi-package-travelbrands | `594765360358.dkr.ecr.ca-central-1.amazonaws.com/tbi-package-travelbrands:6.6.9-his-develop-17` | 1 | 80 | — |

### Ingresses

| Hostname | Ingress Class | Service |
|---|---|---|
| tbi-hotel-service.his.tbidevelopment.ca | internal-nginx | tbi-acc-hotel-service |
| tbi-hotel-service-connector.his.tbidevelopment.ca | internal-nginx | tbi-acc-hotel-service-connector |
| tbi-package-service.his.tbidevelopment.ca | internal-nginx | tbi-acc-package-service |
| tbi-profile-service.his.tbidevelopment.ca | internal-nginx | tbi-acc-profile-service |
| access.his.tbidevelopment.ca | internal-nginx | tbi-acc-travelbrandsagent |
| package.his.tbidevelopment.ca | internal-nginx | tbi-package-travelbrands |

All ingresses have: `ssl-redirect: true`, `force-ssl-redirect: true`, `proxy-read-timeout: 120`, `proxy-send-timeout: 120`

### Load Balancers

| Name | Type | Scheme | DNS |
|---|---|---|---|
| a2854c20f74be49e8867b03065be49ea | NLB | internet-facing | a2854c20f74be49e8867b03065be49ea-8680ac392bad50a2.elb.ca-central-1.amazonaws.com |
| adce107adbcbf4731ab883444da7b9da | NLB | internal | internal-adce107adbcbf4731ab883444da7b9da-1148338063.ca-central-1.elb.amazonaws.com |

### Secrets (Opaque)

- tbi-acc-hotel-service-secrets
- tbi-acc-hotel-service-connector-secrets
- tbi-acc-package-service-secrets
- tbi-acc-profile-service-secrets
- tbi-acc-travelbrandsagent-secrets (+ TLS)
- tbi-package-travelbrands-secrets (+ TLS)

### ConfigMaps

- tbi-acc-hotel-service-config
- tbi-acc-hotel-service-connector-config
- tbi-acc-package-service-config
- tbi-acc-profile-service-config
- tbi-acc-travelbrandsagent-config
- tbi-package-travelbrands-config

---

## DNS Records (External)

These DNS records point to the cluster LBs and will need updating if services are recreated on dev:

| Hostname | Currently Points To | Action Needed |
|---|---|---|
| `*.gimmonix.tbidevelopment.ca` | tbi-acc-gx NLB (a277f...) | Update to dev cluster NLB or remove |
| `*.his.tbidevelopment.ca` | tbi-acc-his internal NLB (adce107...) | Update to dev cluster internal NLB or remove |

**Dev cluster NLBs for reference:**
- External: `ac086a93facdf4c52928feb35f85f077-d5d887f02dba1448.elb.ca-central-1.amazonaws.com`
- Internal: `internal-a17fb567c96734ae58c1bb1003b8b020-644001943.ca-central-1.elb.amazonaws.com`

## Recreation Steps

To recreate on dev cluster:
1. Create ingresses on dev cluster with gimmonix/his hostnames pointing to existing dev deployments
2. Update DNS records to point to dev cluster NLBs
3. Or: deploy separate gimmonix/his-tagged images as new deployments on dev if different configs needed

**Note:** The gimmonix and his clusters use **different image tags** (e.g., `gimmonix-develop` vs `his-develop`) suggesting they may have tenant-specific configurations. Verify with the team before assuming dev cluster deployments are equivalent.