780 karma · joined July 29, 2012
INGREDIENTS: MADE FROM ROASTED PEANUTS AND SUGAR, CONTAINS 2% OR LESS OF: MOLASSES, FULLY HYDROGENATED VEGETABLE OILS (RAPESEED AND SOYBEAN), MONO AND DIGLYCERIDES, SALT.
Oh, maybe molasses (and yes probably the salt) is the flavor note I'm hung up on.
Anyway this is such a pure food-industrial-complex product that I am sure the ingredients list amounts to a sort of cover story. FWIW the parent company scores rates just OK on the 'Palm Oil Scorecard' from your linked page: https://palmoilscorecard.panda.org/check-the-scores/manufact...
[0] https://www.politico.com/story/2019/04/24/ireland-data-priva...
- launch instance A
- create a new CAT and activate it in the Billing console
- apply CAT to instance A
- get no cost data back for that instance in Cost Explorer filtering on that CAT
- terminate instance A
- launch instance B
- apply CAT to instance B
- get cost data back for that instance in Cost Explorer filtering on that CAT
It was explained to me by AWS support that this is in fact how it works, after I opened a case into why I wasn't getting full data back for some legacy stuff. So for any new account I would say that your tagging scheme should get built first, before infrastructure or anything else.At least, if you're very good and don't mind being perceived as a roadblock, you try to understand things. If you're more typical, you just find the most direct route from logged error to added permission (audit2allow approach). And if you're bad, which is also not uncommon, you just give it the broadest permissions possible and call it a day.
With respect to IAM in particular, I'm finding in the Lambda world that some seemingly straightforward functions wind up needing some sort of access to all kind of other AWS services; these services each have their own funky permissions structures and attendant quirks. Each one is a temptation to the IAM admin to just throw their hands in the air and put a wildcard on it.
[0] "an emotion variously combining dread, veneration and wonder" https://www.merriam-webster.com/dictionary/awe
Also, I thought the --security flag did not have any effect on CentOS?
Orwell is claimed by partisans of all kinds due to his great reputation as a moral thinker and his willingness to criticize political actors & ideologies across the spectrum. Consequently his writings are often misquoted, misattributed or taken out of context. The "rough men stand ready to do violence on our behalf" one is a classic example.
Citation needed, I know. There’s a relevant article about this phenomenon out there somewhere, if I can find it I’ll post a link.
I had to dig around to find a page [2] that had some useful instructions allowing me to find out what the actual status of my Windows install was. I'm grateful to the author of that page, they provided critical info that neither Microsoft nor my machine's manufacturer did. I wish I could say that it boggles my mind that they could be so hushmouthed on the subject of a vulnerability this severe. Of course, my OEM (Lenovo) has not released an update for my Windows laptop (Yoga 900) since 2016, and as of today their support page [3] on Meltdown/Spectre does not indicate that they plan to do so.
I'm posting this partly in anger/despair, partly in the hope that I'm wrong and that someone will pop up to comment and tell me there's a fix. There is a Linux BIOS for this machine but it's old and I don't know if it will actually address this issue.
[1] https://support.microsoft.com/en-us/help/4056892/windows-10-... [2] https://www.bleepingcomputer.com/news/security/list-of-meltd... [3] https://support.lenovo.com/us/en/solutions/len-18282