Back to Samora report center

Samora cloud systems

Samora cloud systems An architecture diagram generated by Archify. People and systems · operators + customers · Architecture component People and systems operators + customers Traffic entry · ALB/NLB + WAF/ACM · Architecture component · 6 public / 4 internal Traffic entry ALB/NLB + WAF/ACM 6 public / 4 internal ECS Fargate services · 16 services / 22 tasks · Architecture component · prod + stage + shared ECS Fargate services 16 services / 22 tasks prod + stage + shared EKS runtime · 1 cluster / 1 node group · Architecture component · stage signal EKS runtime 1 cluster / 1 node group stage signal Lambda jobs · 37 primary + 2 secondary · Architecture component · 33 container images Lambda jobs 37 primary + 2 secondary 33 container images Build and release · OIDC + build pipelines + registry · Architecture component · 50 repositories Build and release OIDC + build pipelines + registry 50 repositories Event backbone · SQS + SNS + EventBridge · Architecture component · durable async work Event backbone SQS + SNS + EventBridge durable async work RDS and ElastiCache · 7 PostgreSQL / 3 Redis · Architecture component · records + coordination RDS and ElastiCache 7 PostgreSQL / 3 Redis records + coordination S3 and AWS Backup · encrypted objects + RDS backups · Architecture component · 34 buckets S3 and AWS Backup encrypted objects + RDS backups 34 buckets Channel providers · voice + messaging + tools · Architecture component Channel providers voice + messaging + tools Operations and controls · logs + audit + threat checks · Architecture component · 89 logs / 113 alarms Operations and controls logs + audit + threat checks 89 logs / 113 alarms public traffic 5 ECS routes records + cache async work fan-out + queues objects callbacks releases deploys logs + alarms

What AWS directly proves

  • • Active workloads are concentrated in ap-south-1, with two Lambda functions also observed in us-east-1
  • • Load balancers, ECS services, queues, schedules, Lambda subscriptions, backup links, and audit delivery were counted from AWS associations
  • • No API Gateway was observed in the primary region; CloudFront remains unverified rather than assumed absent

Where code context completes the picture

  • • Samora code and prior verified reports identify PostgreSQL, Redis, queues, object storage, providers, and workflow coordination as application dependencies
  • • AWS task definitions, function environment variables, network rules, and policies were deliberately not read for this public map
  • • Environment labels are naming hints, not proof of workload ownership

Safe sharing boundary

  • • No account IDs, ARNs, endpoints, domains, IP addresses, network IDs, security rules, secret names, secret values, or customer data are included
  • • This is a point-in-time inventory from read-only AWS calls, not a desired-state deployment file
  • • No AWS resource, Samora database row, or Activity row changed during discovery