Benchmark: BP01 Use highly available network connectivity for your workload public endpoints
Description
Building highly available network connectivity to public endpoints of your workloads can help you reduce downtime due to loss of connectivity and improve the availability and SLA of your workload. To achieve this, use highly available DNS, content delivery networks (CDNs), API gateways, load balancing, or reverse proxies.
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-aws-well-architectedStart the Powerpipe server:
steampipe service startpowerpipe serverOpen http://localhost:9033 in your browser and select BP01 Use highly available network connectivity for your workload public endpoints.
Run this benchmark in your terminal:
powerpipe benchmark run aws_well_architected.benchmark.well_architected_framework_rel02_bp01Snapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_well_architected.benchmark.well_architected_framework_rel02_bp01 --shareControls
- CloudFront distributions should have origin failover configured
- CloudFront distributions should have AWS WAF enabled
- ELB application, network, and gateway load balancers should span multiple availability zones
- ELB classic load balancers should have cross-zone load balancing enabled
- ELB classic load balancers should span multiple availability zones
- Lambda functions should operate in more than one availability zone
- RDS DB clusters should be configured for multiple Availability Zones
- RDS DB instance multiple az should be enabled
- S3 bucket cross-region replication should be enabled