aws / aws-dotnet-extensions-configuration

This repository hosts various libraries that help developers configure .NET applications using AWS services.

Home Page:https://aws.amazon.com/developer/language/net/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Upgrade aws-sdk-net packages to version with support for sts:AssumeRoleWithWebIdentity

brianbakeratx opened this issue · comments

AWS has added EKS support for IAM Roles for Service Accounts.

This new EKS feature requires an updated SDK that contains a new credential provider that calls sts:AssumeRoleWithWebIdentity. It looks like aws-sdk-net 3.3.101 contains this change to support sts:AssumeRoleWithWebIdentity.

Any update on this?

Hi @brianbakeratx,

Good afternoon.

Please check if the new version 2.0.0 for Amazon.Extensions.Configuration.SystemsManager on NuGet https://www.nuget.org/packages/Amazon.Extensions.Configuration.SystemsManager/ resolves the issue. I do see that the latest Amazon.Extensions.Configuration.SystemsManager.csproj references version 3.3.101 of AWSSDK.Extensions.NETCore.Setup.

Thanks,
Ashish

Still problems here.

Unhandled exception. System.InvalidOperationException: Assembly AWSSDK.SecurityToken could not be found or loaded. This assembly must be available at runtime to use Amazon.Runtime.AssumeRoleAWSCredentials. mysampleapp ---> System.IO.FileNotFoundException: Could not load file or assembly 'AWSSDK.SecurityToken, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.

We might just need to add the AWSSDK.SecurityToken package but this means that the aws-dotnet-extensions-configuration has a dependency on it and I believe it should be adding this as per my pull request:
#73 @ashishdhingra

Upgrading to the 2.0.0 package and adding a reference to AWSSDK.SecurityToken fixed the issue.

This issue has not recieved a response in 2 weeks. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled.