Easy ReviewSAA-C03
Design Secure Architectures11

Multi-account strategy

Separate workloads and shared services, automate account baselines, and protect central audit evidence.

Este conteúdo de estudo ainda não foi traduzido, então aparece em inglês. Ajude a traduzir

Use account boundaries to separate responsibilities. Apply organization controls, deploy common resources, and keep security administration and audit storage apart from application workloads.

Account boundaries and shared services

An AWS account is an isolation boundary for resources, access, and billing. Separate accounts let teams apply different controls and limit how far an operational or security mistake can spread.

How it works

  1. Separate production and non-production workloads into accounts. Account-scoped quotas and API request limits are also distributed across those accounts.

  2. Group accounts into organizational unitsAn organizational unit groups AWS accounts with common governance requirements. (OUs), groups that share governance requirements. Base the structure on security and operational needs.

  3. Separate shared responsibilities.

    Account Responsibility
    Management Organization administration; keep application workloads elsewhere
    Security tooling Operate security services across accounts
    Log archive Ingest and archive logs separately from workloads
    Network Operate shared networking infrastructure
    Shared services Host services used by multiple teams
    Application Run application workloads
  4. Use AWS RAM resource shares for supported resources that several accounts need. Enable organization sharing through RAM to create its required service-linked roleA service-linked role is a role that an integrated AWS service uses to perform its required tasks., a role reserved for that service.

  5. For cross-account shares, the RAM managed permission sets the maximum actions. The consumer account must grant its identities access too. For role-based access, configure destination role trust and permissions and allow the originating identity to assume it.

  6. A network account can share VPC subnets with accounts in the same organization. Each participant manages its own resources, not another participant’s resources.

  7. Enable organization sharing from the management account through RAM with all Organizations features and the required RAM, IAM and Organizations permissions. Sharing does not raise the resource owner’s quota.

Exam cues

  • If the question says development changes must not affect production access or quotas, think separate accounts, because accounts create access boundaries and distribute account-scoped limits.
  • If the question says many accounts need the same supported infrastructure resource, think RAM, because sharing gives access without creating a separate resource in every account.
  • If the question says protect workload data from workload administrators, think a separate log archive or data account with restricted access, because account access is separate by default.
  • If a RAM share exists but a workload role is denied, check its identity policy as well as the share’s managed permission.
  • If a developer needs access to a bucket in another account, think an IAM role with destination trust and permissions and an sts:AssumeRole grant in the originating account.
  • If the question says new accounts in an organization need higher quotas automatically, think a Service Quotas quota request template, because it requests increases at account creation.

Remember

  • Group OUs by control requirements.
  • SCPs do not constrain the management account.
  • Ordinary RAM shares inside an enabled organization do not require invitations.
  • Sharing a resource does not raise the owner’s quota.

Trap: An OU groups accounts for governance. It does not replace the account boundary or automatically grant access between accounts.

Share a supported resource across accounts
12Resource owneriRAM shareiConsumer accounti
  1. The resource owner creates the share in RAM.

  2. An authorized consumer gains access to the shared resource.

Detalhes das caixas (3)
Resource owner

The owning account creates a RAM resource share.

RAM share

The share specifies a supported resource and an account, OU, or organization.

Consumer account

The consumer accesses the shared resource under the share permissions.

Da documentação da AWS (16)
  • AWS accounts provide security, access, and billing boundaries; access between accounts is not allowed by default.
  • Use separate accounts for production and non-production workloads to apply distinct controls and isolate resources and data.
  • Group accounts into organizational units by security and operational requirements rather than copying the reporting hierarchy.
  • Avoid application workloads in the management account and restrict access because SCPs do not constrain that account.
  • AWS SRA separates security tooling, log archives, network infrastructure, and application workloads into dedicated accounts.
  • A shared services account hosts services used by multiple applications and teams.
  • Multiple accounts distribute account-scoped service quotas and API request rate limits.
  • AWS RAM shares supported resources with accounts, organizational units, or the organization.
  • With RAM organization sharing enabled, normal shares inside the organization do not require invitations; retain-on-leave account shares are an exception.
  • Enable organization sharing through RAM so that its required service-linked role is created.
  • For a cross-account RAM share, its managed permission sets the maximum available permissions; the consumer account must also grant its users or roles access through identity policies.
  • A VPC owner can share subnets with accounts in the same organization; participants manage their own resources but cannot manage other participants' resources.
  • Cross-account role access requires destination-role trust and permissions plus permission for the originating identity to assume the role.
  • Enabling RAM organization sharing requires all Organizations features, a management account principal, ram:EnableSharingWithAwsOrganization, iam:CreateServiceLinkedRole, organizations:EnableAWSServiceAccess, and organizations:DescribeOrganization.
  • Sharing a resource does not change the permissions or quotas applying to it in its owner account.
  • With Service Quotas trusted access in AWS Organizations, a quota request template automatically requests quota increases when new accounts are created in the organization.

Flashcards

toque para virar
Resposta

·

Todos os 11 flashcards em lista

Why use separate AWS accounts for production and development rather than only separate VPCs?

Accounts provide security, access, and billing boundaries and allow different controls for production and non-production.

A company wants AWS organizational units to mirror every manager and reporting line. What grouping principle should it use?

Group accounts by shared security and operational requirements so controls match the accounts they govern.

Which dedicated AWS accounts separate security operations from audit-log storage?

A security tooling account operates security services; a log archive account ingests and archives logs.

A platform team wants to share supported network resources with an entire OU without invitation handling. What should it configure?

Enable AWS RAM sharing with Organizations through RAM, then create an organization resource share for the OU.

Should an application be deployed in the AWS Organizations management account so that an SCP can protect it?

No. SCPs do not constrain the management account. Keep application workloads in member accounts and restrict management-account access.

A workload account cannot use a subnet shared by AWS RAM even though the share permits the operation. What permissions should its administrator check?

Grant the workload identity access with an IAM identity policy. The RAM managed permission is a ceiling, not a substitute for the consumer account's identity permissions.

A network account shares an Amazon VPC subnet with workload accounts in its organization. Can one workload account manage another participant's EC2 instances?

No. Participants manage their own resources, not resources owned by other participants.

A developer in one AWS account needs to assume a role to access an Amazon S3 bucket in another account. What must both accounts configure?

The destination role needs trust and bucket permissions; the originating identity needs permission to assume that role.

An administrator enabled trusted access in AWS Organizations but cannot share an OU resource through AWS RAM. What setup is required?

Enable sharing through RAM from the management account with all Organizations features enabled and the required RAM, IAM and Organizations permissions.

A team shares a resource using AWS RAM to avoid the resource owner's quota. Does sharing increase that quota?

No. Sharing does not change the quotas that apply to the resource in its owning account.

Every new account in an AWS organization needs higher quotas for some services from day one. What avoids manual requests per account?

A Service Quotas quota request template with trusted access enabled in Organizations. It requests the increases automatically when accounts are created.

Você concluiu todos os tópicos da SAA-C03!

Seu badge ficou dourado. Próximo passo: agendar a prova na AWS. Depois de passar, adicione-se ao Quem passou.

Compartilhar

Conte que você concluiu esta certificação

Concluí todos os tópicos da AWS Certified Solutions Architect - Associate (SAA-C03) no Easy Review. Venha estudar também!