Missing dependency AWSSDK.SecurityToken ?

[peabnuts123]

Missing dependency AWSSDK.SecurityToken ?

[normj]

This is one of the awkward parts of the SDK where we have a circular dependency because the AWS credentials resolution and types all exist in Core but some credential profiles require AWSSDK.SecurityToken or other service clients but those service clients depend on core. This runtime dependency based approach is how we have solved the problem so far. I suspect we will need to revisit this design in the future as we try and add support for things like Native AOT which isn't going to like this approach.

[normj]

AWSSDK.SecurityToken is a runtime optional dependency needed depending on how the AWS credentials are sourced to the application. In fact this is the state for all of our libraries. We don't automatically include it because most production use cases don't need it and users want to keep the deployment bundles small. Especially for Lambda use cases.

With EKS credentials are often sourced via web identity token provided by EKS to the container. To turn the web identity token into AWS credentials AWSSDK.SecurityToken is used. Lambda uses environment variables and ECS and EC2 use a local network lookup so AWSSDK.SecurityToken is not needed in those use cases.

[peabnuts123]

Thanks for the clarification @normj. Is there anywhere this is documented? Could this not be perhaps a more intentional error, perhaps containing this information? As it stands, it looks more like a bug that the application has a missing dependency rather than something intended.

[ashishdhingra]

This is perhaps a documentation issue and Readme needs to document possible dependency on AWSSDK.SecurityToken.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.