George Fu comments

Results 216 comments of


                                            George Fu

"InvalidSignatureException: The request signature we calculated does not match the signature you provided" when calling a command with credentials from the SDK, but the same command and credentials work when called from the CLI

Is there any information on the region of the returned `credentials` before you feed them to `DynamoDBClient`? Could they be for the wrong region?

S3 Multi-Region Access Point(MRAP) is not available unless with additional dependency

The AWS SDK for JavaScript team is planning to change the usage of the optional CRT dependency in a future update. The change is described in this announcement: https://github.com/aws/aws-sdk-js-v3/issues/5229. The...

type checking error with `fromEnv` in @aws-sdk/credential-providers

`fromEnv` will not be provided in the browser, since `process` is a Node.js global and to use it would mean leaving credentials readable in an easily discoverable global object, vulnerable...

type checking error with `fromEnv` in @aws-sdk/credential-providers

@jove4015 please create a new issue with instructions on how to replicate the error.

Client retry strategy documentation

Docs on how to customize attempts and delay (backoff) computation are here: https://github.com/awslabs/smithy-typescript/blob/main/packages/util-retry/README.md One note: I have a PR open to fix a typo on that page, it should say...

Unable to use S3 with TypeScript and Yarn 3, missing dependencies

We have moved all types imports to dependencies and not devDeps.

TypeError: Cannot read property 'Code' of undefined

PR #4367 adds the suggested `?.Code` checked access operator. These TypeErrors should now fall through to the default error handler and give more information. The versioning containing it is https://github.com/aws/aws-sdk-js-v3/releases/tag/v3.261.0

Ini file takes over env variables for specifying credentials

I'm not able to reproduce this on the latest version, setting to closing-soon.

fix(property-provider): only reject if providers are not given to avoid debugger pause

https://github.com/awslabs/smithy-typescript/blob/main/packages/property-provider/src/chain.ts should no longer be an issue since there is no longer a promise rejection happening in the chain function.

Typescript compilation problems since 3.52.0 in lib-dynamodb

I'm able to install and compile a specific (not latest) version of the `client-dynamodb` and `lib-dynamodb` packages by adding a single override: ```json "dependencies": { "@aws-sdk/client-dynamodb": "3.287.0", "@aws-sdk/lib-dynamodb": "3.287.0" },...