solutions-architect-pro video for you have hired a Cloud consulting agency, Example Corp, to monitor your AWS account and help optimize costs. To track daily
You have hired a Cloud consulting agency, Example Corp, to monitor your AWS account and help optimize costs. To track daily spending, Example Corp needs access to your AWS resources, therefore, you allow Example Corp to assume an IAM role in your account. However, Example Corp also tracks spending for other customers, and there could be a configuration issue in the Example Corp environment that allows another customer to compel Example Corp to attempt to take an action in your AWS account, even though that customer should only be able to take the action in their account. How will you mitigate the risk of such a cross-account access scenario?