[request]: Support static & STS assume role credentials in the ECS / HTTPS credentials provider

[rcoh]

trafficstars

Tell us about your request

Currently, the ECS/HTTPS credentials provider only supports refreshable credentials with a token & an expiry but this doesn't support all use cases effectively eg. for customers with their own HTTPS credentials provider that returns static credentials. Add support for static credentials:

       //  {
       //    "AccessKeyId" : "MUA...",
       //    "SecretAccessKey" : "/7PC5om...."
       //  }

and assume role credentials:

       //   {
       //     // fields to construct STS client:
       //     "Region": "sts-region-name",
       //     "AccessKeyId" : "MUA...",
       //     "Expiration" : "2016-02-25T06:03:31Z", // optional
       //     "SecretAccessKey" : "/7PC5om....",
       //     "Token" : "AQoDY....=", // optional
       //     // fields controlling the STS role:
       //     "RoleArn": "...", // required
       //     "RoleSessionName": "...", // required
       //     // and also: DurationSeconds, ExternalId, SerialNumber, TokenCode, Policy
       //     ...
       //   }

Tell us about the problem you're trying to solve.

use my HTTP credential provider that I use with other AWS SDKs

Are you currently working around this issue?

with my own custom credentials provider

Additional context

No response

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue, please leave a comment