Skip to content

[v2] Enable CRT S3 transfer client by default on all remaining EC2 instances - #10728

Merged
aemous merged 5 commits into
v2from
crt-rollout-5
Oct 6, 2026
Merged

aemous merged 5 commits into
v2from
crt-rollout-5

Conversation

@aemous

@aemous aemous commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

Issue #, if available:

#10676

Description of changes:

  • Enable the CRT S3 transfer client by default for all remaining EC2 instances. This includes removing the allowlist from internal code and documentation.
  • Update outdated unit tests that relied on some EC2 instances not being rolled out yet.
  • Update docs to clarify all EC2 families auto-resolve to CRT S3 transfer client by default (barring config settings).

Description of tests:

  • Successfully ran all tests and CI (see GitHub Actions).

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@aemous
aemous requested a review from a team as a code owner October 5, 2026 20:35
Comment thread awscli/topics/s3-config.rst Outdated
Comment on lines +344 to +345
* Note that the ``crt`` transfer client is current optimized
urrently, these instance types are: ``p4d.24xlarge``, ``p4de.24xlarge``,

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fragment "urrently". And should we just remove this list and revise the bullet on L341 to "The host running the AWS CLI is an Amazon EC2 instance "

@aemous aemous Oct 6, 2026 •

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will push a fix for the typo.

I kept the list of optimized instance families in the docs for two reasons:

  1. The list is referenced later in the docs to determine fallback logic, so it's helpful for customers to know whether their host is considered optimized to understand CLI fallback logic:

The crt transfer client supports the requested transfer. If the host
is not of an instance type that the crt transfer client is optimized
for, the AWS CLI falls back to the classic transfer client when any
of the following are in use:

  1. Which hosts are optimized is valuable information for customers. It may guide their decision in choosing a host, for example.

Open to discussion / feedback.

Comment thread awscli/topics/s3-config.rst Outdated
@aemous
aemous requested review from ashovlin and luigi617 October 6, 2026 14:17
Comment thread awscli/customizations/s3/factory.py Outdated
@aemous
aemous requested a review from luigi617 October 6, 2026 14:43
is not of an instance type that the ``crt`` transfer client is optimized
for, the AWS CLI falls back to the ``classic`` transfer client when any
of the following are in use:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like this part is confusing. We are rolling out all the EC2 instances, but as we removed the list of instance families, my understanding of this sentence is, crt will be used only for p4d.24xlarge``, p4de.24xlarge``, ....and for all other families we are falling back to classic transfer client.

@aemous aemous Oct 6, 2026 •

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the AWS CLI falls back to the classic transfer client when any
of the following are in use:

crt will be used only for p4d.24xlarge, ... and for all other families we fall back to classic client when certain config settings are used.

does this help resolve the confusion? do you have suggested alternative wording?

@luigi617 luigi617 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@aemous
aemous merged commit c1dd101 into v2 Oct 6, 2026
111 of 112 checks passed
@aemous
aemous deleted the crt-rollout-5 branch October 6, 2026 16:53
aemous added a commit that referenced this pull request Oct 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants