A Solutions Architect is designing a secure multi-account environment for a growing enterprise. The company's security policy requires centralized access management for employee identities, enforcement of compliance guardrails across all member accounts in the organization, and preventing individual account administrators from disabling logging or modifying centralized security resources. Which architectural strategy best meets these requirements?
- Configure AWS IAM Identity Center for centralized single sign-on access, and use AWS Organizations to apply a Service Control Policy (SCP) at the organizational unit level that denies CloudTrail deletion and S3 log bucket modifications.Cevap
- BCreate individual IAM users in each member account with long-term credentials synchronized to the corporate directory, and use IAM policies in each account to restrict access to log settings.
- CUse the management account root credentials to configure administrative access across member accounts, and attach an IAM policy to the root user to enforce logging compliance.
- DConfigure federated access using individual IAM users in the management account, and store administrative access keys as plaintext in Systems Manager Parameter Store parameters for automated compliance checking.
Cevap
Configure AWS IAM Identity Center for centralized single sign-on access, and use AWS Organizations to apply a Service Control Policy (SCP) at the organizational unit level that denies CloudTrail deletion and S3 log bucket modifications.
The correct strategy combines AWS IAM Identity Center for centralized, federated access (avoiding individual IAM users and long-term credentials) with AWS Organizations SCPs applied at the OU level to prevent member account administrators from disabling CloudTrail or altering S3 logging resources.
Adım Adım Çözüm
Anahtar Kavram
Centralized multi-account governance using Service Control Policies and federated identity integration via AWS IAM Identity Center.