reference
該当する場合
Design resilient network sensor deployments with failover, load balancing, and multi-region architectures.
対象読者: Platform architects, network engineers, SRE teams所要時間の目安: 15 minutes
開始前に
- You have a single-sensor deployment running and stable.
- You understand your organization's RTO and RPO requirements.
- You have access to infrastructure-as-code tools (CDK, Terraform, or Bicep) for your cloud.
ガイドの手順
1
ステップ 1
Baseline: Single-sensor deployment
Start here for small environments (<10 Gbps). Verify the sensor is working before adding complexity.
- Deploy one sensor instance per VPC/VNet/GCP region.
- Use local health check (port 8080) to validate sensor is running.
- Store API key in Secrets Manager with read access restricted to the sensor IAM role.
- Monitor CPU, memory, and ingestion metrics — upgrade instance type if >80% utilization.
成功の基準
Monitor CPU, memory, and ingestion metrics — upgrade instance type if >80% utilization.
2
ステップ 2
Active-passive failover (HA pair)
Deploy a primary and standby sensor; failover triggered by health check failure.
- Create two sensor instances in different subnets (primary and standby).
- Use Auto Scaling Group with min=1, desired=1, max=1 to handle replacement.
- Traffic Mirror Session: point primary ENI, set failover target to standby ENI.
- If primary health check fails, AWS automatically switches to standby (manual or automatic via Lambda).
- Monitoring: CloudWatch alarm on health check status; page on incident.
成功の基準
Monitoring: CloudWatch alarm on health check status; page on incident.
3
ステップ 3
Active-active load distribution
Deploy multiple sensors and load-balance traffic across them for higher throughput.
- Create 2–4 sensor instances behind a load balancer (NLB for AWS, ILB for GCP/Azure).
- VPC Traffic Mirror / Packet Mirroring routes traffic to the load balancer target.
- Each sensor ingests independently; findings are deduplicated at the platform.
- Scale with Auto Scaling based on CPU/memory metrics.
- RTO: <1 min; RPO: 0 (stateless sensors).
成功の基準
RTO: <1 min; RPO: 0 (stateless sensors).
4
ステップ 4
Multi-region architecture
Deploy sensors in each region for local capture and resilience across data center failures.
- Repeat active-active or active-passive in each production region.
- Each region has its own VPC/VNet with independent sensors.
- Platform backend is replicated (Primary region upstream, Secondary region warm standby).
- DNS failover (Route 53, Cloud DNS, Azure DNS) or application-level failover to switch regions.
- RPO: 0 (findings streamed in real-time); RTO: <5 min (DNS propagation + app failover).
成功の基準
RPO: 0 (findings streamed in real-time); RTO: <5 min (DNS propagation + app failover).
5
ステップ 5
High-availability checklist
Before going production, confirm all aspects of your HA design.
- Health checks: API endpoint responds 200 within 2 seconds.
- Auto-scaling: ASG replaces failed instances within 3 minutes.
- Secrets rotation: API key rotated without downtime (sensor pulls latest from Secrets Manager).
- Backup and restore: sensor configuration backed up; can redeploy from template in <10 minutes.
- Failover test: disable primary sensor, confirm traffic switches to secondary within SLA.
- Metrics exported to central monitoring (CloudWatch, Datadog, Splunk, etc.).
成功の基準
Metrics exported to central monitoring (CloudWatch, Datadog, Splunk, etc.).
Demonstration only
This configuration is designed for ease of use. To deploy scanner clients at scale, please plan your deployment architecture accordingly or contact us for enterprise best practices.
実行する
active-passive-failover.yaml
AWSTemplateFormatVersion: "2010-09-09"
Description: "Network sensor failover using ASG"
Resources:
SensorASG:
Type: AWS::AutoScaling::AutoScalingGroup
Properties:
MinSize: 1
DesiredCapacity: 1
MaxSize: 1
HealthCheckType: ELB
HealthCheckGracePeriod: 300成功の基準
- All sensor instances are healthy and passing health checks.
- Failover occurs automatically within your defined RTO.
- Findings continue to flow to the platform during sensor maintenance.