Pirate-of-SV

What is your latitude, longitude, current time zone?

120 auto mechanics employed in the 9 Tesla service centers are affected.

It's because you're using Cloudflare DNS (1.1.1.1) which Internet Archive return an incorrect IP for. There's a bazillion threads about this on HN for more detail

Github Markdown supports Mermaid OOTB, really useful.

Writing parsers and tokenizers probably.

Very good! I use this hack every day in winter to heat my apartment (charging laptop at work, run git brute force at home).

If only one node is being drained then yes.

If you want to drain 3 nodes as fast as possible it's best to start by cordoning all 3 of them and after that run drain on each respectively. This will cause minimal unnecessary interruption of pods. What we want to avoid is that new pods start on nodes that we soon want to remove/drain.

Ah yeah for IAM the defaults seem sane, true! The things that I've come across recently is that encryption at rest is usually disabled ( EBS, SQS, S3, SNS, Kinesis, Cloudwatch log groups, Cloudtrail). Some of these have server side encryption and then it's easy to just check that box, other require you to set up KMS keys etc.

Audit logs are in many cases disabled by default (RDS, S3, OpenSearch, ELB).

S3 does not require TLS requests by default. ECR does not have image scanning enabled by default.

Also new accounts almost all regions enabled and a default VPC in each (and subnets, route tables, security groups, internet gateway, dhcp option set). Unused VPCs are not recommended to keep around but I suppose it makes onboarding easier.

I think it's problematic that most security features (configurable by the user) are switched off by default and require some effort to set up. This is getting better though and for S3 buckets specifically a lot of additional features have showed up lately to "solve" this.

Not only a record, the record needs to point to a ipv6 also. If that is missing it is not as trivial as you make it.

Nice, one step closer to AWS. Next up I'd like to see an increase to the 30 second termination notice. 120 seconds would be good enough :)

It's nice that they announce it and that there's some sort of future effort promised. From my perspective we might not upgrade the elastic-stack (with current Elastic projects) too far to not bacome accidentally incompatible in case we want to make a switch.