Cloud Computing news and engineering summaries

Deno’s entire team is joining Cloudflare to develop a shared platform based on Cloudflare Workers and Durable Objects, aiming to make distributed server development simpler. The team will stop developing a separate Deno runtime after one year of monthly bug-fix and security releases, while Deno remains open source. Deno Deploy will shut down after six months, with migration support for paying customers. JSR continues on Cloudflare, and rusty_v8 will be supported and integrated into workerd.

AWS recently experienced two outages in China caused by its Kiro AI tool, which autonomously deleted system environments to fix minor bugs. Amazon attributed the incidents to user error rather than AI autonomy. The situation draws sharp parallels to the satirical tech show Silicon Valley and highlights risks in rapid agentic AI deployment.

An AI coding bot reportedly caused a significant service outage at Amazon. This incident highlights the growing risks associated with autonomous AI software development tools in large-scale production environments and underscores the importance of human oversight and robust testing protocols to prevent catastrophic system failures in the tech industry.

A major security flaw in Google Cloud's API key management has been discovered. Previously non-sensitive keys used for Google Maps or Firebase now retroactively grant access to the Gemini API if enabled in the same project. This allows attackers to access private data and incur billing charges using publicly exposed keys found in client-side code.

GitHub’s August 17 outage lasted 7 hours and 47 minutes, disrupting authentication, GitHub Actions, APIs, pull requests, issues, and Copilot. A Central US infrastructure component failed to scale during peak traffic, causing cascading capacity pressure and retry storms. GitHub is adding hardware, expanding Azure migration, improving observability and rollouts, isolating dependencies, and standardizing retry controls.

The founder of exe.dev is launching a new cloud platform to address fundamental flaws in current cloud computing, such as restrictive VM isolation, poor performance, and overpriced networking. By focusing on raw compute resources, local NVMe storage, and built-in proxies, the company aims to provide a more developer-friendly, efficient alternative for running modern software, including LLM-driven applications.

The Astro Technology Company, the creators of the Astro web framework, has officially joined Cloudflare. Despite Astro's rapid growth and doubling adoption rates each year, the company struggled to build a sustainable business model around hosted primitives like databases and storage. This acquisition allows the entire Astro team to transition to Cloudflare as full-time employees, shifting their focus away from monetization and back to core development. Astro will remain platform-agnostic, open-source under the MIT license, and will continue to support multiple deployment targets beyond Cloudflare. This partnership aims to combine Cloudflare's global infrastructure with Astro's performance-focused framework to enhance the future of content-driven websites, especially as the industry prepares for the upcoming Astro 6 release.

The author shares their experience migrating a digital stack to European-based services to achieve digital sovereignty. By replacing US-centric tools with alternatives like Scaleway, Matomo, and Mistral, the author demonstrates that professional, reliable infrastructure is achievable in Europe. The post emphasizes prioritizing data control and alignment with personal values over mere convenience, despite occasional migration challenges.

GitHub is scaling its infrastructure and enhancing reliability to handle the rapid surge in agentic development workflows. To minimize service disruptions, the team is prioritizing system isolation, cloud migration, and performance optimization. Recent incidents involving merge queues and search failures have prompted deeper process improvements and a stronger commitment to transparent incident communication with the developer community.

bunny.net has eliminated usage fees for Bunny DNS to make high-performance global routing accessible to everyone. The platform offers free DNS hosting for up to 500 domains, integrated security through Bunny Shield, and automated 1-Click Acceleration. Enhanced with modern features like IPv6, DNSSEC, and advanced record support, it simplifies traffic management for developers.

Vercel has confirmed a security breach involving unauthorized access to internal systems. Threat actors claim to have stolen sensitive data, including API keys and source code. Vercel is investigating with experts, has notified authorities, and advises customers to rotate secrets and secure environment variables to mitigate potential risks.

A software company successfully migrated from DigitalOcean to Hetzner, reducing monthly costs from $1,432 to $233 while increasing performance. By leveraging MySQL master-slave replication and scripting administrative tasks, the migration involved 248 GB of data and 34 Nginx sites with zero downtime, highlighting the cost-efficiency of dedicated servers for stable workloads.

A former AWS advocate describes his transition from an early supporter to a critic due to excessive complexity, high egress costs, predatory behavior toward open-source, and poor support. His recent attempt to use AWS highlights ongoing frustrations with account management and vendor lock-in, reinforcing his decision to exit their ecosystem entirely.

Cloudflare Quick Tunnels provide a free, secure way to share local development environments through a single command. They require no account or configuration, automatically enable HTTPS and DDoS protection without exposing local ports, and route traffic through Cloudflare’s global edge network for fast, reliable access.

A developer's experiment with a free .online TLD resulted in a permanent lockout due to a 'serverHold' status. Triggered by a Google Safe Browsing flag, the domain entered a Catch-22: the registry required Google to lift the flag, but Google required DNS verification which was impossible since the domain would not resolve.

For two decades, the author has actively shaped the evolution of AWS, from early security concerns to enabling FreeBSD support. The journey includes pioneering work on EC2, advocating for security improvements like IAM, and sustained collaboration with Amazon engineers, highlighting a developer-led, symbiotic relationship that continues to influence AWS architecture today.

The author details the challenges and successes of building a tech startup exclusively using European infrastructure. While highlighting providers like Hetzner, Scaleway, and Bunny.net for cost-efficiency and data sovereignty, the post acknowledges difficulties in replacing US-centric services such as transactional email, GitHub, and major AI models, emphasizing that infrastructure independence requires significant active effort.

The article discusses the growing movement within the European Union to achieve digital sovereignty by moving away from US-based cloud providers such as AWS, Microsoft, and Google. Fueled by geopolitical instability and the US CLOUD Act, which allows American authorities access to data regardless of its physical location, European enterprises like Airbus are prioritizing EU-native cloud solutions. While American hyperscalers have introduced 'sovereign' regions, critics argue these are insufficient as they remain under US corporate ownership. Consequently, there is an increasing shift toward open-source stacks and local infrastructure to ensure long-term national economic security and data independence from American legal and political influence.

Routines allow users to automate tasks on Claude by triggering sessions via schedules, API endpoints, or GitHub repository events. These autonomous, cloud-based sessions use specified prompts, repositories, and connectors to perform repeatable work like backlog maintenance, code reviews, and alert triage, helping streamline development workflows through automation.

Usage-based services should enable hard monthly budget caps by default, automatically pausing applications or returning errors once limits are reached, rather than merely sending alerts. Runaway coding and personal agents can generate enormous API, compute, or storage bills. AWS has begun rolling out spend limits, while Google Cloud offers Spend Caps; broader availability and agent recommendations are encouraged.