New serverless pattern - lambda-invoicing-bedrock-cdk

[NithinChandranR-AWS]

Summary

New pattern: Automated AWS Invoice Retrieval and Analysis with Amazon Bedrock

Amazon EventBridge triggers an AWS Lambda function monthly that retrieves invoices via the new AWS Invoicing APIs (ListInvoiceSummaries, GetInvoicePDF), archives PDFs to Amazon S3, and generates cost analysis summaries using Amazon Bedrock.

Pattern details

• Language: Python
• Framework: AWS CDK
• Level: 200

Composition

• Amazon EventBridge — monthly scheduled trigger
• AWS Lambda — orchestrates invoice retrieval and analysis
• AWS Invoicing APIs — programmatic invoice access (launched June 25, 2026)
• Amazon S3 — PDF archive with lifecycle transitions
• Amazon Bedrock (Claude Sonnet 4) — cost analysis and optimization recommendations

Removing any service breaks the pattern: no EventBridge = no automation, no Lambda = no orchestration, no S3 = no archive, no Bedrock = no intelligent analysis.

Testing

Deployed and tested in us-east-1. Results:

• 1 invoice retrieved
• PDF archived to Amazon S3
• Amazon Bedrock generated structured executive summary with spend breakdown and recommendations

[NithinChandranR-AWS]

"What does this solve that Cost Explorer doesn't?"

The Real Enterprise Pain Point

Enterprise customers have:

1. Multiple AWS Organizations (M&A, subsidiaries, regional entities, MSP-managed accounts)
2. Invoice Units mapped to business entities (BU chargebacks, cost centers, legal entities)
3. Monthly close cycles where finance teams manually download 50-200 PDFs from different payer accounts, rename them, reconcile them against POs, and feed them into SAP/Oracle ERP

The June 25, 2026 blog quotes: "If you manage invoices for dozens or hundreds of AWS payer accounts, you face repetitive console logins, individual file downloads, and manual data entry into your financial systems."

hence the PR. Thanks.