Developer Finds $13 in Forgotten AWS Charges After First Detailed Bill Audit

·1 views

A developer studying for AWS certifications conducted a line-by-line audit of their AWS account and discovered $13.16 in charges spread across four services, including an EC2 instance they had forgotten to shut down after a study group project. The EC2 server in US East Ohio accounted for $8.25, while an attached public IPv4 address — which AWS began charging for in 2024 — added another $3.67 in unexpected fees. Route 53 DNS hosting for two domains cost $1.01, and a low-traffic static site on AWS Amplify added just $0.23. After confirming the idle EC2 instance was not serving any live site, the developer terminated it, reducing their projected monthly bill to approximately $1.64. The experience highlighted the importance of regularly reviewing cloud bills, understanding the difference between services, and choosing cost-appropriate tools like Amplify over EC2 for static websites.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Developer open-sources high-performance Solana copy-trading bot built in Rust

A developer has released an open-source copy-trading bot for the Solana blockchain, written in Rust and available on GitHub under the handle DexCrancer. The bot monitors a target wallet's on-chain activity and automatically mirrors its trades on decentralized platforms Raydium and Pump.fun in near real-time. It is designed for developers working in Solana Web3, offering a full-stack architecture that includes wallet integration, on-chain logic, a backend API with WebSockets, and a frontend UI. Users can backtest strategies, apply custom risk rules, and extend the bot with their own market filters before deploying with real capital. The project is intended purely for educational purposes, with the author noting that trading involves risk and users should comply with applicable local laws.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How FIFA pre-sets the 2026 World Cup bracket before third-place teams are known

The 2026 FIFA World Cup features 48 teams across 12 groups, with the top two from each group advancing automatically to make 24 qualifiers. To complete a 32-team knockout bracket, the eight best third-placed finishers from across all 12 groups are also admitted, but their identities are unknown until the group stage ends. Despite this uncertainty, the bracket structure — determining who plays whom and where — is fixed well in advance of any matches being played. FIFA achieves this by pre-mapping all possible combinations of which eight groups produce the qualifying third-place teams, assigning each combination a predetermined set of matchups. A key constraint in the draw is that no third-place team can be drawn against the group winner from their own group, since the two sides already met during the group stage.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

DocuShark Launches Collaborative Document Hub With Offline and AI Agent Support

DocuShark has launched a document collaboration platform designed to consolidate multiple work tools into a single hub. The editor supports real-time collaborative editing, simultaneous writing, drawing, and file storage within a single document. Users can continue working offline, with changes syncing automatically once they reconnect to the internet. The platform is built with AI agent integration in mind, offering features like citations, field-based duplication prevention, and targeted edits via MCP endpoints. DocuShark positions itself as an integration layer rather than a competitor to existing tools, aiming to reduce knowledge fragmentation across platforms.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Kiponos Java SDK Lets Ops Tune Saga Timeouts Live Without Redeployment

Managing distributed checkout sagas across inventory, payment, and shipping services traditionally requires hardcoded timeouts scattered across multiple Spring Boot configuration files or Helm deployments. Kiponos.io addresses this by providing a shared, hierarchical config tree where every saga participant reads step timeouts, retry budgets, and compensation triggers from local in-memory cache. When operators update a value in the Kiponos dashboard, WebSocket deltas propagate the change to all connected JVMs instantly, eliminating the need to roll out new deployments across services. Each service reads only its relevant subtree locally, keeping the saga executor hot path fast while remaining responsive to live operational changes. This approach allows NOC and risk teams to adjust saga behavior — such as extending a payment timeout during a card processor slowdown — in real time without waiting for a deployment cycle.

0 comments Read more at DEV Community