Sunday, August 09, 2026

Amazon RDS now allows users to monitor the initialization progress of storage volumes created from snapshots during restores, read replica creation, or Multi-AZ conversions. This visibility helps identify when the underlying storage blocks have finished downloading from S3 and are ready to handle latency-sensitive workloads. During this initialization phase, I/O latency may remain elevated until the volume is fully provisioned and ready.

• Monitor initialization status to avoid performance issues when launching restored instances or replicas.
• High I/O latency during volume setup is expected until initialization completes.
• Use the new status to time workload cutover for latency-sensitive applications.
• Applies to point-in-time restores, read replicas, and Single-AZ to Multi-AZ conversions.

PostgreSQL has become the default database for agentic AI, but many teams treat it merely as storage rather than leveraging its compute capabilities. As AI agents generate complex signals, state, and checkpoints, the database must handle concurrent multi-step workflows and shared state updates. AI engineers often lack the expertise to optimize Postgres for these novel workload patterns that differ significantly from traditional operations.

• Shift mindset from Postgres as storage to a first-class compute layer for AI agents.
• Optimize for concurrent multi-step workflows and shared state updates in agentic systems.
• AI engineers need to explore PostgreSQL's capabilities beyond basic CRUD operations.
• Production agentic workloads require different optimization strategies than traditional apps.

pgAdmin 4 version 9.17 has been released with 28 bug fixes and seven critical security vulnerabilities addressed. The update introduces a configurable row limit for the View Data action to prevent performance issues on large tables. It also adds the authenticated user identity to HTTP access logs and offers an opt-in Gateway API HTTPRoute template in its Helm chart.

• Fixes seven security vulnerabilities (CVE-2026-17346 through 17351, 17566) immediately.
• New row count cap for View Data prevents browser hangs on large tables.
• Helm chart now supports Gateway API HTTPRoute as an Ingress alternative.
• HTTP access logs now include authenticated user identity for better auditing.
• Total of 28 bug fixes included in this minor release.

Amazon Quick now supports multi-dataset topics, allowing users to define relationships across multiple datasets within a single topic model. This capability eliminates the need for pre-joining data into a single dataset or writing manual JOIN logic during preparation. The system performs joins at runtime, enabling reusable relational models for both dashboard building and natural language Q&A without consuming extra SPICE capacity.

• Define relationships once in a topic rather than pre-joining data manually.
• Runtime joins replace static pre-joined datasets, reducing SPICE consumption.
• Single topic models now support both dashboard visuals and NLQ across datasets.
• No need to rebuild datasets when underlying data models or use cases change.

Pavel Stehule has introduced an initial integration of the Lua language into psql, allowing users to execute Lua scripts directly within the interactive session. The new \luacode command enables entering Lua code blocks that can define functions and perform operations, such as printing results, before being executed. This feature provides a lightweight scripting capability alongside SQL for ad-hoc data manipulation and tooling within the client environment.

• New \luacode command allows inline Lua scripting directly in psql sessions
• Supports defining Lua functions and printing output for quick client-side logic
• No server-side extension required; operates entirely within the psql client
• Initial integration phase; check docs for current limitations and syntax rules
• Useful for ad-hoc data transformation or automation without leaving the shell

Amazon Cognito is now a core skill in the Agent Toolkit for AWS, enabling AI coding agents to configure user pools, app clients, and OAuth flows. The aws-auth skill supports token management, JWT authorizers, and passkey enrollment, allowing agents to implement secure sign-in patterns autonomously. When used with the AWS MCP Server, agents execute CLI commands with IAM guardrails and CloudTrail logging for auditability.

• AI agents can now autonomously set up and troubleshoot Cognito auth flows via the aws-auth skill.
• Covers user pools, app clients, OAuth 2.0, JWT authorizers, and WebAuthn enrollment.
• Agents can leverage IAM guardrails and CloudTrail audit logging when paired with AWS MCP Server.
• Works standalone via AWS CLI for direct command-line execution without full agent integration.
• Accelerates implementation of secure sign-in for users, AI agents, and microservices.

Google has open-sourced a repository of Agent Skills designed to streamline interactions with Google Cloud and related technologies. The project provides pre-built configurations for tasks such as authentication, solution architecture, and agentic analytics. Users can install specific skills via npx, allowing for modular adoption of these tools into their existing AI agent workflows.

