Lesson 3 of 3
Serverless & Data Transfer Cost Optimization
Apply FinOps practices to serverless compute, managed services, and the often-overlooked data transfer costs that surprise teams at billing time.
FinOpsDecode is an independent training product and is not affiliated with, endorsed by, or sponsored by the FinOps Foundation or any certification body.
Serverless FinOps
Serverless functions (AWS Lambda, Azure Functions, GCP Cloud Functions) are billed per invocation and per GB-second of execution. Unlike VM-based compute, there is no idle cost—but runaway invocations from misconfigured event triggers, retry loops, or traffic spikes can generate large unexpected bills. FinOps for serverless focuses on per-function cost attribution, invocation efficiency (right memory configuration reduces per-invocation cost), and alert thresholds on invocation counts.
Data Transfer: The Hidden Cost Driver
- Intra-region, cross-AZ data transfer: often overlooked, but traffic between availability zones is billed at $0.01–$0.02/GB on major clouds.
- Cross-region data transfer: typically $0.02–$0.09/GB, can dominate costs in multi-region architectures.
- Internet egress: the highest rate category ($0.05–$0.09/GB)—moving data out to the internet is expensive.
- CDN offset: CloudFront, Azure CDN, or GCP Cloud CDN can reduce origin egress costs by caching content at the edge.
- VPC endpoints: using private endpoints for S3 and other services eliminates NAT gateway data processing charges.
Serverless shifts cost visibility from infrastructure to invocations. Measure differently, not less.
Practice this topic
Reinforce this lesson with scenario questions tagged Serverless, Cost Visibility, Waste Elimination.
Go to Practice