all right. So before we dive into I am, I wanted to talk a little bit about eight of us organizations which kind of focuses on the organization of multiple AWS accounts and security and compliance for all of that. So
a dubious organizations is a newer service, Um,
and has been pretty. It's been pretty helpful. I know for me in my organization, um, as far as managing all the accounts that we have, So when you have multiple a devious accounts, you know, you're usually gonna be using them for different purposes. Maybe you have a dubious accounts that handle que environments. You have an abusive accounts that handle
infrastructure for whatever business is whatever
applications were running and internally, you may have heard of this accounts for specific projects that you're working with and having an AWS organization accounts that that handles all those other accounts. All those sub accounts, if you will,
is a really great way to keep in charge or keep on top of the building.
Ah, you know, keep on top of her. Done in service is and resource is that don't need to be deployed anymore
and just really be able to audit and monitor and secure all of your environment. So here's some of the key bullet points. It does allow you to manage the finding organization. Your accounts. You can control access and permissions to your accounts kind of keeping more. You know, tighter guard rails on who has access to what and each accounts.
Like I said, you can audit, monitor and secure environment for compliance.
Ah, you can share Resource is across multiple accounts. That's also really great benefit Essentially manage costs and building within your atavus organization account. And this is what I mean here. Ah, So obviously, this is your head honchos accounts. This is your organization account and then here you might have softer development team won and suffer development team too.
Any of the other accounts
as well. These air the sub accounts
and so you can you can designate your compliance requirements for each accounts will say this one has to be hip a compliant. This one has to be PC a compliant. They don't have to cross over, but you need to be able to handle the building
and the you know both the compliance requirements still like that within your head account within eight of these organizations.
It's a really great way to distribute access to your devil up steam or developer teamwork. You're a team for that specific team environment,
but they don't necessarily have to have access to your organization's either. So you can kind of reduced who has access to what, thus keeping your internal security posture. And, you know, only leaving this open to senior management directors things like that who need access to the organizational accounts.
So it's a really helpful thing. I'm not gonna go too far in depth into it because this is, of course, primarily focused on I am.
But it is worth mentioning organizations as part of the security of your your accounts. And so you know whether you're gonna be pursuing it obvious security specialty exam or you just want to learn how to secure your obvious environments.
This is definitely a topic worth noting, and I encourage you to read more and even play with it on your own, so
hopefully this was helpful. I'll see you guys and the next lecture