One-click deployment on AWS is perhaps incomplete, with broken variable and documentation references

Support
1

Hi team,

I’m brand new to this space, so apologies in advanced for anything obvious that I may have missed.

I find it very useful to just get [stuck in] with Infrastructure in order to learn new concepts, and when I saw there was a “one-click deployment” for AWS, I thought that would be a great starting point. However, I’ve been encountering some issues, and I’m not sure how to progress.

Issue 1
I get started with this README:

It states that you must already be setup with eSignet and Sunbird RC, and directs you to the following repository (which doesn’t seem to exist):

https://github.com/dpgonaws/inji-certify-aws-automation/

It’s unclear to me what prerequisites I need to get set up with before I start setting up the Inji stack.

It would also be good to know if any outputs from eSignet and Sunbird RC are needed for the Inji setup. I think at the moment that is also a little unclear.

Issue 2
I decided to push ahead even without eSignet/Sunbird RC (just to see what happens), so I went into this README:

All noted Prerequisites have been met.

A minor comment is that the instructions tell you to cd into a directory called inji-aws-automation (which doesn’t exist), but I assumed it meant the aws directory.

I then attempt to run cdk bootstrap aws://<ACCOUNT-NUMBER>/<REGION> (replacing values appropriately), but I receive the following error:

1
1956×364 54.1 KB

From “lib/eks-ec2-stack.ts” I can see that no definition for this variable exists:

2
21026×190 39.9 KB

Because it has been commented out:

3
3655×206 29.5 KB

I thought about just adding the line back in, but it looks like this configuration was also quite purposefully commented out from configuration requirements, and there is no reference to it in the required environment variables:

4
4981×226 26.8 KB

Issue 3 (maybe?)
I also spotted some hardcoded accounts in files that aren’t mentioned in the README, and I’m wondering if those might be problematic for future steps. EG:

5
5650×236 12 KB

6
61045×205 33.9 KB

Issue 4 (maybe?)
I’m not sure if this bin file is used at any point, but I noticed that aws/inji-certify-aws-automation/bin/inji-certify-aws-automation.ts also has an import for a file that doesn’t exist (though, also, the import doesn’t appear to be used, so perhaps it can just be removed):

7
7893×153 17.4 KB

Rewinding back to the start
So, I absolutely appreciate that there are lot of complex topics that go into this technology, and it’s probably not ideal that I’m trying to dive right in, but again, this is how I find that I learn best, so it would be amazing if there were some step by step (and end to end) instructions (even if they are far more manual and not “one-click”) that will get folks like myself up and running at some basic level so that we’re free to start playing around.

Thank you so much for reading, and thank you in advance for any help!

2

Hi @chrispenny

Thank you again for raising this and for your continued engagement.

To support a smoother setup and to address the gaps you encountered, we are sharing a detailed deployment guide covering the end-to-end environment setup, tool prerequisites, cluster configuration, and Wireguard access required for Inji stack deployment. Below are the prerequisites given, and for the detailed doc, click here!

Prerequisites

Tools and Utilities:

  • Ansible

  • Rancher

  • Command line utilities:

    • kubectl

    • helm

    • rke (v1.3.10)

    • istioctl (v1.15.0)

Helm Repositories:

helm repo add bitnami https://charts.bitnami.com/bitnami
helm repo add mosip https://mosip.github.io/mosip-helm

System Requirements

Hardware, Network, and Certificate Requirements

Purpose vCPUs RAM Storage VMs Notes
Bastion Host (Wireguard) 2 4 GB 8 GB 1 Active-passive setup
Observation Cluster 2 8 GB 32 GB 2 For Rancher & logs
Observation Nginx 2 4 GB 16 GB 1 Load balancer
Inji Cluster Nodes 8 32 GB 64 GB 3 Include nginx, etcd, control plane

Network Requirements:

  • Stable internal & external connectivity

  • All VMs must be on the same internal network

  • Public IP or NAT forwarding for Wireguard and Inji nginx servers (51820/udp, 443/tcp)

DNS Requirements (Sample)

Domain Maps To Purpose
rancher.xyz.net Observation nginx Rancher dashboard
api.sandbox.xyz.net Inji nginx public IP Public-facing APIs
injiverify.sandbox.xyz.net Inji nginx Access Inji Verify portal
…and others listed in full guide

SSL Certificate Requirements

  • Wildcard certificates for *.org.net (Observation) and *.sandbox.xyz.net (Inji)

  • Must be installed inside corresponding nginx VMs

Tools to Install on Developer Machine

Includes:

  • Wireguard setup (client & bastion)

  • Docker setup via Ansible

  • Secure access with preconfigured peer confs

  • Peer assignment and client configuration for private access

Observation Cluster Setup (Optional, Not required as a mandatory step can be skipped for now)

  • Setup cluster nodes with passwordless SSH

  • Clone and run playbooks from k8s-infra

  • Install rke, kubectl, helm, istioctl

  • Follow step-by-step scripts to:

    • Install Kubernetes via RKE

    • Configure Ingress and Nginx

    • Deploy Rancher and monitoring apps

Once the prerequisites are completed, then we can move to the next steps to set up each module

Let us know if you face any blockers during any prerequisite steps. We’ll prioritize support and keep updating this thread as we resolve open variables or missing references.

Best regards,
MOSIP Team