cloudscraper VS aws-sdk-rust

Try https://github.com/yifeikong/curl_cffi or https://github.com/VeNoMouS/cloudscraper , I believe you should be able to bypass this.

But scraping has definitely gotten tougher with services like cloudflare that even the popular cloudscraper gave up years ago and never made a comeback.

If you're scraping with Python, try cloudscraper—among other things(!), it supports JS rendering (basically the bare-minimum check cloudflare does), without needing to run a full browser in the background. It's built on requests, so integration (for me, anyway) was pretty easy.

https://github.com/venomous/cloudscraper

I've tried using Cloudscraper here https://github.com/VeNoMouS/cloudscraper but I get the following error:

No amount of googling turns up anything. There are others with the same problem - but no real solution. In the gitlab README it explains that to solve CAPTCHAs with cloudscraper you need an API key, which would explain the error that it's not available in the free version. But for the life of me, I can't find where to get a key or any other solution.

cloudscraper

Anyone with a stake in bypassing anti-bot measures isn't going to share their tactics, since sharing it will lead to such workaround being patched or mitigated, requiring them to research for more bot detection workarounds.

Projects like cloudscraper[0] are often linked to point and say "look! they broke Cloudflare!" but CF and the rest of the industry has detections for tools like this, and instead of rolling out blocks for these tools, they give website owners tools like bot score[1] to manage their own risk level on a per-page basis.

0: https://github.com/VeNoMouS/cloudscraper

1: https://developers.cloudflare.com/bots/concepts/bot-score/

This is being used: https://github.com/VeNoMouS/cloudscraper

The AWS SDK for Rust contains one crate for each AWS service - you can check them out here.

> What kind of plans for support of Rust's evolving async ecosystem?

We were hoping async-function-in-trait would land before GA, however, we have a plan to add support in a backwards compatible way when it's released.

> Any particular reason why the public roadmap does not show the columns similar to "Researching", "We're Working On It" like the other similar public AWS Roadmaps?

Our roadmap has unfortunately been in a state of disrepair for some time. We're hoping to get it cleaned up and accurate post GA.

> Would be nice to have fully working examples on Github, for most common scenarios across most AWS services. This is something that historically AWS SDKs have been inconsistent on. Just a request not really a question :-)

There are lots of examples here [1], some simple, some quite complex. If there's something you have in mind, please file an issue! Having great examples is one of our priorities.

[1]: https://github.com/awslabs/aws-sdk-rust/tree/main/examples

There’s a pretty nice example of this in the aws rust sdk here.

The official AWS Rust SDK still seems to be a work in progress(developer preview) with a warning to not use it in production.

i'm using https://github.com/awslabs/aws-sdk-rust heavily and was wondering if there was a more specific community (subreddit, Discord server, etc) of Rust x AWS developers?

Only relevant search result was this github issue, which didn't really solve the problem.

I went on rusoto just because aws-sdk-rust says at the beginning of the readme:

Official libraries for major cloud vendors will definitely boost Rust's adoption. aws-sdk-rust is still in 'developer preview', but it's getting there.