Scenario · Last verified 2026-08-25
Internal microservice traffic
East-west bytes that never leave the VPC, plus the small public edge that still hits internet SKUs.
| Metric | Value | Unit | Source type | Derivation | Link |
|---|---|---|---|---|---|
| Configs and artifacts | 80 | GB | Author assumption assumption | Container images, configs, and job output in object storage. Not the east-west packet volume. | — |
| Public internet from the edge | 90 | GB | Author assumption assumption | Frontend and webhook egress only. Internal service-to-service traffic is not this number. | — |
| Artifact PUTs | 30000 | request | Author assumption assumption | CI image pushes and job outputs. | — |
| Artifact GETs | 400000 | request | Author assumption assumption | Pull-through of images and configs. Cross-AZ chatter is additional and often unmetered here. | — |
Adjust the assumptions
| Vendor | Monthly total at the hub usage |
|---|---|
| Azure | $0.00 |
| Google Cloud | $0.00 |
| DigitalOcean | $0.90 |
| AWS | $18.78 |
Breakeven: cross-region-read-vs-multi-region-replica
Assumptions and limits
East-west traffic is the part this calculator understates on purpose. Cross-AZ bytes, NAT processing, and interface endpoints are not in the snapshot, yet they are how microservice meshes actually get billed. The ninety gigabytes of public edge traffic here still looks like a grant-sized internet line. The hidden-cost pages describe the meters you should add by hand from the VPC, ELB, and PrivateLink pricing pages. Putting every service in a second region for "HA" turns same-region chatter into cross-region SKUs. Read https://aws.amazon.com/vpc/pricing/ and https://aws.amazon.com/ec2/pricing/on-demand/ for the NAT, IPv4, and cross-AZ lines before you trust an internet-only estimate for an EKS or ECS mesh.