This PR updates how the scripts handles presense of an AWS profile name.
If an AWS profile is present in the environment variables, the scripts uses it to communicate with Bedrock and Kendra.
If an AWS profile does not exist in the environment variables, the script will use the default profile.
Note, if you are running on SageMaker Studio Classic, the default profile will be your instance's IAM Execution Role so make sure it has the right IAM permissions to invoke models on Bedrock and query and retrieve from Kendra.
This has been tested on SageMaker Studio Classic with and without an AWS Profile defined. Both worked as expected.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
This PR updates how the scripts handles presense of an AWS profile name. If an AWS profile is present in the environment variables, the scripts uses it to communicate with Bedrock and Kendra. If an AWS profile does not exist in the environment variables, the script will use the default profile.
Note, if you are running on SageMaker Studio Classic, the default profile will be your instance's IAM Execution Role so make sure it has the right IAM permissions to invoke models on Bedrock and query and retrieve from Kendra.
This has been tested on SageMaker Studio Classic with and without an AWS Profile defined. Both worked as expected.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.