Examkin

Soru

Zorluk: Çok zorAWS Budgets and Cost Alerts

A company has a multi-account organization managed by AWS Organizations. A SysOps administrator needs to enforce strict cost controls in a development sandbox account. If the monthly forecasted cost for the sandbox account exceeds $5,000, all running Amazon EC2 instances in that account must be stopped automatically. The administrator wants to implement this solution with minimal custom code and administrative overhead. Which configuration will meet these requirements?

  1. Create an AWS Budget with a monthly cost budget for the sandbox account, set to trigger a budget action when the forecasted spend exceeds $5,000. Create a custom IAM role with a trust policy for the budgets.amazonaws.com service principal and an execution policy allowing ec2:StopInstances and ec2:DescribeInstances actions. Grant the administrator iam:PassRole permissions for this custom role in their IAM policy.Cevap
  2. B
    Create an AWS Cost Anomaly Detection monitor with a threshold of $5,000. Configure an anomaly subscription to send alerts to an Amazon SNS topic. Subscribe an AWS Lambda function to the SNS topic to stop all running EC2 instances in the sandbox account.
  3. C
    Create an Amazon CloudWatch billing alarm that monitors the total monthly charges for the sandbox account and triggers when it exceeds $5,000. Configure the alarm to send a notification to an Amazon SNS topic, and use AWS Systems Manager Automation to automatically stop EC2 instances when the SNS topic receives the alarm.
  4. D
    Create an AWS Budget with a monthly cost budget for the sandbox account, set to trigger a budget action when the forecasted spend exceeds $5,000. Configure the budget action to use the AWS service-linked role AWSServiceRoleForBudgets to stop the EC2 instances, and grant the administrator sts:AssumeRole permissions for this service-linked role in their IAM policy.

Cevap

Create an AWS Budget with a monthly cost budget configured to trigger a budget action based on forecasted spend. Associate this action with a custom IAM role that trusts budgets.amazonaws.com and has ec2:StopInstances permissions, ensuring the administrator has iam:PassRole permissions for that role.
The correct configuration uses AWS Budgets to alert on monthly forecasted costs and leverages native Budget Actions to stop the EC2 instances. To allow AWS Budgets to act on the administrator's behalf, a custom IAM role trusting the budgets.amazonaws.com service principal must be created with ec2:StopInstances permissions, and the administrator must have iam:PassRole permissions to associate that role with the budget action.

Adım Adım Çözüm

1
Determine the type of cost trigger needed.
The requirement is to trigger based on 'forecasted' cost. AWS Budgets supports forecasted triggers, whereas CloudWatch billing alarms only support actual metrics.
This rules out CloudWatch billing alarms as a primary mechanism.
2
Identify the service suited for enforcing static thresholds with automated actions.
AWS Budgets offers Budget Actions to automatically stop EC2 or RDS instances. AWS Cost Anomaly Detection is designed for machine-learning-driven pattern anomaly detection rather than static limits.
This rules out Cost Anomaly Detection.
3
Configure the required IAM permissions for AWS Budgets Actions.
Create a custom IAM role that trusts budgets.amazonaws.com and has the policy to perform ec2:StopInstances. Grant iam:PassRole permissions to the administrator's policy so they can assign the role to the budget.
AWS Budgets Actions does not use service-linked roles for target instance control, and configuring it requires iam:PassRole, not sts:AssumeRole.

Anahtar Kavram

AWS Budgets Actions IAM Requirements and Cost Monitoring Differentiation
Bu soruyu puanla

Konular

AWS Budgets and Cost Alerts

Bu konudan daha fazla soru