Who is your 📧 provider?
New AWS Accounts require unique email addresses. How do you manage them?
Good day. This is Unlimited Leave, the AWS Governance and Management email newsletter that comes into your mailbox like a lamb and stays that way.
Short and sweet today.
Meme of the week -
Compliments of fellow ACB Member DMorgan
This week's topics
AWS Organizations Greenfield Content Update
Which email provider do you use?
Governance Announcements and Releases
I’m remembering now why I haven’t generated a ton of static content in the past. Lots of decisions result in fatigue.
I’ve waffled on self-hosting vs. using an LMS Platform for the content and right now I think using a platform will save me time. The solution will also allow you to be more easily review content on the go if that is your thing.
To make things more digestible, I have broken content out into more Modules so I can drip them out more frequently once completed and not cram so much into a single video.
Much about the configuration of a new AWS Organization, or making some of these modifications to an existing Org will be waiting for changes and updates to replicate which in many cases will be 24-72 hours. When these things happen that seems like a logical end to a module and to pick up in the next where that one left off. If you’re just joining me, the original plan can be found here.
Believe it or not, when it comes to governance and management, the foundation is laid long before you deploy your first AWS Account. Part of that is naming convention and communications.
To support the content in the first module, I’d like to know what Email provider you use in your organization. What emails do you use when generating new AWS Accounts? If you were interested in the content (or even if not) I’d love to know what email provider you are using in your companies and for the spawning of new AWS accounts. Please answer this quick form:
AWS Control Tower announces a progress tracker for landing zone setup and upgrades - Cool, no more waiting and staring at a blue banner with a percentage that updates every 15 minutes. At least now we’ll know where in the update process we are or get stuck.
AWS Service Catalog now supports the ability to disassociate and delete products in one action. - helpful in not having to track down deployed resources or worry about terminations that may take place in the removal of a product. I don’t recall ever running into this as an issue. However, as I share in the future content, sharing Portfolios across an Org or Orgs is extremely helpful so this is bound to have an impact on me.
AWS Security Hub launches 7 new security best practice controls - I don’t personally care about ElastiCache but someone might. SIDE NOTE: I don’t recall mentioning the NIST 800-53 Standard being released in Security Hub. If I did, here is a reminder.
Announcing Consolidated Control Findings and a Consolidated Controls View for AWS Security Hub - still overjoyed about this one but I haven’t started consolidation yet. I see a big banner in the console that gave me some reservations. I need to review what I have for notes in disabled and suppressed checks before I flip this switch.