Skip to content

v1.4.0
Compare
Choose a tag to compare
@aws-sdk-kotlin-ci aws-sdk-kotlin-ci released this 15 Jan 22:41
· 92 commits to main since this release
v1.4.0
5512867

[1.4.0] - 01/15/2025

Features

  • (bedrockagentruntime) Now supports streaming for inline agents.
  • (cognitoidentity) corrects the dual-stack endpoint configuration
  • (partnercentralselling) Add Tagging support for ResourceSnapshotJob resources
  • (s3) 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.
  • (securityir) Increase minimum length of Threat Actor IP 'userAgent' to 1.
  • (sesv2) This release introduces a new recommendation in Virtual Deliverability Manager Advisor, which detects elevated complaint rates for customer sending identities.
  • (workspaces) Added GeneralPurpose.4xlarge & GeneralPurpose.8xlarge ComputeTypes.
  • (workspacesthinclient) Mark type in MaintenanceWindow as required.
  • ⚠️ IMPORTANT: 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 varies by SDK (CRC32 or CRC64, CRC32 for the Kotlin SDK). Checksum calculation behavior can be configured using when_supported and when_required options - in code using requestChecksumCalculation, in shared config using request_checksum_calculation, or as env variable using AWS_REQUEST_CHECKSUM_CALCULATION. 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. Checksum validation behavior can be configured using when_supported and when_required options - in code using responseChecksumValidation, in shared config using response_checksum_validation, or as env variable using AWS_RESPONSE_CHECKSUM_VALIDATION.

Fixes

  • #1321 Include more information when retry strategy halts early due to token bucket capacity errors

Documentation

  • (apigateway) Documentation updates for Amazon API Gateway

Miscellaneous

  • The order of credentials resolution in the credentials provider chain has been updated to: system properties, environment variables, web identity tokens, profile, ECS, EC2
  • ⚠️ IMPORTANT: Upgrade to Kotlin 2.1.0
  • The order of credentials resolution in config files has been updated to: static credentials, assume role with source profile OR assume role with named provider, web identity token, SSO session, legacy SSO, process
Assets 2
Loading