Daniel (dB.) Doubrovkine

I prefer the very explicit method that defaults to the old way, aka exactly what you said @mkcode. Give it a try!

I am going to speculate that `credentials` needs to be a credentials object like [here](https://github.com/aws-samples/aws-dataexchange-api-samples/blob/master/subscribers/javascript/all-entitled-datasets/index.ts#L3). Does that change anything? ```typescript const marketplacemetering = new MarketplaceMeteringClient({ region: 'us-west-2', credentials: new Credentials(tempCredentials)...

Ok, I am wrong. First, credentials now are brought in via providers that implement a basic Credentials interface, so you can just use a plain object/hash as you did, or...

I put this code up in https://github.com/aws-samples/aws-marketplace-api-samples/pull/4 and I get the expected error. ``` $ node -v v12.9.0 $ npm -v 6.10.2 $ npm run build { InvalidTokenException: Registration token...

Aha, so this is the actual problem. This is because metering does not support/allow CORS, see https://github.com/aws/aws-sdk-js/blob/master/SERVICES.md that says which ones do and which ones don't. I am not sure...

I have flagged this to someone in AWS who's close to this service, but I think it's a feature request at this point, so you should probably open a ticket...

@gjoshevski care to comment on ^?

Thanks @slimandslam. Consider PRing some changes into the actual documentation?

> I'll make you a deal. I'll PR some changes into the documentation if you successfully solve a JavaScript SDK v3 issue I have involving Marketplace API calls. Open another...

https://github.com/lostisland/faraday/issues/1090