Bug description Current documentation states:
AWS region is resolved in the following order: - Spring-AI Bedrock spring.ai.bedrock.aws.region property. - Java System Properties - aws.region. - Environment Variables - AWS_REGION. - Credential profiles file at the default location (~/.aws/credentials) shared by all AWS SDKs and the AWS CLI. - Instance profile region delivered through the Amazon EC2 metadata service.
In case when region configuration provided only using spring.ai.bedrock.aws.region property (no Java System Properties, Env Vars, etc) Folowing WARN log appears:
o.s.a.b.c.BedrockProxyChatModel - Failed to load region from DefaultAwsRegionProviderChain, using US_EAST_1
2025-12-16T14:51:07.757422240Z software.amazon.awssdk.core.exception.SdkClientException: Unable to load region from any of the providers in the chain software.amazon.awssdk.regions.providers.DefaultAwsRegionProviderChain@f989d46: [software.amazon.awssdk.regions.providers.SystemSettingsRegionProvider@1dca91d6: Unable to load region from system settings. Region must be specified either via environment variable (AWS_REGION) or system property (aws.region)., software.amazon.awssdk.regions.providers.AwsProfileRegionProvider@4ebbee76: No region provided in profile: default, software.amazon.awssdk.regions.providers.InstanceProfileRegionProvider@1c7385d: Unable to contact EC2 metadata service.]
It happens in BedrockConverseProxyChatAutoConfiguration while BedrockProxyChatModel.builder() execution. Builder in its constructor checks DefaultAwsRegionProviderChain in order to find region and produces WARN log if nothing was found without consideration of spring.ai.bedrock.aws.region property.
Hopefully autoconfiguration provides region to the builder after creation, so the resulting ChatModel will use configured region, but WARN log doe's not represent current state of the application and looks confusing.
Environment Spring AI version: 1.1.2
Expected behavior No WARN logs in case spring.ai.bedrock.aws.region property exists.