Cloud Data Transfer Costs: Cutting Cross-Zone Traffic, NAT Gateway Charges and Egress
Every arrow on an architecture diagram can be a path billed per gigabyte. Which traffic costs money and why, how to measure it, how to cut it with gateway endpoints and zone affinity, and what breaks along the way.
Compute and disk are the predictable parts of a cloud bill: you pay for the machines you started. Data transfer is different. Every arrow between two boxes on an architecture diagram can be a path billed per gigabyte, and most of those paths appear without anyone deciding to pay for them. Spreading a service across three availability zones, letting a private workload reach object storage through NAT, replicating between clusters: each choice is reasonable on its own, and together they become the fastest growing line on the invoice. This post covers which traffic is billed and why, how to measure it, and what breaks when you try to cut it.
What actually costs money
Pricing details differ between the large providers, but the shape is the same. We are not quoting prices here because they change and vary by region; check your provider's current table. What matters is knowing which paths are billed:
Within one availability zone: usually free over private addresses.
Across availability zones in the same region: billed on most providers, and on some both the sender and the receiver pay. Every replica you add for high availability lands here.
Across regions: more expensive still.
Egress to the internet: typically the most expensive item. Ingress is usually free; providers make it cheap to bring data in and expensive to take it out.
Managed gateways: NAT gateways, some load balancers and private endpoints charge per gigabyte processed on top of an hourly fee. That is a second meter on a path that may already be metered.
Surprise bills rarely come from the last items. They come from the first ones, because that traffic is "internal" and nobody expects internal traffic to cost anything.
Measure first
Do not optimize on guesses. Data transfer looks like one line on the bill but hides dozens of usage types. Load the detailed billing export (the Cost and Usage Report on AWS, billing export elsewhere) into a query engine and group by usage type. On AWS the usage type names tell you what is billed: DataTransfer-Regional-Bytes is cross-zone traffic, NatGateway-Bytes is data processed by NAT, DataTransfer-Out-Bytes is internet egress.
That tells you how much you pay, not who causes it. For that you need flow logs. Enable VPC flow logs, map source and destination addresses to subnets and subnets to zones, and rank the pairs that move the most bytes. On Kubernetes, pod traffic may show up under node addresses depending on your network plugin, so know how your CNI assigns addresses before you interpret anything. Tools such as Cilium Hubble give you the same mapping at the workload level.
You will usually find two or three dominant sources. Start there; the long tail is rarely worth the effort.
NAT gateways: the easy win
Workloads in private subnets reach the internet through NAT. The catch is that traffic to the same provider's object storage takes that path by default. If an application writes terabytes of backups or logs a day, you pay NAT processing on every gigabyte even though the traffic never leaves the provider's network.
The fix is a gateway endpoint for object storage. On AWS, gateway endpoints for S3 and DynamoDB are free and work by adding a route to your route tables:
Other managed services (container registry, secrets manager, queues) use interface endpoints, and those are not free: they bill per hour and per gigabyte. Only add them where measurement shows real volume. One interface endpoint per service in a low traffic environment can cost more than the NAT traffic it replaces.
The second NAT trap is placement. If one NAT gateway serves every zone, requests from the other zones pay the cross-zone charge first and the NAT charge second, and they all lose internet access when that one zone goes down. A NAT gateway per zone raises the fixed cost but pays for itself quickly once traffic is significant.
Cross-zone traffic: the price of the architecture
Workloads are spread across zones for availability. The cost is that any service-to-service call may cross a zone boundary. In a system spread evenly over three zones with random load balancing, roughly two out of three calls go to another zone.
Kubernetes can help. The trafficDistribution: PreferClose field on a Service asks the dataplane to prefer endpoints in the client's zone when healthy ones exist:
The field exists in recent releases; older clusters get similar behavior from the service.kubernetes.io/topology-mode: Auto annotation. Check which one your cluster version supports in its documentation.
The same idea applies to the data layer. In Kafka, setting client.rack on consumers together with a rack-aware replica selector on the brokers lets consumers fetch from a replica in their own zone instead of the leader. Pointing applications at a read replica in their own zone gives a similar win for databases.
Pitfalls
Zone affinity breaks load balancing. Keeping traffic local assumes each zone has a proportional share of replicas. With two replicas in one zone, six in another and evenly spread clients, the small zone gets overloaded. The automatic topology mode in Kubernetes disables its hints in that situation, but PreferClose does not always give you the same safety net. Enforce replica spread with topologySpreadConstraints and check that your autoscaler keeps the balance.
Trading availability for cost. The cheapest design is everything in one zone, and some teams quietly drift there. That is a risk decision, not a cost optimization, and it should be written down as one. Agree with the business which services can live in a single zone.
Forgetting compression. Service-to-service JSON, log shipping and replication streams often travel uncompressed. Turning on compression in log agents and gRPC clients can cut traffic several times over for a measurable CPU cost. Compare the CPU price with the transfer price and decide.
Observability data itself. Shipping metrics, logs and traces to another region or an external service generates real egress. Running the collector in the same zone and filtering and sampling there shrinks the data close to its source.
Mismeasuring a CDN. Putting static content behind a CDN reduces egress, but with a low cache hit ratio the CDN asks the origin for every request and you pay twice. Turning on a CDN without fixing cache headers does not save money.
When not to bother
If data transfer is a small share of the total bill, these changes are not worth the engineering time; idle capacity in compute and storage usually offers more. Do not enable zone affinity for low traffic services with few replicas: the gain is small and the imbalance risk is real. And where legal or contractual rules dictate where data lives, cost decisions sit under that constraint.
A practical order: break the bill down by usage type, find the top two or three sources with flow logs, add a gateway endpoint for object storage, place NAT per zone, then move to zone affinity at the service level. Watch the bill for a week after each step; that is the only way to see whether the change actually lowered anything.
[OK] 30 records · 9 featured · 1 retainer · 20 standard
/02 services
services.tree
> note
· Prices are in USD. Volume discounts of 7% for 6-12 day projects and 14% for 13+ day projects apply. Programs of 100+ person-days are priced individually. Prices are negotiable based on scope, urgency and long-term collaboration.
> ls ~/products/ --open-source
[OK] 2 entries · 1 live · 1 pre-release
/03 products
products.list
liveopen source · mit/prod/01
filex
the self-hosted file manager that embeds anywhere
single go binary · vue/react/web-component embed · 5 storage drivers · realtime collab · rbac · native multi-tenancy · mcp server for ai agents
We build infrastructure, automate everything, and keep systems running.
BRF Tech is a Bursa-based DevSecOps and software consulting firm. We operate across 30 service areas, from Kubernetes cluster management to serverless platform setup, CI/CD pipeline design to AI agent development.
What we do is simple: we set up your systems, automate them, and make sure they won't wake you up at 3 AM. We codify your infrastructure with Terraform, move your deployments to GitOps with ArgoCD, and monitor everything with Prometheus. If something breaks — we intervene before it does.
We're against vendor lock-in. We work with open-source tools, self-hosted solutions, and industry-standard technologies. We build your own serverless platform on Knative, isolate with Kata Containers, manage your secrets with Vault. Every project is delivered with clear scope, clear timeline, clear pricing.
DevSecOps & CI/CD
Kubernetes & Serverless
Infrastructure as Code
AI & Agent (MCP/ACP)
Security & Zero Trust
Full-Stack Development
Self-Hosted Solutions
> grep -i question ~/faq.md
[OK] 3 entries · click to expand
[?]What services are included in BRF Tech's DevOps solutions?▾
We offer CI/CD pipeline setup, Kubernetes cluster management, container migration, infrastructure automation with Terraform, monitoring & alerting, in-house technology installations and DevOps consulting services.
[?]What are your software development services?▾
We offer MVP development, existing software performance optimization, backend API development (Node.js, Go, Python) and full-stack application development. Every project is delivered with minimal technical debt.
[?]Which DevOps tools do you work with?▾
From Kubernetes and Docker to Talos Linux, from Terraform and OpenTofu to Ansible, and across Jenkins, GitLab CI/CD, GitHub Actions, ArgoCD, Flux, Helm and Rancher, we work with industry-standard tooling. For observability and error tracking we use Prometheus, Grafana, Loki, Tempo, OpenTelemetry and GlitchTip; for networking, Cilium and Envoy; for test automation, Playwright, Cypress, k6, Locust, Testcontainers and Trivy. We determine the most suitable toolset together, based on your project’s needs.
Automated build, test and deployment pipelines with GitHub Actions, GitLab CI/CD.
Automated build, test and deploy pipeline setup for existing or new repositories. GitHub Actions, GitLab CI/CD or preferred tool is used. Separate workflows are defined for staging + production environments.
Container architecture migration, cluster setup and orchestration.
Production-ready Kubernetes cluster setup on bare-metal or cloud. Includes Helm charts, Ingress, TLS certificate management, namespace isolation and RBAC.
Cozystack is an open-source cloud platform built on Kubernetes and the VMware alternative we recommend most. Virtual machines run on KubeVirt, while managed PostgreSQL, MySQL, Redis and Kafka services and dedicated tenant Kubernetes clusters are provisioned from the same dashboard and API. Includes installation on your own bare-metal servers on Talos Linux, replicated storage with LINSTOR/DRBD, network isolation with Kube-OVN, tenant and quota structure, monitoring, backup and a disaster recovery plan. After deployment we also handle upgrades, operations and support; since the platform is open source, there are no license fees and no vendor lock-in.
Packages
Virtual machine support on an existing Kubernetes cluster with KubeVirt
$2,800
4–6 person-day
Pilot setup (3 nodes, virtual machines + managed database)
$3,500
5–8 person-day
Production setup (HA + replicated storage + monitoring + backup)
$6,500
10–16 person-day
Multi-tenant private cloud (tenants, quotas, managed service catalog)
Planned, low-downtime migration of vSphere/ESXi environments to Cozystack, OpenStack or VHI.
A planned move to a VMware alternative for environments whose costs rose after Broadcom moved VMware licensing to subscription bundles, or whose renewal is coming up. We start with an inventory of your vSphere/ESXi estate (virtual machines, disks, networks, dependencies), then compare today's license cost with the total cost of the target platform. In most environments the target is Cozystack; OpenStack fits large-scale IaaS needs and Virtuozzo Hybrid Infrastructure fits storage-heavy service providers. A pilot runs on non-critical virtual machines, disks are converted with tools such as virt-v2v and Forklift, and the migration proceeds in waves within maintenance windows, with a rollback plan for every step.
Packages
Inventory + cost comparison + migration plan
$2,400
3–5 person-day
Pilot migration (up to 10 virtual machines)
$3,500
5–8 person-day
Phased migration (up to 100 virtual machines)
$9,750
15–22 person-day
Full data center migration (network + storage + backup)
OpenStack deployment, Neutron networking, Ceph/Cinder storage, upgrades and operations.
OpenStack deployment and operations in your own data center. A containerized, highly available control plane with Kolla-Ansible; Nova (compute), Keystone (identity), Glance (images) and Horizon (dashboard). On the network side, Neutron with OVN, VLAN/VXLAN, provider and tenant networks, floating IPs and the Octavia load balancer; on the storage side, Cinder block storage on Ceph RBD and optional S3-compatible object storage. For existing deployments: health checks, planned upgrades between releases, monitoring and alerting setup, and a backup strategy.
Packages
Health check + improvement report (existing deployment)
$2,400
3–5 person-day
Lab / PoC setup (single region, 3 nodes)
$3,500
5–8 person-day
Release upgrade (existing deployment)
$3,900
6–10 person-day
Production setup (HA control plane + Ceph + Neutron/OVN)
Hyperconverged infrastructure: multi-tenant cloud plus block and S3-compatible storage for service providers.
Hyperconverged infrastructure with Virtuozzo Hybrid Infrastructure, where compute, storage and networking run on the same servers. Block, S3-compatible object and NFS storage on software-defined storage, plus backup storage (Backup Gateway) for backup products such as Acronis. For service providers: a multi-tenant cloud with domains and projects, quotas, a self-service panel and an OpenStack-compatible API. Includes hardware sizing, network design, cluster deployment and expansion, version upgrades and operations support.
Packages
Pre-deployment assessment + hardware sizing
$2,400
3–4 person-day
Version upgrade / cluster expansion
$2,800
4–6 person-day
Hyperconverged cluster setup (storage + compute)
$3,900
6–10 person-day
Service provider setup (multi-tenant cloud + S3 + backup storage)
Migration of existing applications to container architecture.
Migration of existing applications to container architecture. Docker image design, Compose configuration and conversion to Kubernetes manifests. Kata Containers / gVisor can be included for advanced isolation.
Health check of your current environment, capacity planning, platform selection and a roadmap.
An independent assessment of your current virtualization environment (VMware vSphere, OpenStack, VHI or other KVM-based platforms). The health check covers cluster configuration, resource overcommit, storage latency, forgotten snapshots, backup and patch status. Capacity planning measures CPU, memory and storage growth to work out the hardware you will need next. Platform selection decides which workload should run where: Cozystack for teams running containers and virtual machines side by side, OpenStack for large-scale IaaS, VHI for storage-heavy service providers; staying on the current platform is also an option for some workloads. The deliverable is a written report with a cost comparison and a prioritized roadmap.
In-house tools like GitLab, Nextcloud, VPN, mail server.
Installation of tools like GitLab, Mattermost, Nextcloud, mail server, VPN, internal monitoring on company servers. Deployed on Docker Compose or Kubernetes.
DB + cache + code bottleneck identification and resolution.
Profiling of existing application, identification and resolution of bottlenecks. DB query optimization, caching layer (Redis), service-level improvements.
MCP/ACP agents, RAG pipelines, multi-agent orchestration, model serving.
LLM integration (OpenAI, Claude, Gemini, local models), tool-augmented AI agents with MCP (Model Context Protocol) and ACP (Agent Communication Protocol). RAG pipeline, multi-agent orchestration, model serving (vLLM/Ollama). AI layer for existing business processes.
Event-driven data pipeline with Apache Kafka, RabbitMQ, NATS. ETL/ELT orchestration with Apache Airflow, real-time data streaming, CDC (Change Data Capture). Data lake/warehouse design, schema registry, dead letter queue management.
Packages
Kafka/RabbitMQ setup + basic producer/consumer
$3,500
5–7 person-day
ETL pipeline (Airflow + source → warehouse)
$5,200
8–12 person-day
Full event-driven architecture (CDC + streaming + DLQ)
Hands-on technical training for your teams. Docker & container fundamentals, Kubernetes operations, Terraform IaC, CI/CD best practices, AI/LLM integration workshops. Practical exercises in live lab environments, content customized by skill level.
E2E test automation with Playwright, Cypress, load testing with k6/Gatling. Pre-deploy quality gate integrated into CI/CD pipeline, test coverage reporting, visual regression testing. Reduce test writing time by up to 60% with AI-assisted test generation.
Your Collected Personal Data, Collection Method and Legal Basis
Any information that identifies or makes you identifiable is considered "personal data." When you visit our website or use our services, contact information such as your name, surname, email address, phone number, as well as your IP address and browser cookie data may be collected through automatic or semi-automatic means. This data is processed based on the legal grounds specified in Article 5 of the Personal Data Protection Law No. 6698: "being directly related to the establishment or performance of a contract" and "being mandatory for the legitimate interests of the data controller, provided that it does not harm the fundamental rights and freedoms of the data subject."
Purpose of Processing Your Personal Data
Your collected personal data is processed for the purposes of providing and improving our services, fulfilling customer requests, meeting legal obligations, conducting information security processes and managing communication activities. Your data is processed in a limited and proportionate manner for the stated purposes; when the purpose ceases to exist, data is deleted, destroyed or anonymized.
To Whom and For What Purposes Collected Personal Data May Be Transferred
Your personal data may be transferred to public institutions and organizations as required by legal regulations, to our business partners and technical infrastructure providers for the purpose of delivering services, and to lawyers and consultants in legal disputes. Transfers are carried out in accordance with Articles 8 and 9 of the Law, with necessary technical and administrative measures in place.
Your Rights as a Data Subject
In accordance with Article 11 of Law No. 6698, you have the right to: learn whether your personal data is being processed; request information if it has been processed; learn the purpose of processing and whether it is used in accordance with its purpose; know the third parties to whom it is transferred domestically or abroad; request correction if it has been processed incompletely or incorrectly; request deletion or destruction within the framework of conditions set out in Article 7 of the Law; request that the operations carried out be notified to third parties to whom data has been transferred; object to any adverse result arising from the analysis of data exclusively through automated systems; and claim compensation for damages in case of unlawful processing. You may contact us through the communication channels on our website to exercise these rights.
Terms & Conditions
Terms & Conditions
1. Service Scope and Changes
BRF Tech conducts its software development, DevOps consulting, infrastructure setup and technical support services within the framework of these terms and conditions. The scope of service is determined separately for each project and finalized through mutual agreement. BRF Tech reserves the right to update the scope, pricing and technical details of its services, provided that prior notice is given.
2. Privacy Policy
Personal data collected within the scope of our services is processed in accordance with our Privacy Policy. For detailed information, please review our Privacy Policy page.
3. Service Usage and Responsibilities
Clients agree to use the provided services solely within legal and ethical boundaries. BRF Tech reserves the right to suspend or terminate services in the event of misuse, violation of third-party rights, or use for illegal activities. The client is responsible for the accuracy and currency of the information provided within the project scope.
4. Payment Terms
Payment terms are determined on a project basis and finalized through mutual agreement at the start of the project. Unless otherwise specified, invoices are payable within 15 days of project delivery. A monthly late payment interest of 2% may apply to overdue payments.
5. Cancellation and Refund Policy
Cancellation requests must be submitted in writing at least 7 days before the service start date. For projects already in progress, billing is based on the proportion of completed work. No refunds are issued for software and infrastructure components specifically developed within the project scope.