Amazon CloudFront adds IP based routing and connection logs to SaaS Manager

Amazon CloudFront now allows web development and SaaS platforms to serve different tiers of customers on the same wildcard domain by using IP addresses to route them to the right configuration. For example, these platforms can serve premium and pro customers from dedicated Anycast static IP address lists, each with its own configuration, and serve free-tier customers on the shared CloudFront IP addresses, all under *.example.com. Additionally, these customers also have visibility into viewer connections with connection logging.
Previously, CloudFront chose the configuration from the domain name alone, so the same domain always went to the same configuration. With address-based selection, you can register the same wildcard domain on several IP lists and send each list to its own tenant. Because you control which clients resolve to which IP list, you can shift traffic between your service tiers without your customers needing to make any changes. You can also serve IoT devices, embedded SDKs, and older TLS clients that connect by IP address without sending a domain name in the TLS handshake (Server Name Indication, or SNI). With viewer fallback, you choose a distribution to accept these connections, and CloudFront uses the Host header in each request to serve the right content. Connection logs now also record HTTPS connections to these tenants which helps you troubleshoot how clients connect.
These features are available at all CloudFront edge locations. To learn more, see Address-based selection and Connection Logs in the Amazon CloudFront Developer Guide.
Quelle: aws.amazon.com

Amazon Aurora DSQL now delivers up to 50% higher write throughput

With upgrades to its storage layer, Amazon Aurora DSQL now delivers up to 50% higher write throughput for many transactional workloads. Data loads finish sooner, and tables whose primary key always increases, such as tables keyed by a timestamp, an identity column, or a time-ordered ID like ULID or UUIDv7, see even greater benefits.
Applications such as audit logs, ledgers, and event feeds are read in time order, and keying them by time keeps those reads fast. You can now use that design for write-heavy tables too. In our tests, an audit log table keyed by event time accepted up to 200% more inserts per second.
The improvement is available in all AWS Regions where Aurora DSQL is available, for new and existing clusters, at no additional cost. To learn more, see the Aurora DSQL User Guide.
Quelle: aws.amazon.com

Amazon Cognito now supports client ID metadata documents

Amazon Cognito now supports OAuth client ID metadata documents (CIMD). Amazon Cognito helps you implement secure sign-in and access control for users, AI agents, and microservices in minutes. With CIMD, Model Context Protocol (MCP) clients and AI agents can sign users in to your user pool without registering a separate app client. Previously, each external client needed its own app client, either created in advance or through dynamic client registration, and you had to manage and clean up those clients over time.
With CIMD, a client uses an HTTPS URL as its client ID and publishes a JSON metadata document at that URL. When the client starts sign-in, Cognito fetches and validates the document and uses it to identify the client and validate its sign-in request. You decide which clients to accept with CIMD policies that map URL patterns to one of your app clients, and Cognito grants only the scopes and grant types that both the app client and the metadata document allow. For example, a company that runs an MCP server can accept an AI assistant by allowing the URL where that assistant publishes its metadata without creating or maintaining an app client for it.
CIMD is available on the Essentials and Plus feature plans in all AWS Regions where Amazon Cognito is available. To learn more, see Client ID metadata documents (CIMD) in the Amazon Cognito Developer Guide.
Quelle: aws.amazon.com

AWS Marketplace now supports agentic payments with AgentCore

AWS Marketplace now supports agentic payments over the x402 protocol, so AI agents can discover and buy select products and pay per request in US dollars through AgentCore payments, part of Amazon Bedrock AgentCore. Agents often need paid APIs, data, or content mid-task, but access usually requires a person to sign up, add a payment method, and create an API key. With agentic payments, customers skip that per-seller setup, and charges settle on their existing AWS bill with no crypto wallet required.
Customers enable the AWS Marketplace payment connector in AgentCore payments, then they or their agents find listings through the AWS Marketplace connector in AgentCore Gateway. For example, a research agent can buy a single web search, or a coding agent can call a paid guardrail service. Customers can set spending limits, approved sellers, and guardrails before agents transact, Private Marketplace policies still apply, and transactions appear in AWS CloudTrail and AWS Cost Explorer.
AWS Marketplace sellers can charge AI agents per request without building a sign-up flow or billing system. They register with AWS Marketplace, configure agentic payments for their listings, and integrate the AWS Marketplace x402 SDK. AWS Marketplace collects customer payments and pays sellers through their AWS Marketplace seller disbursements, like other AWS Marketplace transactions.
The capability is available in all AWS Regions where AgentCore payments is available. To learn more, see AWS Marketplace and the Amazon Bedrock AgentCore Developer Guide. To list as a seller, see the AWS Marketplace Seller Guide.
Quelle: aws.amazon.com

Announcing the general availability of a new AWS Local Zone in Bogotá, Colombia

Today, AWS announces the general availability of a new Local Zone in Bogotá, Colombia, bringing AWS infrastructure closer to end users for applications that require single-digit millisecond latency. You can use the Bogotá Local Zone for workloads such as real-time gaming, live video streaming, medical imaging, and financial transaction processing.
AWS Local Zones are infrastructure deployments that place compute, storage, networking, and other select AWS services closer to metropolitan areas, with the same APIs and tools as AWS Regions. You pay only for what you use, with no minimum commitment. Pricing options include On-Demand, Savings Plans, and Spot Instances. AWS Local Zones are available in more than 30 locations worldwide.
The AWS Local Zone in Bogotá supports Amazon Elastic Compute Cloud (Amazon EC2) with C7i, M7i, and R7i instances, Amazon S3 with the One Zone-Infrequent Access storage class, Amazon EBS with local snapshots and volume types gp3, gp2, and io1, Amazon Elastic Container Service (Amazon ECS), Amazon Elastic Kubernetes Service (Amazon EKS), Amazon Virtual Private Cloud (Amazon VPC), AWS Direct Connect, and Application Load Balancer.  
To get started, enable the AWS Local Zone in Bogotá (us-east-1-bog-1a) from the Regions and Zones tab in the AWS Global View or by using the ModifyAvailabilityZoneGroup API. For pricing information, visit the AWS Local Zones pricing page. To learn more, visit the AWS Local Zones overview page.
Quelle: aws.amazon.com