AWS Transform custom now supports cross-account sharing of transformation definitions

AWS Transform custom now enables you to share transformation definitions (TDs) and their associated lessons across AWS accounts, organizational units (OUs), or your entire organization in AWS Organizations through AWS Resource Access Manager (AWS RAM). AWS Transform custom is a capability of AWS Transform that performs transformations across your technology stack, including API and framework upgrades, migrations, and language translations.
With this launch, you can share TDs as live resources rather than static copies, so consumers run the owner’s latest published version by default while the owner maintains full control. As the TD owner, you select from four managed permissions ranging from execute-only (the default) to permissions that allow consumers to use your lessons, contribute lessons back to you, or download the TD. Lessons flow back to the owner only when the permission allows it and the consumer opts in.
This capability is particularly valuable for platform engineering teams and AWS Partners who need to deploy standardized transformations across multiple accounts. A central team can create a TD once and share it organization-wide.
This feature is available via the AWS Transform CLI and AWS RAM in US East (N. Virginia), Europe (Frankfurt), Europe (London), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Sydney), Asia Pacific (Tokyo), and Canada (Central) Regions. To learn more, visit the AWS Transform User Guide.
Quelle: aws.amazon.com

Amazon SageMaker AI now supports cross-Region inference routing

Today, Amazon SageMaker AI announces cross-Region inference routing, which helps keep inference applications available when a region runs short of capacity by sending requests to endpoints deployed in other AWS Regions and AWS accounts. Models served on accelerated instances can reach capacity limits in a single Region, and an unhealthy endpoint can lead to throttling and errors for end users. Previously, teams had to build and maintain their own routing, health checks, and retry logic across Regions. With cross-Region inference routing in SageMaker AI, developers create an inference router, register the real-time endpoints, asynchronous endpoints, and inference components they already run, and point their applications at the router. The router prefers endpoints in its own Region, shifts new requests to healthy destinations in other Regions as errors rise, and returns traffic gradually after the local endpoint recovers. Existing endpoints, models, and containers do not change. Endpoint owners stay in control: an endpoint policy determines which routers in other accounts can use an endpoint, and an optional cross-Region traffic cap reserves capacity for the endpoint’s local callers. Each real-time response identifies the endpoint that served the request and the reason, and router metrics in Amazon CloudWatch show where traffic went. Cross-Region inference routing is available for real-time inference in 32 commercial AWS Regions, and for asynchronous inference in 25 Regions. There is no additional charge for cross-Region inference routing. Customers pay standard SageMaker AI pricing for the endpoints that serve requests and standard Amazon CloudWatch rates for router metrics. To learn more, see the Amazon SageMaker AI Developer Guide and SageMaker AI Deployment page.
Quelle: aws.amazon.com

AWS announces ExtendDB 1.0

Today, Amazon Web Services (AWS) announced version 1.0 of ExtendDB, the first release of the open source Amazon DynamoDB-compatible adapter for production use. ExtendDB is fully compatible with the DynamoDB API and runs on a database backend that you choose, so developers and infrastructure teams can run DynamoDB workloads in on-premises data centers, in private or public clouds, and at the edge without rewriting application code.
ExtendDB 1.0 supports four storage backends, PostgreSQL, SQLite, Cassandra, and MongoDB. For local development and continuous integration (CI), the extenddb-dev container image and the @extenddb/dev npm package run a DynamoDB-compatible endpoint over SQLite, so you don’t have to set up an external database.
ExtendDB is maintained by AWS, released under the Apache 2.0 license, and developed in the open on GitHub. To learn more, see the ExtendDB project page. To get started or contribute, visit the GitHub repository.
Quelle: aws.amazon.com

Introducing the Apache Spark Optimization Agent for AWS Glue ETL

AWS Glue ETL now offers the Apache Spark Optimization Agent, which analyzes completed Spark job runs and delivers cost and performance optimization recommendations within minutes. You can select a cost or performance goal, and the agent returns specific configuration changes with the telemetry evidence and reasoning behind each suggestion. You can use the agent on any completed job run from the AWS Glue console, or from your own tools through the Amazon SageMaker Unified Studio MCP Server.
The agent takes the job’s configuration, logs, and Spark telemetry together with your chosen goal and returns recommendations computed by a deterministic recommendation engine. The engine reads all job artifacts together to identify what is driving runtime and cost: too little parallelism, a skewed join key, memory pressure forcing spill, idle executors, or capacity provisioned beyond what the job uses. When cost and performance trade off, the agent improves the metric you chose while keeping any regression of the other within defined limits. The engine also checks best practices such as platform-level improvements like upgrading to a newer AWS Glue version or using AWS Graviton processors. Each recommendation is labeled by the area it modifies: infrastructure, Spark configuration, code, or data layout. All access is authenticated with AWS Identity and Access Management (IAM) and logged in AWS CloudTrail.
The Apache Spark Optimization Agent is available at no additional charge for AWS Glue versions 4.0 and later in all Regions where AWS Glue is available, except the AWS GovCloud (US) and China Regions. To get started, see Apache Spark Optimization Agent for Amazon EMR and AWS Glue and the blog post – Introducing the Apache Spark optimization agent for Amazon EMR Serverless and AWS Glue ETL.
Quelle: aws.amazon.com

Amazon OpenSearch Memory is now generally available

Today, AWS announced the general availability of Amazon OpenSearch Memory, a new serverless capability in Amazon OpenSearch Service for adding persistent memory to AI agents. OpenSearch Memory stores agent interactions as searchable events, derives useful memories, and retrieves relevant context across sessions, so agents can recall prior decisions, earlier interactions, and user preferences without replaying the full conversation history to the model. Customers can give agents long-term memory without provisioning infrastructure or building separate extraction, indexing, consolidation, and retrieval systems.
OpenSearch Memory stores the original events verbatim, makes them searchable within seconds, and asynchronously derives structured memories. It manages the full memory lifecycle, including extraction, embedding, indexing, consolidation (adding, updating, or skipping memories as new information arrives), and retrieval using keyword, semantic, and hybrid search. Customers control access with AWS Identity and Access Management (IAM) for each memory store, with actor and session scoping, and can set expiration periods for events and memories. Because it is serverless, there are no clusters to provision, instance types to choose, or indexes to create, and capacity for extraction and search scales automatically.
Amazon OpenSearch Memory is available today in US East (N. Virginia, Ohio), US West (Oregon), Europe (Frankfurt), and Asia Pacific (Tokyo) Regions. For pricing details about Amazon OpenSearch Memory, visit the pricing page.
To learn more about Amazon OpenSearch Memory, see the technical documentation and launch blog. You can get started by visiting the technical launch blog that details how to add persistent memory to your agents with Amazon OpenSearch Memory. 
Quelle: aws.amazon.com