Mismatch Credential Type (@aws-sdk/client-ec2 and @aws-sdk/client-sts)

Describe the bug

Looks like there is a mismatch between credential types in @aws-sdk/client-ec2, @aws-sdk/client-sts such that credentials generated by the Security Token Service SDK can’t directly be used in the EC2 SDK.

Type defintion of Credentials from @aws-sdk/client-ec2

interface Credentials {
    /**
     * AWS access key ID
     */
    readonly accessKeyId: string;
    /**
     * AWS secret access key
     */
    readonly secretAccessKey: string;
    /**
     * A security or session token to use with these credentials. Usually
     * present for temporary credentials.
     */
    readonly sessionToken?: string;
    /**
     * A {Date} when these credentials will no longer be accepted.
     */
    readonly expiration?: Date;
}

Type defintion of Credentials from @aws-sdk/client-sts

interface Credentials {
    /**
     * <p>The access key ID that identifies the temporary security credentials.</p>
     */
    AccessKeyId: string | undefined;
    /**
     * <p>The secret access key that can be used to sign requests.</p>
     */
    SecretAccessKey: string | undefined;
    /**
     * <p>The token that users must pass to the service API to use the temporary
     *          credentials.</p>
     */
    SessionToken: string | undefined;
    /**
     * <p>The date on which the current credentials expire.</p>
     */
    Expiration: Date | undefined;
}

Your environment

SDK version number

@aws-sdk/client-ec2@3.12.0 @aws-sdk/client-sts@3.13.0

Is the issue in the browser/Node.js/ReactNative?

Node.js

Details of the browser/Node.js/ReactNative version

v15.10.0

Steps to reproduce

const credentialsProvider = fromIni({ profile: argv.profile });

const roleCredentialsProvider = async () => {
  const client = new STSClient({ region: 'us-east-1', credentials: credentialsProvider});

  const assumeRoleRequest = new AssumeRoleCommand({
    RoleArn: 'arn:aws:iam::<ACCOUNT_HERE>:role/<ROLE_HERE>',
    RoleSessionName: '<SESSION_NAME>',
  });

  const response = await client.send(assumeRoleRequest);

  return response.Credentials;
};

const client = new EC2Client({ region: 'us-east-1', credentials: roleCredentialsProvider });

Observed behavior

The error that results in this incorrect value being passed in.

TypeError: Cannot read property 'byteLength' of undefined
    at Object.fromArrayBuffer (/Users/tcvs/Development/Tulip/tulip/environments/node_modules/@aws-sdk/util-buffer-from/dist/cjs/index.js:6:60)
    at castSourceData (/Users/tcvs/Development/Tulip/tulip/environments/node_modules/@aws-sdk/hash-node/dist/cjs/index.js:29:31)
    at Hash.update (/Users/tcvs/Development/Tulip/tulip/environments/node_modules/@aws-sdk/hash-node/dist/cjs/index.js:12:26)
    at hmac (/Users/tcvs/Development/Tulip/tulip/environments/node_modules/@aws-sdk/signature-v4/dist/cjs/credentialDerivation.js:60:10)
    at Object.getSigningKey (/Users/tcvs/Development/Tulip/tulip/environments/node_modules/@aws-sdk/signature-v4/dist/cjs/credentialDerivation.js:32:29)
    at SignatureV4.getSigningKey (/Users/tcvs/Development/Tulip/tulip/environments/node_modules/@aws-sdk/signature-v4/dist/cjs/SignatureV4.js:139:39)
    at SignatureV4.signRequest (/Users/tcvs/Development/Tulip/tulip/environments/node_modules/@aws-sdk/signature-v4/dist/cjs/SignatureV4.js:98:73)
    at processTicksAndRejections (node:internal/process/task_queues:94:5)
    at async /Users/tcvs/Development/Tulip/tulip/environments/node_modules/@aws-sdk/middleware-signing/dist/cjs/middleware.js:14:22
    at async StandardRetryStrategy.retry (/Users/tcvs/Development/Tulip/tulip/environments/node_modules/@aws-sdk/middleware-retry/dist/cjs/defaultStrategy.js:56:46)
    at async /Users/tcvs/Development/Tulip/tulip/environments/node_modules/@aws-sdk/middleware-logger/dist/cjs/loggerMiddleware.js:6:22
    at async initSpotInstances (/Users/tcvs/Development/Tulip/tulip/environments/cypress/loadTest/ec2LoadTest.js:171:30)
    at async main (/Users/tcvs/Development/Tulip/tulip/environments/cypress/loadTest/ec2LoadTest.js:255:18) {
  '$metadata': { attempts: 1, totalRetryDelay: 0 }
}

Expected behaviour

Expected that I would be able to pass the credentials object directly or at least have a more usuable error to make this more easily debuggable.

[jackallnutt]

I am experiencing the same problem with @aws-skd/client-s3.

[github-actions[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.