How akachain/akc-mamba works
Project type and purpose
• This is an open-source, CLI-driven infrastructure-as-code tool (“AKC-Mamba”) for automating the deployment and management of a Hyperledger Fabric 1.4 blockchain network on AWS EKS (Kubernetes). It bundles Fabric components (CAs, ordering service, peers, sample chaincode), custom administrative APIs, and monitoring stacks (Explorer, Prometheus, Grafana).
File structure
• Top-level modules:
• mamba/cli – the Python CLI entry point
• mamba/blockchain – commands to bootstrap, register orgs/peers/orderers, generate artifacts, start/terminate the Fabric network
• mamba/k8s – wrappers to install Kubernetes components (EFS, ingress, autoscaler, VPN, secrets)
• mamba/template – YAML templates for Kubernetes Deployments/StatefulSets/Jobs for every Fabric component and auxiliary services
• mamba/scripts – shell scripts invoked by the CLI for low-level tasks (cryptogen, configtxgen, registrations)
• eks/, efs/ – provider-specific setup guides and policies for AWS EKS & EFS
• CI/CD: .github workflows for issue labeling; setup.py, requirements.txt, packaging.
README for additional insights
• System Model:
– 1 Root CA + 1 Intermediate CA per organization
– Kafka-based ordering service (Kafka + Zookeeper)
– A pre-configured number of peer nodes per org
– Bootstrapped sample chaincode
– In-house tools: AKC-Admin (REST API), Fabric Explorer, Prometheus, Grafana
• Deploy targets: AWS EKS cluster, EFS for shared storage, Bastion host as the operator’s client.
Final advice
• Be as detailed as possible: block out each StatefulSet/Deployment with its PVCs and Services.
• Both the static topology (how many pods, storage attachments) and the dynamic interactions (workflow phases and data flows).
• Don’t overthink—maximally decompose into logical components, then annotate connections clearly.