VPCs with Multiple NATs
AWS VPCs do not require multiple NATs unless the marginal gains from cross-AZ resiliency are worth the increased cost and maintence burden. In such cases, it may be better to consider multi-region …
Cost risks identify where resources are being wasted or overused. These issues may include unused services, overprovisioned infrastructure, or inefficient configurations that increase spend without delivering value. Addressing cost risks helps ensure resources are used effectively and budgets are controlled.
AWS VPCs do not require multiple NATs unless the marginal gains from cross-AZ resiliency are worth the increased cost and maintence burden. In such cases, it may be better to consider multi-region …
Elastic IP addresses are requisitioned by the account but not in current use
Instances not running inside a VPC are unsupported
EKS Clusters should remain updated to prevent publicly exposed APIs from compromise and avoid forced updates which can break service
Cloudfront Distributions are set to distribute content to all available edge locations, including locations that may not include commercially viable users or may pose data sovereignty concerns
Cloudfront Distributions are accepting traffic from all locations on the internet. This includes traffic from geographical regions which are unlikely to be business accessible.