...
| Type | Granularity | Service | Example | Utilization per service | Type | Formula | Free Tier | Cost US/m | Shared overhead |
|---|---|---|---|---|---|---|---|---|---|
| compute | 1 vCPU | IaaS EC2 | t3a.micro | 100% | On Demand | ||||
| Reserved 3y no front | |||||||||
| Spot 20210218 | |||||||||
| PaaS K8S | 3 x t3a.large | 1/12 | |||||||
| CaaS Fargate | n/a | ||||||||
| FaaS Lambda | n/a | 1M 128Kb 100ms = .0125 GB-s | 400k GB-s | 0.20 req 0.21 exec $0.41 | |||||
| persistence | 1 GB | IaaS RDS | 100% | ||||||
| DBaaS Aurora | n/a | ||||||||
| DBaaS DynamoDB | n/a | ||||||||
| storage | 1 GB | S3 | n/a | ||||||
| throughput | 1 Gbps | Network In | |||||||
| AI AWS Textract | Text and Image Processing#TextractAPIExamples | 0.07 / tx
|
Costing Options
| Tool | Details | |
|---|---|---|
| Cost Explorer | ||
| Cost Estimator | ||
| Savings Plans | ||
| Free tier usage | Most services have tier - once used gone - so the first service in gets the benefit | |
| Volume pricing | If several services saturate for example S3 - subsequent services will benefit with lower pricing (resource pooling) | |
| Auto scaled reserved | If service A kicks in k8s autoscaling of the worker nodes - all other services benefit by default due the capacity increase. The reverse is true - if service A terminates - then service B (rogue) had full use of most of the vCores on a scaled node - now needs to share in a more overall saturated smaller cluster | |
| Partitioned use | Move read-only traffic - like monitoring/reporting to a read replica that is optimized for read not read/write |
...