(Feel free to update this bug's summary to be more specific.)
Component Readiness has found a potential regression in the following test:

install should succeed: infrastructure

Significant regression detected.
Fishers Exact probability of a regression: 100.00%.
Test pass rate dropped from 100.00% to 89.29%.

Sample (being evaluated) Release: 4.21
Start Time: 2025-11-14T00:00:00Z
End Time: 2025-11-21T20:00:00Z
Success Rate: 89.29%
Successes: 50
Failures: 6
Flakes: 0
Base (historical) Release: 4.19
Start Time: 2025-05-18T00:00:00Z
End Time: 2025-06-17T00:00:00Z
Success Rate: 100.00%
Successes: 133
Failures: 0
Flakes: 0

View the test details report for additional context.

========================================

During periods of heavy load in the aws account, installs may fail with:

```
level=error msg=failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed during pre-provisioning: failed to create IAM roles: failed to get master instance profile: operation error IAM: GetInstanceProfile, exceeded maximum number of attempts, 3, https response error StatusCode: 400, RequestID: 3ebea067-1aee-4a94-a71b-b1b3c1326d38, api error Throttling: Rate exceeded
```

We can fix this by increasing the number of retry attempts from the default of 3 and also disable the new built-in client-side rate limiter, which was brought in through the aws sdk v2 upgrade.