• Enables modular installation of GCP-specific agent capabilities via npx.
• Covers key workflows like onboarding, authentication, and solution architecture.
• Supports agentic analytics across multi-cloud and data lakehouse environments.
• Repository is under active development, so features may evolve rapidly.

Amazon Bedrock AgentCore now generally offers runtime instances that deploy agents directly onto customer-owned EC2 infrastructure. This new capability complements the existing microVM option by providing access to diverse instance types, including GPU, memory-optimized, and compute-optimized families. AWS manages the provisioning, patching, scaling, and lifecycle of these resources while teams define needs via capacity providers.

• Use EC2 runtime instances for sustained, resource-intensive, or specialized-hardware AI agent workloads.
• Access broad EC2 families including GPU, memory, and compute-optimized types directly within AgentCore.
• AWS handles infrastructure lifecycle management: provisioning, patching, scaling, and lifecycle ops.
• Configure capacity providers via Console, CLI, SDKs, or APIs to specify required instance types.

Amazon Bedrock AgentCore introduces temporal policies to enforce stateful authorization rules that evaluate requests based on prior agent actions within a session. This allows for workflow sequencing, argument validation against previous outputs, human approval gates, and data freshness checks. Additionally, new rate limiting capabilities enable per-user or per-group traffic controls for tools, models, and agents scoped via OAuth or IAM.

• Enforce workflow sequencing by evaluating requests against prior session actions.
• Require human approval before executing privileged agent actions.
• Validate tool arguments against outputs from previous calls in the session.
• Apply rate limits per user or group using OAuth or IAM scopes.
• Prevent stateless tool calls that are safe in isolation but risky in context.

Amazon Bedrock AgentCore has expanded to AWS GovCloud (US-West) with new capabilities for building regulated AI agents. The update introduces memory features for both short-term conversation context and long-term persistent insights. It also includes centralized policy controls for agent-tool interactions that operate independently of agent code.

• AgentCore is now available in AWS GovCloud (US-West) for regulated environments.
• Short-term memory handles immediate conversation context without manual infrastructure management.
• Long-term memory extracts persistent insights and user preferences across sessions.
• Centralized policies enforce fine-grained controls on agent-tool interactions outside code.
• These features aim to accelerate the transition from prototype to production for enterprise agents.

AWS Transform now handles post-launch actions automatically as part of the migration workflow, eliminating manual server-by-server setup. These actions execute through AWS Systems Manager immediately after test or cutover launches and can be defined at the account level for multi-account targets. Users can leverage predefined actions or supply custom SSM documents, with updated migration inventory files simplifying per-server configuration reviews.

• Post-launch actions run via SSM right after test or cutover launches.
• Define actions at account level to apply across all target servers automatically.
• Supports both predefined actions and custom SSM documents.
• Migration inventory files now include structured post-launch action fields.
• Reduces manual effort and errors in bulk server configuration.

AWS IAM Identity Center now allows users to enable multi-Region support with a single click when creating a new organization instance. This feature automatically provisions a customer-managed multi-Region KMS key and replicates the instance to an additional Region. The update replaces the previous manual workflow that required creating keys, configuring policies, and adding Regions individually. Users can now choose between single-Region, multi-Region, or custom configurations during instance creation.

• New org instances can now be deployed as multi-Region with one click, reducing setup complexity.
• The service automatically creates a customer-managed multi-Region KMS key for encryption.
• Instance replication to a secondary Region is handled automatically to improve access resilience.
• Manual steps for KMS key creation and policy configuration are no longer required for this option.
• Three configuration options are available: single-Region, multi-Region, or custom.

Amazon ElastiCache now supports Graviton4-based M8g, R8g, and C8gn node families for both Valkey and Memcached engines. These new nodes deliver up to 47% higher throughput and 43% lower P99 latency compared to Graviton3 equivalents, with up to 31% better price-performance on on-demand pricing. The M8g family also provides up to 20% more memory per node size, while C8gn nodes offer 200 Gbps network bandwidth for network-intensive workloads.

