Automate AWS Cost Reports with Python, boto3, and SES
The article discusses the problem of surprise AWS bills and the lack of cost visibility in many teams. It highlights the symptoms of this issue, including finance teams sending messages about unexpected bill spikes and engineers being unable to answer immediately. The article aims to provide a solution to this problem by automating AWS cost reports using Python, boto3, and SES.
- ▪Many teams lack cost visibility, leading to surprise AWS bills and post-mortem analyses.
- ▪The AWS Cost Explorer API has several non-obvious activation and usage requirements that create friction.
- ▪Automating cost reports using Python, boto3, and SES can help shift visibility from invoice to inbox.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/oleksandr_kuryzhev_42873f/automate-aws-cost-reports-with-python-boto3-and-ses-4keg |
| Publication time | Tue, 30 Jun 2026 07:02:43 +0000 |
| Retrieval time | 2026-06-30T07:24:23.532Z |
| Last seen | 2026-06-30T07:24:23.532Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | JK2TjMOvAm69 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3970301) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Oleksandr Kuryzhev Posted on Jun 30 • Originally published at kuryzhev.cloud Automate AWS Cost Reports with Python, boto3, and SES #python #aws #devops Originally published on kuryzhev.cloud Your AWS bill already increased by the time you open Cost Explorer — here's how to make Python tell you before finance does. Last month a team I was working with got a Slack message from their finance lead: "Why did AWS spend jump 40% this month?" Nobody in engineering knew.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
