A company manages its multi-account environment using AWS Organizations. A SysOps administrator must establish a cost control policy for development sandbox accounts to prevent monthly spending from exceeding a fixed limit of per account. The solution must satisfy the following criteria:
1. If a sandbox account's actual monthly spend reaches of the budget, the account must be immediately barred from provisioning new resources.
2. A notification must be sent automatically to the SysOps team's Slack channel.
Which combination of actions should the SysOps administrator perform to meet these requirements? (Select TWO.)
- Configure the cost budget in the AWS Organizations management account, and define a budget action that applies a restrictive Service Control Policy (SCP) to the target member account. Ensure the IAM identity configuring the budget has iam:PassRole permissions for the role that AWS Budgets assumes.Answer
- Create an Amazon Simple Notification Service (Amazon SNS) topic, configure AWS Chatbot to integrate the SNS topic with the Slack channel, and configure the budget to send an alert to the SNS topic when the limit is reached.Answer
- CConfigure the cost budget directly within the sandbox member account, and define a budget action that applies a local IAM policy to deny resource creation. Create an AWS Chatbot client role with sts:AssumeRole permissions in the member account to deliver the notification.
- DConfigure an AWS Cost Anomaly Detection monitor with a threshold of . Configure the monitor to trigger an AWS Systems Manager Automation document that attaches a restrictive SCP to the member account.
- EConfigure the budget in the sandbox member account to publish alerts directly to the Slack webhook URL. Define a budget action that stops all running Amazon EC2 and Amazon RDS instances in the sandbox account using a local service-linked role.
Answer
Configure the cost budget in the AWS Organizations management account, defining a budget action to apply a restrictive Service Control Policy (SCP) to the target member account while ensuring the configuring IAM identity has iam:PassRole permissions; and create an Amazon SNS topic integrated with AWS Chatbot and the Slack channel to send alerts when the limit is reached.
The correct combination of actions uses AWS Budgets created in the AWS Organizations management account to trigger a native budget action. Since member accounts cannot apply SCPs to themselves, this must be done at the Organization level, requiring the administrator to have iam:PassRole permissions for the role that AWS Budgets assumes. Additionally, sending notifications to Slack is achieved by publishing alerts from AWS Budgets to an Amazon SNS topic, which triggers AWS Chatbot to deliver the message to Slack.
Step-by-Step Solution
Key Concept
AWS Budgets Actions allow organization-wide enforcement (such as applying Service Control Policies) and integration with alerting mechanisms like Amazon SNS and AWS Chatbot for automated notifications.