Рет қаралды 27,459
The most secure option to isolate workloads from each other is to use multiple AWS accounts. Many organizations use different AWS accounts for testing and production, for example. The more AWS accounts you use, the more complicated it gets to manage users and grant them access.
Formerly, using IAM roles for cross-account access was a popular pattern. How did that work in practice? Often, everything started with an AWS account that contained nothing but the IAM users and groups, allowing engineers to authenticate. Besides that, account administrators added IAM roles for cross-account access to every AWS account.
In this video we will show you an alternative approach with Amazon Web Services Single Sign-on or AWS SSO.
Interested in more? Check out this blog post: cloudonaut.io/aws-sso-instead...
Chapters:
00:00 - Intro
01:04 - Why you need multiple AWS Accounts
02:04 - Explaining AWS Single Sign-On (SSO)
03:23 - AWS Single Sign-On (SSO) Costs
03:42 - Using IAM Users in AWS
05:20 - Why you should consider AWS Single Sign-On (SSO)
06:10 - Demo: How AWS SSO works
16:36 - Wrap Up
17:31 - Outro
Support us:
Have you learned something new by reading, listening, or watching our content? If so, we kindly ask you to support us in producing high-quality & independent AWS content. We look forward to sharing our AWS knowledge with you. cloudonaut.io/support-us/
#aws #amazonwebservice #cloudcomputing #cloudonaut #iamusers #iam #sso #singlesignon