Summary

A user reported they were still not able to use AWS IAM role policy with the changes from #4038. It was found that making these changes made it work, despite that the previous changes were working with ~/.aws/credentials when access keys were omitted.

• Modified the getOptions function in the Bedrock options file to omit the credentials field from the initial requestOptions object.
• Added a conditional check to include credentials in requestOptions only if they are explicitly provided.
• This change allows the AWS SDK to fall back to its default credential chain when no specific credentials are set, improving flexibility and adherence to AWS best practices.
• Maintained existing functionality for cases where credentials are explicitly provided.

Change Type

• New feature (non-breaking change which adds functionality)

Testing

To test this change:

1. Ensure that AWS credentials are properly configured in your environment (e.g., in ~/.aws/credentials, environment variables, or EC2 instance profile).
2. Run the application and attempt to use the Bedrock endpoint without explicitly providing credentials.
3. Verify that the application successfully authenticates with AWS and can interact with Bedrock services.
4. Test again with explicitly provided credentials to ensure that functionality is maintained.

Checklist

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• I have commented in any complex areas of my code
• My changes do not introduce new warnings
• I have tested my changes in various AWS credential scenarios