amazon-bedrock provider may not support EC2 Instance Metadata (IMDSv2) as a credential source #17777

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Summary
When running OpenCode on an EC2 instance with an IAM Instance Profile (EC2 Role), the amazon-bedrock provider doesn't seem to load properly.

Background
I'm running OpenCode on an EC2 instance that has an IAM Instance Profile attached. IMDSv2 is enforced on the instance (IMDSv1 is disabled, which is the current AWS default for new instances). No explicit AWS credentials are configured — the expectation is that the AWS SDK would automatically discover credentials via the Instance Metadata Service, as it does with other AWS tools and SDKs.
However, without manually injecting credentials via environment variables, the amazon-bedrock provider does not appear to load and Bedrock models are unavailable.

Looking at the provider initialization code, there appears to be a guard condition along the lines of:
if (!profile && !awsAccessKeyId && !awsBearerToken && !awsWebIdentityTokenFile && !containerCreds)
return { autoload: false };
If this is indeed the case, EC2 Instance Metadata would not be among the recognized credential sources, causing the provider to exit early before fromNodeProviderChain() ever gets a chance to resolve credentials via IMDS — even though the bundled @smithy/credential-provider-imds package appears to support IMDSv2.
That said, I may be misreading the code or missing something. Is this the intended behavior, or could this be a gap in credential source coverage?

Environment

• Running on: EC2 instance with IAM Instance Profile
• IMDSv1: disabled (IMDSv2 only)
• OpenCode installed via npm install -g opencode-ai
• Bundled credential provider: @smithy/[email protected]