(This is part of an open ended series of posts where I write down random things I feel are sharable from the years of mailing lists I’ve not caught up on…)
This, Part 2, catches me on Last Week in AWS so ‘new’ things will actually be ‘new’. You know, while I am solo-preneuring things and my AWS configuration is amazingly simplistic. Ah well.
- Seconds Since the Epoch – reminds me of Noah’s Falsehoods Programmers Believe About Time (likely because it is on the list.)
- Say Goodbye to Outdated Footer Years, Forever. – This starts as ‘why does this exist?’ and slowly gets better as you keep scrolling.
- How I use git worktrees –
git worktreesseem kinda magical. ‘In this way, I have branches that are a bit less stateful than the normal way of using git.’ which seems importand from what I know of AI code agents. Which, admittedly, is not too too much. - The risks of user impersonation – Impersonation code is second only to billing code in terms of risks.
- Why Amazon Never Makes The Same Mistake Twice – I’ve never heard of COE (Correction of Error) docs before. This is interesting. Amazon is really weird on the inside. But this is worth stealing.
- awskillswitch – That is a lot of warnings about usage. I think I am glad there are currently no open issues, or prs. And only 23 forks. It hasnt been updated in 3 years so I suspect the forks are for new things.
- AWS NAT Gateway – Interactive guide to this. It is pretty neat. They also have one for S3 Storage Classes: Fast Acces
- cloud-snitch – ‘Map visualization and firewall for AWS activity, inspired by Little Snitch for macOS.’
- ripgrep – Has a ‘why should I use’ and ‘why shouldn’t I use’ section. Which is nice.
- lights-off-aws – ‘Stop EC2 instances and RDS/Aurora databases overnight by tagging them with cron schedules, to cut AWS costs.’ Remember when this was /the/ talking point about automation environments when EC2 was new?
- Fantastic AWS Policies and Where to Find Them –‘You can’t secure what you can’t see.’
- Eleventeen ways to delete an AWS resource – This (lack of consistency) is the downside of ‘2 pizza box teams’.
- What Does a ‘Sovereign Cloud’ Really Mean? – ‘Cloud infrastructure from American companies, whether located in Europe or Canada, is incompatible with sovereignty.’
- pathfinding.cloud – ‘tools to understand and detect IAM-based privilege-escalation attacks in AWS so you can remediate misconfigurations before they’re exploited’