A software-as-a-service (SaaS) company manages separate AWS accounts for its development, staging, and production environments. The finance team wants to receive a single monthly invoice for all accounts and benefit from aggregated volume pricing discounts for storage. At the same time, the security team must prevent users in the development accounts from deleting Amazon S3 buckets, even if those users have administrator permissions within their local accounts. Which of the following solutions should the company implement?
- AAWS Organizations with billing-only features enabled, combined with VPC Peering connections between all member accounts to share pricing tiers.
- BIndividual AWS accounts linked using AWS Billing Conductor, with an IAM policy configured directly by the AWS account root user of each member account.
- AWS Organizations with consolidated billing enabled, and a Service Control Policy applied to the development accounts.Cevap
- DAWS Billing and Cost Management console linked to AWS IAM Identity Center, with the AWS Shared Responsibility Model configured to prevent bucket deletion.
Cevap
AWS Organizations with consolidated billing enabled, and a Service Control Policy applied to the development accounts.
AWS Organizations allows organizations to centrally manage billing and permissions across multiple AWS accounts. Enabling consolidated billing generates a single monthly invoice for the management account and aggregates usage across all member accounts to qualify for volume pricing discounts. Furthermore, Service Control Policies (SCPs) can be applied to organizational units or specific member accounts to restrict maximum permissions—such as preventing S3 bucket deletion—which overrides even administrative permissions within those member accounts.
Adım Adım Çözüm
Anahtar Kavram
Consolidated Billing and AWS Organizations
Tahmini Süre:1m 30s