Overview
How Sygna hub service flow works
Sygna Hub and Gate are compliance-focused infrastructure components that integrate Know Your Transaction (KYT) and sanction screening services, while transmitting Travel Rule payloads based on the Sygna Bridge protocol. They also provide interoperability with external Travel Rule protocols such as GTR, CODE, TRISA, and Veriscope (Shyft). With a single configuration setup, VASPs can establish secure data exchange and message interoperability not only within the Sygna Alliance but also across heterogeneous TRP networks.
Highlights
- Travel Rule
- AML/CFT
- Crypto currency
Details
Unlock automation with AI agent solutions

Features and programs
Financing for AWS Marketplace purchases
Quick Launch
Pricing
Vendor refund policy
This product is target for test environment and there will be no refund policy for now.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Deploy with helm
- Amazon EKS
- Amazon EKS Anywhere
Helm chart
Helm charts are Kubernetes YAML manifests combined into a single package that can be installed on Kubernetes clusters. The containerized application is deployed on a cluster by running a single Helm install command to install the seller-provided Helm chart.
Version release notes
Add helm chart
Additional details
Usage instructions
Usage instructions DEPLOYMENT GUIDE: SYGNA HUB & HUB CONSOLE
INTRODUCTION Guide to deploy Sygna Hub on Amazon EKS via AWS Marketplace. Includes 30-day trial. Sygna Hub is standalone. For API key or production, email services@sygna.io . Subscribe on AWS Marketplace, then follow these steps.
PREREQUISITES EKS Cluster: Running with AWS Load Balancer Controller & IAM OIDC provider. Domain & Certificate: Registered domain and ACM certificate ARN. RDS Database: Running instance with endpoint, port, credentials, DB name; SG allows EKS traffic. IAM Role (IRSA): Role with Parameter Store access; need ARN. IRSA lets EKS pods access AWS resources. OBTAIN API KEY Email AWS Account ID to services@sygna.io (Subject: "Trial API Key Request"). Key issued in 3 business days after verification.
PREPARE CONFIGURATION Generate config.yml at https://coolbitx-technology.github.io/sygna-hub-api-doc/configurator/ . This file stores secrets like DB credentials and API keys in a Kubernetes ConfigMap. PREPARE values-aws-env.yaml at https://github.com/CoolBitX-Technology/sygna-hub-api-doc/blob/dev/platform/helm/values-aws-env.yaml . PREPARE AWS VALUES Download values-aws-env.yaml from [github URL]. You must update these 4 values: ACM ARN, Host, BACKEND_API_URL, and IRSA ARN. This file is used by Helm to deploy on EKS.
ACM Certificate ARN
Custom Domain (e.g., sygna.yourcompany.com)
Backend API URL (e.g., https://sygna.yourcompany.com/v1Â )
IRSA Role ARN
DEPLOYMENT Helm chart uses AWS Marketplace ECR: oci://709825985650.dkr.ecr.us-east-1.amazonaws.com/sygna/sygna-hub-helm.
Login: aws ecr get-login-password --region us-east-1 | helm registry login --username AWS --password-stdin 709825985650.dkr.ecr.us-east-1.amazonaws.com
Namespace: kubectl create namespace sygna-hub
ConfigMap: kubectl create configmap sygna-hub-backend-config --from-file=config.yml=./config.yml -n sygna-hub
ALBService: helm install aws-load-balancer-controller eks/aws-load-balancer-controller
-n kube-system
--set clusterName=sygna-hub
--set serviceAccount.create=false
--set serviceAccount.name=aws-load-balancer-controller
Deploy: helm upgrade --install sygna-hub \
oci://709825985650.dkr.ecr.us-east-1.amazonaws.com/sygna/sygna-hub-helm
--version 0.0.6
-n sygna-hub
-f values-aws-env.yaml
VERIFICATION Check Pods: kubectl get pods -n sygna-hub -w
Get URL: kubectl get ingress -n sygna-hub
Check ALB status in AWS EC2 console under Load Balancers.
UPGRADE Re-run helm command from DEPLOYMENT with new --version. ConfigMap and RDS data preserved. Check release notes on AWS Marketplace for updates.
SECURITY & BACKUP
Storage: config.yml secrets in Kubernetes ConfigMap. - Transit Encryption: TLS via ALB with ACM certificate. Rest Encryption: Enable RDS encryption (see AWS RDS docs). No app-level encryption; use Kubernetes Secrets for ConfigMap security. Key Rotation: ACM auto-renews. For API key, contact support, update ConfigMap. Rotate yearly or post-exposure. Backup: Use RDS snapshots for data; back up config.yml. No proprietary stores. AWS SERVICE QUOTAS Ensure your AWS account has sufficient service quotas for EKS clusters, RDS instances, and Application Load Balancers. Check limits in the AWS Service Quotas console and request increases if needed.
PRICING CONSIDERATIONS Your subscription fee with private offer covers the Sygna Hub software license. You are responsible for the costs of AWS resources deployed in your account, including the EKS cluster, RDS instance, and Application Load Balancer. The Helm chart deploys 2 pods (256m CPU, 512M memory each) by default, or 4 for high availability.
Resources
Vendor resources
Support
Vendor support
If you have any questions or requests, please contact services@sygna.io . We will get back to you in 3 workdays.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.