4 ms·
I had this experience with AWS earlier this week. ======== Hello, This is a reminder to update your policies to avoid changes to your access to AWS Billing,
by jvolkman 3y ago
I had this experience with AWS earlier this week.
========
Hello,
This is a reminder to update your policies to avoid changes to your access to AWS Billing, Cost Management and Account consoles. Our records indicate that you are still using retired actions to access these consoles.
If your policies are not updated with new actions by December 11, 2023, your users’ access to the AWS billing, Cost Management, and Account consoles will be affected.
The policies that need to be updated to include the new fine-grained actions are listed in the “Affected Resources” tab of the AWS Health Dashboard in the “Policy | Policy Name | Policy ARN | Type” format.
To help you with the migration, we have published a mapping between old and new actions in our user guide [1]. If you need to update policies across multiple member accounts in your organization, we have built bulk policy migration scripts to help you update all policies quickly and securely from your management account. See the bulk policy migration scripts user guide [2] for more information. You can find a detailed guide on how and which policies you need to update on our blog [3] and definitions of new IAM actions in Cost Management [4] and Billing [5] user guides.
AWS will not be able to grant further exceptions after December 11, 2023, so we strongly recommend that you act promptly to migrate your policies to new actions.
If you have more questions or need help make updates to your policies, please contact AWS Support [6].
Sincerely,
Amazon Web Services
========
Not only did they send me this email, they sent me 10 copies - one for each account we have. Pages and pages of documentation, steps to follow, Cloud Formation stacks to create, Python scripts to run, etc. I'm still not completely sure what the problem was or what is supposedly improved, or if I would've actually lost access to anything, but hopefully the emails stop now.
- mh- 3y agoI've been getting these too, and it all feels very messy and out of character for AWS. If automatable changes are required.. pop up a dialog and ask me to confirm them?
- coredog64 3y agoThe automation all happens on your side of the control plane. AWS isn’t going to update IAM roles for any customer. The closest you get is that roles can consume managed policies, and those could change but you know that going in.
- grumple 3y agoI run things at a mid sized company and I get AWS emails like this daily. There's always something that needs attention. Except sometimes it doesn't really need attention. Other times it's something absolutely critical. Sometimes can't tell unless I read 50 pages of documentation and talk to their support. Meanwhile at my old job, we had actual servers and vms in house. We had a machine running some obscure service sitting in a corner for two decades with no problems. Magical.
- AwaAwa 3y agoCloud opex is high. And I don't mean the bill. Though the former does add to the latter.
- icedchai 3y agoOk, so don't change or upgrade anything for years. Sounds like a good solution. /s What happens when your VM host craps out and nobody knows how to restore it? I once had a contract job at place that hadn't updated their systems in over 5 years. One server, a VM like you describe, had a 1500 day uptime. The VP/CIO was in a panic because nothing was supported anymore.
- pargon 3y agoI've built a startup on AWS, and same. Since we started about a year ago, I've gotten two "action required" messages from AWS. One involved migrating our Go-based lambdas from the "Go 1.x Runtime" to a more generic one that AWS wants to use for compiled binaries across languages. They provided a very helpful guide, including the Cloudformation template changes. I implemented them, and they worked perfectly just as promised. The other message I got was rather urgent and telling me I need to upgrade the SSL cert on my RDS. The due date on that action is August 22, 2024. There are a few areas of AWS I've found to be pretty abandoned. (Don't try to send push notifications using the AWS Platform Application + SNS approach, woof.) But overall, I've been very happy with AWS as a developer.
- jay_kyburz 3y agoOh we are posting emails. Here is one from google I have been ignoring because updating the app is so far down my todo list it will just never happen. ======== This is your final reminder: By November 1, 2023 version 4 will be deprecated and any updates to existing apps will first require you to migrate to PBL version 5 or newer. We are sending you this reminder as one or more of your apps is still using Play Billing Library (PBL) version 4. Important notes: If your app is targeting Android 14 or higher, you must update to PBL 5.2.1 or PBL 6.0.1 or higher. In May we launched Play Billing Library 6.0 with updates to subscription features, in-app purchase logging, and new API insights. We highly recommend upgrading directly to version 6.0 to future-proof your integration for the next two years and take advantage of the latest tools and features our commerce platform has to offer.
- Terretta 3y agoWorking for two years is "future-proof". Says as much in a few words as the original article.
- jay_kyburz 3y agoTo be fair, this email doesn't say they are going to stop collecting payments, or that they will remove the app from the play store, only that I will not be able to update it. And given I haven't updated this one is a very very long time, its not really a big deal. I would be more upset if they actually remove the app from the app store. I'm looking at you Apple.