Event-driven repair history synchronization architecture using EventBridge Scheduler to trigger ephemeral ECS Fargate tasks daily at 02:00 JST, pulling data from external Rakuraku CSV API via allowlisted static EIPs over TLS. Data flows through a dedicated VPC with dual availability zones, Network Firewall-controlled egress, VPC endpoints for AWS service access, and private connectivity to integration MySQL and warranty CMS backends. The design enforces least-privilege IAM roles, secrets rotation via AWS Secrets Manager, container image signing via ECR, and failure handling through SQS DLQs and SNS alerts to CloudWatch. Fork this diagram on Diagrams.so to customize scheduling rules, add additional external systems, or adapt the multi-AZ failover strategy for your repair data pipeline.