OffNet Newsroom

Daily topic roundup

AWS

Tuesday, July 14, 2026 · 6 stories, curated & summarized — click any story for the source.

Davide de Paolis outlines a strategy for implementing 'minimum viable governance' on AWS without alienating internal users. The approach emphasizes shifting from rigid enforcement to high-empathy, data-driven collaboration. Key tactics include using event-driven Slack alerting to automate policy feedback loops.

  • Adopt 'minimum viable governance' to reduce friction during cloud infrastructure rollout.
  • Use event-driven Slack alerts to provide immediate, automated policy feedback to developers.
  • Prioritize high-empathy collaboration over rigid enforcement to maintain team relations.
  • Leverage data-driven insights to guide compliance decisions rather than arbitrary rules.

Regional outages exposed a pre-flight discovery call embedded in every client session, creating a latency bottleneck for global failover. The engineering team refactored the architecture to eliminate this mandatory round trip. The article details the implementation steps and the operational cost required to roll out this change.

  • Legacy discovery calls can silently block effective multi-region failover strategies.
  • Refactoring client sessions requires careful rollout planning to manage operational costs.
  • Proactive latency audits are essential for maintaining global API performance.
AWS What's New awsdatabase ↺ since 07-10

Timestream for InfluxDB emits EventBridge state change events

Amazon Timestream for InfluxDB now publishes database lifecycle events to Amazon EventBridge, covering creation, deletion, scaling, maintenance, and reboot operations. These events capture both successful completions and failures, eliminating the need for API polling. Teams can route these signals to trigger automation workflows, alerting systems, or audit logging pipelines.

  • Eliminates polling by pushing state changes directly to EventBridge
  • Covers full lifecycle including scaling, maintenance, and failures
  • Enables automated workflows triggered by specific database events
  • Supports compliance via persistent logging to CloudWatch or S3
HOW IT WORKSInfluxDB Event Pipeline1Database lifecycle change occurs2Timestream emits state event3EventBridge routes signal4Trigger automation or logging

AWS has launched Amazon Managed Service for Prometheus in the Asia Pacific (New Zealand) region. This fully managed, Prometheus-compatible service enables scalable monitoring and alerting for operational metrics. Each workspace supports up to 1 billion active metric series, allowing teams to store and query data efficiently across multiple workspaces per account.

  • Prometheus monitoring is now available in the New Zealand region for lower latency.
  • Workspaces support up to 1 billion active metric series for high-scale observability.
  • Fully managed service eliminates operational overhead of self-hosted Prometheus stacks.
  • Multiple workspaces can be created per account to logically separate metric data.
BY THE NUMBERSMax Metrics Per Workspace1 billionActive metric series capacityEach workspace can store and query this volume
AWS What's New awsdatabase ↺ since 07-10

AWS MCP Server adds OAuth for direct AI agent authentication

The AWS MCP Server now supports OAuth via AWS Sign-In, allowing AI agents to connect using industry-standard protocols without extra middleware. This update leverages existing IAM permissions and governance controls while enabling both interactive and headless authorization flows. Administrators gain enhanced oversight through new CloudTrail audit events, token introspection, and dynamic client registration capabilities.

  • AI agents authenticate via OAuth using existing AWS identities and IAM policies.
  • Supports both interactive browser-based and programmatic headless authorization flows.
  • New governance features include token introspection, revocation APIs, and dynamic client registration.
  • Access is fully auditable through new CloudTrail events and global condition keys.
HOW IT WORKSAWS MCP OAuth Flow1Agent initiates authentication2User signs in via AWS3IAM validates permissions4Token issued securely5Access granted to resources
AWS What's New awsdatabase ↺ since 07-10

Amazon MSK Replicator now supports external Kafka to MSK Standard brokers

AWS has expanded Amazon MSK Replicator to allow data replication from external Apache Kafka clusters—including on-premises, self-managed, or third-party cloud environments—to MSK Standard brokers. This update extends prior support that was limited to MSK Express brokers, enabling broader adoption of the managed replication service. The feature automates data movement, removing the need for custom infrastructure or open-source tooling.

  • External Kafka clusters can now replicate directly to MSK Standard brokers.
  • Supports hybrid and multi-cloud disaster recovery and backup scenarios.
  • Eliminates the need for custom replication code or open-source tools.
  • Simplifies workload migration from on-prem or other cloud Kafka providers.
CHECKLISTKey Benefits of MSK ReplicatorReplicate from external Kafka to MSK StandardEnable hybrid and multi-cloud disaster recoveryEliminate custom replication code needsSimplify workload migrations from on-prem