The Route53 control plane is in us-east-1, with an optional temporary auto-failover to us-west-2 during outages. The data plane for public zones is globally distributed and highly resilient, with a 100% SLA. It continues to serve DNS records during regular control plane outages in us-east-1, but access to make changes is lost during outages.
CloudFront CDN has a similar setup. The SSL certificate and key have to be hosted in us-east-1 for control plane operations but once deployed, the public data plane is globally or regionally dispersed. There is no auto failover for the cert dependency yet. The SLA is only three 9s. Also depends on Route53.
The elephant in the room for hyperscalers is the potential for rogue employees or a cyber attack on a control plane. Considering the high stakes and economic criticality of these platforms, both are inevitable and both have likely already happened.
This is an artifact of how the Japanese system works. In a nutshell, they track households (families) with individuals as sub records of the family record.
Everybody on the family register record shares the same surname. Non-citizens are listed as distrinct references (for foreign spouses and the like) and they may have a different surname from the household record.
There is more to it than this but that is the key thing to know about the system.
The killer app is fiber reliability as compared to copper and coax where line errors are the norm, particularly every time it rains and water gets into a compromised circuit.
Like many companies - they are likely self-insured. If that is true, then they pay the actual costs of the claims right out of their pockets rather than participating in a larger risk pool.
I agree - it's completely disgusting to bring these costs up in that context.
CloudFront CDN has a similar setup. The SSL certificate and key have to be hosted in us-east-1 for control plane operations but once deployed, the public data plane is globally or regionally dispersed. There is no auto failover for the cert dependency yet. The SLA is only three 9s. Also depends on Route53.
The elephant in the room for hyperscalers is the potential for rogue employees or a cyber attack on a control plane. Considering the high stakes and economic criticality of these platforms, both are inevitable and both have likely already happened.