TonyCoffman

6 ms·

1.
by TonyCoffman 9mo ago
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 record
2.
by TonyCoffman 2y ago
You don’t need any of that. Define a data source to query the instances and then a for_each DNS resource using the data source instances.
3.
by TonyCoffman 2y ago
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 l
4.
by TonyCoffman 3y ago
December 22, 2021 was the last partial impact we had in us-east-1 for EC2 instances. They had power issues in USE1-AZ4 that took a while to sort out.
5.
by TonyCoffman 4y ago
From the roadmap, it looks like they are reimplementing the same/similar feature set.
6.
by TonyCoffman 5y ago
Eucalyptus built a clone. It wasn’t one click but it also wasn’t hard to deploy. It really never made much of a dent. I’m pretty sure it ended up where all software goes to die: HP.
7.
by TonyCoffman 10y ago
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. The speed is just a bonus.
8.
by TonyCoffman 13y ago
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 brin
9.
by TonyCoffman 13y ago
Have a look at Wickard v. Filburn