How can this request be fulfilled?
Use Amazon CloudWatch Events to schedule a billing inquiry on a bi-weekly basis. Use AWS Glue to convert the output to CSV.
Set AWS Cost and Usage Reports to publish bills daily to an Amazon S3 bucket in CSV format.
Use the AWS CLI to output billing data as JSON. Use Amazon SES to email bills on a daily basis.
Use AWS Lambda, triggered by CloudWatch, to query billing data and push to Amazon RDS.
Explanations:
AWS CloudWatch Events can schedule tasks, but AWS Glue is not necessary for converting billing data to CSV. AWS Cost and Usage Reports can directly generate CSV files without needing Glue.
AWS Cost and Usage Reports can be set up to publish billing data daily in CSV format to an S3 bucket, which is easily accessible for spreadsheet applications.
The AWS CLI can output billing data as JSON, but sending it via Amazon SES does not directly meet the requirement for a format easily viewed in a spreadsheet. CSV would be more appropriate.
While AWS Lambda can process billing data, querying and pushing to Amazon RDS is unnecessary for this task. The simplest solution is using AWS Cost and Usage Reports to publish to S3 in CSV format.
As I understand it, the answer is:
Set AWS Cost and Usage Reports to publish bills daily to an Amazon S3 bucket in CSV format.
If I had to guess, I’d say the answer is:
Set AWS Cost and Usage Reports to publish bills daily to an Amazon S3 bucket in CSV format.