👋 Looking for changelogs for older versions? You can find them in the changelogs directory.
-
- Added "future" allocation type for future dated capacity reservation
-
- Adds ALPN H2 support for Netty client
-
- Reuse connections that receive a 5xx service response.
-
- AWS Elemental MediaLive adds a new feature, ID3 segment tagging, in CMAF Ingest output groups. It allows customers to insert ID3 tags into every output segment, controlled by a newly added channel schedule action Id3SegmentTagging.
-
- Docs Update for timeout changes
-
- Updated endpoint and partition metadata.
-
- Adds multi-turn input support for an Agent node in an Amazon Bedrock Flow
-
- Rename WorkSpaces Web to WorkSpaces Secure Browser
-
- Reuse connections that receive a 5xx service response.
-
- Reuse connections that receive a 5xx service response.
-
- Documentation-only update: clarified the description of the shareDecaySeconds parameter of the FairsharePolicy data type, clarified the description of the priority parameter of the JobQueueDetail data type.
-
- AWS IoT SiteWise now supports ingestion and querying of Null (all data types) and NaN (double type) values of bad or uncertain data quality. New partial error handling prevents data loss during ingestion. Enabled by default for new customers; existing customers can opt-in.
-
- Updated endpoint and partition metadata.
-
- Documentation-only update to address doc errors
-
- corrects the dual-stack endpoint configuration for cognitoidp
-
- Added DeleteContactFlowVersion API and the CAMPAIGN flow type
-
- Added
DigitGroupingStyle
in ThousandsSeparator to allow grouping byLAKH
( Indian Grouping system ) currency. Support LAKH andCRORE
currency types in Column Formatting.
- Added
-
- This release adds support for the topic attribute FifoThroughputScope for SNS FIFO topics. For details, see the documentation history in the Amazon Simple Notification Service Developer Guide.
-
- Increasing entryPoint in SparkSubmit to accept longer script paths. New limit is 4kb.
-
- Added a new EmfMetricLoggingPublisher class that transforms SdkMetricCollection to emf format string and logs it, which will be automatically collected by cloudwatch.
-
- Updated endpoint and partition metadata.
-
- Added support for Managed Notifications, integration with AWS Organization and added aggregation summaries for Aggregate Notifications
-
- Allow hyphens in tool name for Converse and ConverseStream APIs
-
- Doc only update for Detective documentation.
-
- Release u7i-6tb.112xlarge, u7i-8tb.112xlarge, u7inh-32tb.480xlarge, p5e.48xlarge, p5en.48xlarge, f2.12xlarge, f2.48xlarge, trn2.48xlarge instance types.
-
- Correction of docs for "Added support for ml.trn1.32xlarge instance type in Reserved Capacity Offering"
-
- Fixed contentLength mismatch issue thrown from putObject when multipartEnabled is true and a contentLength is provided in PutObjectRequest. See #5807
-
- Updated endpoint and partition metadata.
-
- The release addresses Amazon ECS documentation tickets.
-
- Added support for ml.trn1.32xlarge instance type in Reserved Capacity Offering
-
- Updated endpoint and partition metadata.
-
- Transform the getter methods on the service model classes that return SdkBytes to return ByteBuffer to be compatible with v1 style getters
-
- Now supports streaming for inline agents.
-
- Documentation updates for Amazon API Gateway
-
- corrects the dual-stack endpoint configuration
-
- This release introduces a new recommendation in Virtual Deliverability Manager Advisor, which detects elevated complaint rates for customer sending identities.
-
- S3 client behavior is updated to always calculate a checksum by default for operations that support it (such as PutObject or UploadPart), or require it (such as DeleteObjects). The checksum algorithm used by default is CRC32. The S3 client attempts to validate response checksums for all S3 API operations that support checksums. However, if the SDK has not implemented the specified checksum algorithm then this validation is skipped. See Dev Guide for more information
- This change enhances integrity protections for new SDK requests to S3. S3 SDKs now support the CRC64NVME checksum algorithm, full object checksums for multipart S3 objects, and new default integrity protections for S3 requests.
-
- Added GeneralPurpose.4xlarge & GeneralPurpose.8xlarge ComputeTypes.
-
- Mark type in MaintenanceWindow as required.
-
- Add Tagging support for ResourceSnapshotJob resources
-
- add static modifier to fromJson(InputStream) method of S3EventNotification
-
- Increase minimum length of Threat Actor IP 'userAgent' to 1.