SAP-C02 · Question #713
A company that has multiple business units is using AWS Organizations with all features enabled. The company has implemented an account structure in which each business unit has its own AWS account…
The correct answer is B. In the organization's management account, configure an S3 event to invoke an AWS Lambda. To enable business unit administrators to query only their own cost data using Amazon Athena from a central Cost and Usage Report (CUR) with least operational complexity, an automated data partitioning solution is needed. An AWS Lambda function triggered by S3 events can…
Question
A company that has multiple business units is using AWS Organizations with all features enabled. The company has implemented an account structure in which each business unit has its own AWS account. Administrators in each AWS account need to view detailed cost and utilization data for their account by using Amazon Athena. Each business unit can have access to only its own cost and utilization data. The IAM policies that govern the ability to set up AWS Cost and Usage Reports are in place. A central Cost and Usage Report that contains all data for the organization is already available in an Amazon S3 bucket. Which solution will meet these requirements with the LEAST operational complexity?
Options
- AIn the organization's management account, use AWS Resource Access Manager (AWS RAM) to
- BIn the organization's management account, configure an S3 event to invoke an AWS Lambda
- CIn each member account, access AWS Cost Explorer. Create a new report that contains relevant
- DIn each member account, create a new S3 bucket to store Cost and Usage Report data. Set up a
How the community answered
(50 responses)- A12% (6)
- B64% (32)
- C18% (9)
- D6% (3)
Why each option
To enable business unit administrators to query only their own cost data using Amazon Athena from a central Cost and Usage Report (CUR) with least operational complexity, an automated data partitioning solution is needed. An AWS Lambda function triggered by S3 events can process new CUR files in the central bucket, extract account-specific data, and store it in separate S3 prefixes or buckets, allowing each business unit to query only its relevant data with Athena.
AWS Resource Access Manager (AWS RAM) is used for sharing AWS resources like VPCs or Transit Gateway attachments and does not provide a mechanism for fine-grained data filtering within an S3 bucket for Athena queries based on data content.
Configuring an S3 event to invoke an AWS Lambda function allows for automated processing of new Cost and Usage Report (CUR) files as they are delivered to the central S3 bucket. The Lambda function can then parse the CUR data, filter it by account ID, and store the account-specific data in separate S3 prefixes or buckets, ensuring each business unit can only access and query its own detailed cost and utilization data using Amazon Athena. This approach centralizes the CUR setup while distributing access to partitioned data with minimal ongoing operational overhead.
AWS Cost Explorer provides reporting and analysis capabilities but does not allow direct integration with Amazon Athena for querying raw Cost and Usage Report data in a granular, partitioned manner.
Creating new S3 buckets and setting up separate AWS Cost and Usage Reports (CURs) in each member account would increase operational complexity and contradict the existing central CUR setup for the organization.
Concept tested: Centralized cost management, data partitioning, and Athena access control.
Source: https://aws.amazon.com/blogs/mt/build-a-serverless-data-lake-to-analyze-your-aws-cost-and-usage-report/
Community Discussion
No community discussion yet for this question.