• Graviton4 nodes boost throughput by 47% and cut P99 latency by 43% vs Graviton3.
• M8g nodes provide up to 20% more memory at the same instance size.
• C8gn nodes deliver 200 Gbps bandwidth for high-network throughput workloads.
• Supported engines include both Valkey and Memcached on ElastiCache.

Amazon DynamoDB has generally available vector search, enabling real-time indexing and querying of vector embeddings at scale. The service promises single-digit millisecond latency with 99%+ recall, addressing the traditional trade-offs between speed, scale, and accuracy for datasets reaching trillions of vectors. Developers can store embeddings alongside standard attributes and use approximate nearest neighbor searches with indexes of their choice.

• Native vector index supports approximate nearest neighbor searches in DynamoDB.
• Latency targets single-digit milliseconds with 99%+ recall at any scale.
• Embeddings can be generated via custom models or Amazon Bedrock.
• Vectors are stored alongside standard DynamoDB attributes in the same table.

Amazon ECS now allows task definitions to request fractional GPU resources, supporting partitions as small as one-eighth of an NVIDIA L4 Tensor Core GPU. This feature targets G6f instances and enables right-sizing for workloads like small-model inference or experimentation that do not require full GPU capacity. Users specify these allocations directly in container definitions using values such as 0.125, 0.25, or 0.5 to optimize cost and resource utilization.

• Right-size containers for AI inference or graphics without paying for full GPUs.
• Request 1/8, 1/4, or 1/2 GPU allocations in ECS task definitions.
• Reduces infrastructure costs for small-model experimentation workloads.
• Requires Amazon EC2 G6f instances with NVIDIA L4 Tensor Core GPUs.

AWS Lambda now offers scalable egress and ingress bandwidth for functions running outside a VPC, scaling linearly with memory from 625 Mbps at 2 GB to 3,000 Mbps at 10 GB. This eliminates the previous hard cap that constrained latency-sensitive workloads transferring large datasets. The update allows higher memory allocations to directly yield proportional network throughput improvements.

• Non-VPC Lambda functions now scale network bandwidth proportionally with memory allocation.
• Egress/ingress speeds range from 625 Mbps (2 GB) to 3 Gbps (10 GB).
• Removes previous 625 Mbps bottleneck for data-intensive, latency-sensitive workloads.
• No VPC configuration required to access increased throughput capabilities.

AWS has updated IAM Identity Center to allow optional management of AWS account access during the initial configuration of new organization instances. This enables organizations to use the service solely for workforce identity federation and application single sign-on, decoupling it from native AWS account permission management. The change applies only to newly created instances and does not alter existing deployments.

• New org instances can now skip AWS account access management, focusing only on application SSO.
• Decouple workforce identity federation from native AWS account permissioning for new setups.
• Existing IAM Identity Center instances remain unaffected by this configuration option.
• Streamlines access management for app owners and end users via consistent SSO experiences.

Amazon EC2 G7 instances powered by NVIDIA RTX PRO 4500 Blackwell Server Edition GPUs are now available in the Europe (Spain) Region. These instances offer up to 4.6x AI inference performance and 2.1x graphics performance compared to the previous G6 generation. The new hardware accelerates workloads including AI inference, real-time graphics rendering, and GPU-accelerated data analytics.

• G7 instances in EU (Spain) use NVIDIA RTX PRO 4500 Blackwell Server Edition GPUs.
• AI inference performance improves up to 4.6x over G6 instances.
• Graphics performance increases up to 2.1x compared to G6.
• Suitable for LLM inference, video transcoding, and spatial computing.
• Enables local deployment of AI models without data residency constraints.

celld is an open-source daemon that enables self-hosted execution of Cloudflare Workers and Durable Objects. It treats each durable object as an independent SQLite database, coordinating state across nodes via a shared S3-compatible bucket without requiring a control plane or consensus protocol. This architecture naturally shards data, eliminating the contention and blast-radius risks associated with shared database instances.

• Each Durable Object is an isolated SQLite DB, removing shared contention and blast-radius risks.
• Nodes coordinate solely through an S3-compatible bucket, avoiding complex consensus or control planes.
• Embeds V8 to execute Wrangler bundles, allowing Cloudflare Workers logic to run on your own infrastructure.
• Idle cells hibernate to near-zero resource usage, optimizing cost for sporadic workloads.