Hello! Firstly, thanks so much for building this - dotnet script is amazing and I've started to convert a bunch of legacy helper scripts into my favorite language for safety and maintainability as a result! While upon this journey, I just started converting some helper scripts that run in AWS CodeBuild to perform some actions that typically required a string of cryptic bash commands during our CI/CD pipelines.

However, most recently the action that I am performing make use of the AWS SDKs for some service calls from the CI/CD pipeline (specifically AWS CodeBuild). There is a default credential resolution chain that the SDKs follow when explicit credentials are not provided within the application code via the AWS service client construction.

When running dotnet script to execute this script locally on my machine, the SDK successfully finds these credentials (for me in the .aws/credentials file) and the script execute successfully, able to interact with the AWS management plane. However, when running AWS CodeBuild, where an IAM Role is associated with the compute/CodeBuild Project; these credentials are not resolved successfully. Regular bash commands in the build spec, which utilize the AWS CLI, do successfully pick up the credentials for the IAM Role associated with this project).

Was wondering if you had any thoughts about what might be preventing this with respect to how the scripts are executed.
I've opened up a ticket with the AWS .NET SDK team for this issue (aws/aws-sdk-net#3724) but the person helping me out indicated that they are not super familiar with dotnet script so I figured I'd ask here :).

Thanks so much!