rusteh1

I'm not a git expert, but how was the attacker able to push the stability branch directly to the Amazon owned repo? The PR would have been to merge the modified branch to main right?

Not true. They are widely available and used in Australia.

Is anyone familiar with the matter able to comment on the use of Torq-set fasteners? Are they a standard for these sort of use cases? They seem to be used frequently in Aerospace? I tend to use Torx whenever possible, are these better? Or should they have used something else to avoid such issues?

I remember my first professional job in 2008 and noticing the lifts in the building had ashtrays in them. I couldn't fathom smoking in such a confined space with others!

My sister-in-law swam the channel a few weeks ago, under the supervision of a pilot from the linked association. A direct point to point swim is around 33km. Due to the tides and the timing of her swim it was a 58km crossing. Incredible!

I feel folks overcomplicate this. At least for the the HN crowd, it is totally possible to eat mostly non-processed, fresh food, don't drink too much booze, and get an average of 30 minutes of incidental exercise a day. Those three things and you are head of 90% of people.

The email is to exec staff, not the entire company? Perhaps a BCC, or maybe just wants the execs to set an example?

Ha, I did have hassio running on a pi, but it killed the SD card twice. Apparently a common issue just due to to the volume of writes...

I'm using an Acer laptop that must be 15 years old for pfsense, never misses a beat, built in UPS! I've got a second laptop, a MacBook air from 2012 running a bunch of containers for Plex, hassio, etc. Works fine. I've got it all in a 19" rack I built out of wood. World's cheapest homelab. Haven't changed it in years.

I previously worked in this space and have a fair bit of experience optimising AWS spend for customers.

Cool idea! I see the pain point you are addressing here is friction in the marketplace, rather than simply cost optimisation? Traditionally the use of standard RIs was a pain, due to the inflexibility of moving between instance families. And the fact that the marketplace requires a US bank account which made it a no-go for non-US customers.

However, these problems were addressed first through the use of convertible RIs. Which allow exchange of instance types, but can't be sold on the marketplace (from memory). But, to be honest, they were still a pain to manage. You needed a good cost person, or a good TAM to keep on top of the required conversions. So, secondly, savings plans were introduced. I generally recommend compute savings plans these days, as they are much more set and forget, though I acknowledge provide less discount than standard RIs. My personal opinion is that EC2 based RIs will probably be deprecated by AWS at some point in the future. For this reason I don't think its likely they'll release this automated marketplace as a feature in future.

I work almost exclusively with enterprise customers and see very little use of standard RIs these days, which given the marketplace angle I'm assuming is the only purchase option you are working with? Are you doing zonal or regional scope? But if you can find an angle that means customers can make more efficient use of standard RIs all the power to you, that is a win!

Recommendation wise, the native tools (Cost Explorer and the CUR) can deliver reasonable recommendations that are good enough for most customers. Especially when using more flexible purchase options like compute savings plans the need to be super accurate just isn't there anymore.