[reggegg]

For any proper use the AWS console is nothing more than a brochure of what you could be doing.

If you want to use their services properly, read the documentation for the ones you have chosen and use proper tooling that provides repeatability (for the lack of a better word), provided by AWS themselves or by a third party.

[Eikon]

The thing is, even “proper tooling” is a nightmare.

Tons of consistency issues in APIs, poor documentation, boto3 is atrocious where services names are passed as strings and why not use ‘args’, ‘*kwargs’ so you don’t know how to use the method by looking at the signature.

I had to implement s3 presigned URLs generation as we had no access to SDKs, the documentation is littered across their website, you literally have to go through dozens of pages to compile enough information.

Their quota system is borderline frightening, there is so much individual limitations that you may really never know if some limit is not gonna blow up in production.

Not to mention their voluntarily incomprehensible pricing. You may brankrupt your company just doing a few API calls and anyway, I generally found the overall quality of their products so poor that their premium just kills it.

Every time I know I’ll need to use one of their service, I prepare for the pain.

[ldoughty]

I generally support most things AWS does, but agree with you here. Though documentation you get a handle on fairly quick... Nearly all SDKs follow the same pattern. Still room for improvement. The lack of easy helpers (like for signing setup and validation) got us too.

Kinda to the other replies point though: does anyone do it better?

[webpaymentsguy]

>does anyone do it better?

Not currently, sadly, imo.

[tuesday20]

What other providers do you use?