2.53.0 2026-08-13

AWS CRT HTTP Client

• Bugfixes

  • Honor wildcard nonProxyHosts entries in CRT-based HTTP clients (AwsCrtHttpClient, AwsCrtAsyncHttpClient, and the S3/CRT client). Previously a *.suffix wildcard or a bare * from http.nonProxyHosts/no_proxy was silently ignored, so matching hosts were routed through the proxy instead of bypassing it. Supported forms are an exact host, a *.suffix wildcard (matches the domain and its subdomains), a single * for all hosts, and CIDR ranges. Entries must not contain surrounding whitespace.

AWS Certificate Manager

• Features

  • This change allows customers to update their existing email-validated certificates to use the DNS validation method.

AWS Clean Rooms Service

• Features

  • This release adds support for minimum aggregation thresholds and comparison controls to the Custom analysis rule type.

AWS CodeCommit

• Features

  • Added the GetBlobDifferences API operation, which returns line-level diffs between two blob versions without requiring a local clone. Returns structured hunks with context, additions, and deletions. Supports pagination for large diffs.

AWS SDK for Java v2

• Features

  • Removed ServiceMetadata usages from client creation and request processing code paths to improve cold start performance. Endpoint and signing region resolution now uses Endpoints 2.0 directly instead of triggering eager initialization of all service metadata classes. Service client artifacts must be version 2.28.1 or later to be compatible with this change.

AWS Security Agent

• Features

  • Add support for setting a maximum task-hour budget cap on penetration tests and code reviews, and for revalidating previously reported findings via a new REVALIDATION job type.

Amazon CloudFront

• Features

  • Adds SHA256 support to CloudFrontUtilities

Amazon Connect Service

• Features

  • Adds the StartAssistantContact API to start chat contacts handled by an AI agent. Adds SegmentAttributes to StartWebRTCContact, and corrects its error response to now receive AccessDeniedException (previously returned as an internal server error due to a missing error declaration).

Amazon DynamoDB Enhanced Client

• Bugfixes

  • Fix AutoGeneratedTimestampRecordExtension failing when TableSchema.converterForAttribute throws UnsupportedOperationException for custom schemas; expand dynamodb-enhanced functional test coverage

Apache 5 HTTP Client

• Bugfixes

  • Trimmed surrounding whitespace from nonProxyHosts / no_proxy entries so comma- or pipe-separated values with spaces (e.g. no_proxy=a.com, *.foo.com) are honored. Previously an entry with a leading or trailing space was treated as part of the host name and never matched, so the host was routed through the proxy instead of bypassing it.

Apache HTTP Client

• Bugfixes

  • Trimmed surrounding whitespace from nonProxyHosts / no_proxy entries so comma- or pipe-separated values with spaces (e.g. no_proxy=a.com, *.foo.com) are honored. Previously an entry with a leading or trailing space was treated as part of the host name and never matched, so the host was routed through the proxy instead of bypassing it.

Apache HTTP Client 5

• Features

  • Upgrade httpcomponents.client5 to 5.6.4 to address CVE-2026-71290

Auto Scaling

• Features

  • Amazon EC2 Auto Scaling now supports terminating multiple instances in a single TerminateInstanceInAutoScalingGroup call via the new InstanceIds parameter, returning an Activities list. LaunchInstances now returns IdempotentCallInProgressFault for duplicate client tokens.

Netty NIO HTTP Client

• Bugfixes

  • Trimmed surrounding whitespace from nonProxyHosts / no_proxy entries so comma- or pipe-separated values with spaces (e.g. no_proxy=a.com, *.foo.com) are honored. Previously an entry with a leading or trailing space was treated as part of the host name and never matched, so the host was routed through the proxy instead of bypassing it.

URL Connection HTTP Client

• Bugfixes

  • Trimmed surrounding whitespace from nonProxyHosts / no_proxy entries so comma- or pipe-separated values with spaces (e.g. no_proxy=a.com, *.foo.com) are honored. Previously an entry with a leading or trailing space was treated as part of the host name and never matched, so the host was routed through the proxy instead of bypassing it.