The default credential provider dynamodb connector falls back to is InstanceProfileCredentialProvider. However, the instance profile is not available in all deployment environments (e.g. EMR Serverless). Instead, aws-java-sdk-v2's default provider should be used as the fallback to handle all environments. This keeps existing behavior as InstanceProfile provider is last provider in the default chain but also contains required providers for other deployments.
The default credential provider dynamodb connector falls back to is InstanceProfileCredentialProvider. However, the instance profile is not available in all deployment environments (e.g. EMR Serverless). Instead, aws-java-sdk-v2's default provider should be used as the fallback to handle all environments. This keeps existing behavior as InstanceProfile provider is last provider in the default chain but also contains required providers for other deployments.
Issue #, if available: N/A
Description of changes: See above
Testing mvn clean install:
Testing was done on an EMR cluster with hive queries connecting to dynamo db SQL executed:
Before change logs:
After change logs:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.