Which combination of solutions will meet these requirements?
(Choose three.)
Use AWS Budgets to create a budget. Set the budget amount under the Cost and Usage Reports section of the required AWS accounts.
Use AWS Budgets to create a budget. Set the budget amount under the Billing dashboards of the required AWS accounts.
Create an IAM user for AWS Budgets to run budget actions with the required permissions.
Create an IAM role for AWS Budgets to run budget actions with the required permissions.
Add an alert to notify the company when each account meets its budget threshold. Add a budget action that selects the IAM identity created with the appropriate config rule to prevent provisioning of additional resources.
Add an alert to notify the company when each account meets its budget threshold. Add a budget action that selects the IAM identity created with the appropriate service control policy (SCP) to prevent provisioning of additional resources.
Explanations:
AWS Budgets does not set budget amounts under the Cost and Usage Reports section; budgets are created and managed through the Billing dashboard.
AWS Budgets allows users to create budgets and set budget amounts through the Billing dashboard, which is the correct location for managing budget settings for AWS accounts.
Creating an IAM user for AWS Budgets is not required; AWS Budgets uses IAM roles for permissions to execute actions, rather than requiring a separate IAM user.
Creating an IAM role for AWS Budgets is necessary to grant the appropriate permissions for budget actions, allowing AWS Budgets to perform tasks like preventing resource provisioning.
While adding alerts and actions to notify when budget thresholds are met is necessary, budget actions must be associated with an IAM role or SCP, not just an IAM identity without context.
Adding alerts and budget actions that leverage service control policies (SCP) allows for preventing additional resource provisioning when budget thresholds are met, aligning with AWS Organizations’ governance.