release-26.3: roachtest: cluster_creation failed

roachtest.cluster_creation [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyAwsBazel/21392023?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyAwsBazel/21392023?buildTab=artifacts#/cdc/fine-grained-checkpointing) on release-26.3 @ [8a9a8e3305daa0890b7b083c13cb572f911bd6cc](https://github.com/cockroachdb/cockroach/commits/8a9a8e3305daa0890b7b083c13cb572f911bd6cc):

```
test cdc/fine-grained-checkpointing failed: (test_runner.go:1017).func4: in provider: aws: failed to create instance teamcity-21392023-1781763034-29-n4cpu4-0001: aws create failed due to capacity for machine type m6id.xlarge in zone(s) [us-east-2c]; suggested zone(s): [us-east-2a us-east-2b]: failed to run: aws ec2 run-instances --associate-public-ip-address --count 1 --instance-type m6id.xlarge --image-id ami-0e83be366243f524a --key-name teamcity-runner-1I59zCM50jZh2E_vhOMi3n7oK40= --region us-east-2 --security-group-ids sg-04d72b57e29d671f1 --subnet-id subnet-0e71591c1fe06645e --tag-specifications ResourceType=instance,Tags=[{Key=usage,Value=roachtest},{Key=roachtest-branch,Value=release-26-3},{Key=Name,Value=teamcity-21392023-1781763034-29-n4cpu4-0001},{Key=Cluster,Value=teamcity-21392023-1781763034-29-n4cpu4},{Key=spot,Value=true},{Key=roachprod,Value=true},{Key=cluster,Value=teamcity-21392023-1781763034-29-n4cpu4},{Key=lifetime,Value=12h0m0s},{Key=arch,Value=amd64},{Key=created,Value=2026-06-18T06:53:46Z}] ResourceType=volume,Tags=[{Key=usage,Value=roachtest},{Key=roachtest-branch,Value=release-26-3},{Key=Name,Value=teamcity-21392023-1781763034-29-n4cpu4-0001},{Key=Cluster,Value=teamcity-21392023-1781763034-29-n4cpu4},{Key=spot,Value=true},{Key=roachprod,Value=true},{Key=cluster,Value=teamcity-21392023-1781763034-29-n4cpu4},{Key=lifetime,Value=12h0m0s},{Key=arch,Value=amd64},{Key=created,Value=2026-06-18T06:53:46Z}] --user-data file:///tmp/aws-startup-script1558875654 --iam-instance-profile Name=roachprod-testing --block-device-mapping file:///tmp/aws-block-device-mapping3365380666 --instance-market-options MarketType=spot,SpotOptions={SpotInstanceType=one-time,InstanceInterruptionBehavior=terminate} --output json: stderr:
An error occurred (InsufficientInstanceCapacity) when calling the RunInstances operation (reached max retries: 2): We currently do not have sufficient m6id.xlarge capacity in the Availability Zone you requested (us-east-2c). Our system will be working on provisioning additional capacity. You can currently get m6id.xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2a, us-east-2b.: exit status 254 [owner=test-eng]
```

Parameters:
- cloud=aws
- coverageBuild=false
- cpu=4
- diskCount=0
- runtimeAssertionsBuild=false
Help

See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)

See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)

/cc @cockroachdb/test-eng

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*cluster_creation.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Jira issue: CRDB-64900

Start with the linked TeamCity failure log and artifacts, then read the roachtest README and the linked roachdash report. Determine whether the cluster_creation failure is reproducible and what project change, if any, is required for AWS capacity errors; done requires an agreed resolution rather than another unexplained failed run.

Written by the indexing model from the issue text.