Skip to content Skip to footer

What AWS’s New AI, Database and Edge Releases Change for Production Teams

What Happened

AWS announced a broad set of service updates on November 19, 2026. The changes most relevant to production AI applications concern agent memory, inference availability, runtime control and edge networking.

  • AI applications: Amazon OpenSearch Memory is generally available for persistent agent memory, with managed extraction and searchable retrieval across sessions. SageMaker AI added cross-Region routing for registered inference endpoints, preferring local capacity and shifting new requests when destinations become unhealthy. Lambda Managed Instances added GPU-backed Event Functions on EC2 G-series instances. [1][2][8]
  • Application platforms: Lambda customer-managed runtimes are generally available; platform teams can publish OCI-based runtimes in Amazon ECR while application teams deploy function code as .zip files. ExtendDB 1.0 is an open-source, DynamoDB API-compatible adapter with PostgreSQL, SQLite, Cassandra and MongoDB backends. [16][3]
  • Data and analytics: The AWS Glue Apache Spark Optimization Agent recommends job configuration, code and data-layout changes for Glue 4.0 and later. AWS Clean Rooms added intermediate tables for PySpark results. AWS Transform custom added cross-account sharing of transformation definitions through AWS RAM. [4][15][5]
  • Edge and delivery: CloudFront Functions added network calls through cf.fetch() and background analytics through cf.beacon(). CloudFront also added origin mutual TLS for WebSocket and gRPC traffic, plus CMCD and other fields in standard logs. [13][7][6]
  • Databases and recovery: RDS for MySQL added minor version 8.4.13 and major version 9.7, launching at 9.7.4. RDS added faster storage initialization after specified restore and topology operations. Cognito added point-in-time recovery for Essentials and Plus user pools. [9][11][14][10]
  • Infrastructure pricing: EKS Hybrid Nodes now caps billed usage at 32 vCPUs per node; existing nodes must be deleted and reattached to receive the new pricing. [12]

Why It Matters to Businesses

These releases address distinct operating problems. Cross-Region inference routing can reduce dependence on one Region’s endpoint health or capacity, but applications still need a policy for where requests and data may travel. Persistent agent memory can improve continuity without replaying entire conversations, but it also creates a retained data store that must be governed. [2][1]

Several changes may reduce operational work rather than eliminate it: centrally managed Lambda runtimes simplify updates across functions; Cognito recovery replaces custom user-pool restore workflows; and RDS storage initialization runs while an instance remains available. Teams should evaluate these against their existing deployment and recovery procedures. [16][10][14]

Kimbodo Engineering Perspective

Adopt by failure mode, not feature count. Use SageMaker routing where endpoint capacity or regional health threatens an availability target. Use OpenSearch Memory only where cross-session recall has a defined product benefit and retention policy. For small inference workloads, compare GPU-backed Lambda Managed Instances with continuously provisioned endpoints: the former adds a 9.75% management fee on EC2 On-Demand pricing and a per-request charge. [2][1][8]

Database releases warrant separate decisions. MySQL 8.4.13 is a minor-version maintenance path; MySQL 9.7 is a major upgrade that calls for application, driver, replication and query-plan testing. Its JSON Duality Views and opt-in Hypergraph Optimizer are reasons to benchmark, not reasons to skip compatibility checks. [9][11]

How We Would Implement It

  • Start with a compatibility inventory: map affected functions, endpoints, database instances, CloudFront distributions and AWS Regions. Confirm availability before committing to a design; OpenSearch Memory, for example, launched in five listed Regions. [1]
  • Build a controlled AI path: keep agent memory behind an application service that enforces user and tenant authorization, IAM access and expiration. Register healthy SageMaker endpoints with the router, set any required local-capacity caps, and test regional failover using response destination details and CloudWatch metrics. [1][2]
  • Roll out platform changes gradually: stage Lambda runtime aliases and test rollback; benchmark Glue recommendations against representative jobs; test CloudFront network-call latency and origin authentication before shifting production traffic. [16][4][13][7]
  • Prove recovery and upgrades: rehearse Cognito recovery previews, measure RDS restore readiness, and use a staged rollout or Blue/Green Deployment for applicable MySQL upgrades. [10][14][9][11]

Risks, Costs and Security

Memory retention and cross-Region routing require explicit access and data-location decisions. CloudFront network calls introduce an external dependency on the request path; cf.beacon() avoids delaying viewers for analytics, but those events still need appropriate data handling. Origin mTLS strengthens origin authentication, provided certificates and rotation are operated reliably. [1][2][13][7]

Check the pricing model before rollout: SageMaker routing has no additional charge, but endpoints and CloudWatch metrics remain billable; CloudFront Functions network calls cost $0.10 per million calls beyond invocation charges on pay-as-you-go pricing; and standard CloudFront logging charges apply to the new fields. Lambda customer-managed runtimes have no separate runtime charge, while ECR charges still apply. [2][13][6][16]

Where Kimbodo Comes In

Kimbodo builds and operates this in production for businesses — see our AI Application Development practice, or Estimate My AI Application.

Sources

  1. [1] Amazon OpenSearch Memory is now generally available
  2. [2] Amazon SageMaker AI now supports cross-Region inference routing
  3. [3] AWS announces ExtendDB 1.0
  4. [4] Introducing the Apache Spark Optimization Agent for AWS Glue ETL
  5. [5] AWS Transform custom now supports cross-account sharing of transformation definitions
  6. [6] Amazon CloudFront standard logging now supports CMCD and additional log fields
  7. [7] Amazon CloudFront Announces WebSocket and gRPC Support for Origin Mutual TLS
  8. [8] AWS Lambda adds support for GPU instances on Lambda Managed Instances
  9. [9] Amazon RDS for MySQL supports MySQL minor version 8.4.13
  10. [10] Amazon Cognito now supports point-in-time recovery
  11. [11] Amazon RDS for MySQL now supports MySQL major version 9.7
  12. [12] Amazon EKS Hybrid Nodes reduces price for large hosts
  13. [13] Amazon CloudFront Functions now supports network calls
  14. [14] Amazon RDS now supports fast storage volume initialization
  15. [15] AWS Clean Rooms supports writing PySpark job results to intermediate tables
  16. [16] AWS Lambda now supports customer-managed runtimes, giving platform teams centralized control over runtime contents and updates

Leave a comment

0.0/5

Engineering Founded & Customer Focused

KIMBODO LLC. © 2026. All Rights Reserved.