- Cell based architecture to reduce traffic over azs
- Ipv6 to remove nats
- Nat instances using alternat
- S3 bucket key enablement for encrypted buckets to reduce kms
- Savings plans instead of reserved instances
- Restricting services and regions by scps
- Aws budgets on cost and usage
- Using nlbs instead of albs
- Rightsizing
- Spot instances
- Removing intermittent resources monitored by aws config
- Tagging everything even s3 buckets by their name so they are searchable and costs are allocatable
- Use trusted advisor a lot
- Use cost optimization hub
- Enable compute optimizer
- Use arm instead of x86
- Using gp3
- For ipv4, use alternat for cheap nat instances instead of a nat gateway
- Talk to TAM about other cost saving approaches, EDP, etc
- Look into a 3rd party to manage RIs or spot
- Use private ips when possible
- Don’t use private ca
- Convert to containers to use ecs, eks, or lambda
- Shutdown extremely low utilization resources
- Cloud watch log groups all have an expiration
- Deploy cudos dashboard
- Enable cost split allocation tags
- S3 intelligent tiering
- VPC endpoints
- Remove old or non recent backups
- Lifecycle policies (ecr, s3, etc)
- Use latest resource instance family
Last active
October 29, 2024 16:22
-
-
Save nitrocode/45a6d234ccf1b5950ac754ae4c2e52ab to your computer and use it in GitHub Desktop.
Saving money in aws
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment