Bump aws.sdk.kotlin:s3-jvm from 1.3.66 to 1.4.1

[dependabot]

Bumps aws.sdk.kotlin:s3-jvm from 1.3.66 to 1.4.1.

Release notes

Sourced from aws.sdk.kotlin:s3-jvm's releases.

v1.4.1

[1.4.1] - 01/16/2025

Features

• (sagemaker) Added support for ml.trn1.32xlarge instance type in Reserved Capacity Offering

Documentation

• (ecs) The release addresses Amazon ECS documentation tickets.

v1.4.0

[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

v1.3.112

[1.3.112] - 01/14/2025

Features

• (gamelift) Amazon GameLift releases a new game session placement feature: PriorityConfigurationOverride. You can now override how a game session queue prioritizes placement locations for a single StartGameSessionPlacement request.
• (route53) Amazon Route 53 now supports the Mexico (Central) Region (mx-central-1) for latency records, geoproximity records, and private DNS for Amazon VPCs in that region

v1.3.111

[1.3.111] - 01/13/2025

Features

• (artifact) Support resolving regional API calls to partition's leader region endpoint.
• (bedrock) With this release, Bedrock Evaluation will now support latency-optimized inference for foundation models.
• (ec2) Add support for DisconnectOnSessionTimeout flag in CreateClientVpnEndpoint and ModifyClientVpnEndpoint requests and DescribeClientVpnEndpoints responses
• (kafkaconnect) Support updating connector configuration via UpdateConnector API. Release Operations API to monitor the status of the connector operation.
• (transcribe) This update provides tagging support for Transcribe's Call Analytics Jobs and Call Analytics Categories.

... (truncated)

Changelog

Sourced from aws.sdk.kotlin:s3-jvm's changelog.

[1.4.1] - 01/16/2025

Features

• (sagemaker) Added support for ml.trn1.32xlarge instance type in Reserved Capacity Offering

Documentation

• (ecs) The release addresses Amazon ECS documentation tickets.

[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

[1.3.112] - 01/14/2025

Features

• (gamelift) Amazon GameLift releases a new game session placement feature: PriorityConfigurationOverride. You can now override how a game session queue prioritizes placement locations for a single StartGameSessionPlacement request.
• (route53) Amazon Route 53 now supports the Mexico (Central) Region (mx-central-1) for latency records, geoproximity records, and private DNS for Amazon VPCs in that region

[1.3.111] - 01/13/2025

Features

• (artifact) Support resolving regional API calls to partition's leader region endpoint.
• (bedrock) With this release, Bedrock Evaluation will now support latency-optimized inference for foundation models.
• (ec2) Add support for DisconnectOnSessionTimeout flag in CreateClientVpnEndpoint and ModifyClientVpnEndpoint requests and DescribeClientVpnEndpoints responses
• (kafkaconnect) Support updating connector configuration via UpdateConnector API. Release Operations API to monitor the status of the connector operation.
• (transcribe) This update provides tagging support for Transcribe's Call Analytics Jobs and Call Analytics Categories.

[1.3.110] - 01/10/2025

Documentation

... (truncated)

Commits

• 55a02f8 chore: release 1.4.1
• 6d624a6 Update partitions file
• c2551d9 feat: update AWS service endpoints metadata
• 8bcddaf feat: update AWS API models
• 7e033d9 chore: bump snapshot version to 1.4.1-SNAPSHOT
• 5512867 chore: release 1.4.0
• 8d3c95c feat: update AWS service endpoints metadata
• a8126cb feat: update AWS API models
• 701faca misc: merge v1.4 into main (#1500)
• b1f8711 chore: bump snapshot version to 1.3.113-SNAPSHOT
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #620.