Dataset builders
bedrockbot is a bot operated by Amazon that crawls pages into a dataset that may be reused or shared with third parties. Connects to and crawls URLs that have been selected for use in a user's AWS bedrock application. It is documented as honouring robots.txt, but no IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine.
Request says
"bedrockbot"
Checked against
Nothing published
Live check
No operator check exists for bedrockbot. This still shows what the address really is.
Reference
| User agent | bedrockbotToken only: match on the substring. |
|---|---|
| Operator | Amazon |
| Purpose | Data scraping for custom AI applications. |
| Respects robots.txt | Honourssource |
| Verification method | Claim onlyNone published, user agent only Runs from an AWS customer account, so the source IP belongs to whoever configured the Bedrock knowledge base rather than to AWS as a crawler operator. https://docs.aws.amazon.com/bedrock/latest/userguide/webcrawl-data-source-connector.html |
| Crawl pattern | Not published |
| Robots.txt tokens | bedrockbot |
| Operator documentation | None published |
Connects to and crawls URLs that have been selected for use in a user's AWS bedrock application.
robots.txt
Paste one at the root of your domain. Rules are per token.
User-agent: bedrockbot
Disallow: /User-agent: bedrockbot
Allow: /User-agent: bedrockbot
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking bedrockbot keeps your pages out of the datasets it builds from future crawls. It does not remove anything collected earlier, and how each operator uses or shares its data varies, so check their policy.
Build a file for every crawlerFAQ
bedrockbot is a bot operated by Amazon that crawls pages into a dataset that may be reused or shared with third parties. Connects to and crawls URLs that have been selected for use in a user's AWS bedrock application. It is documented as honouring robots.txt, but no IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine.
Yes. The operator documents that bedrockbot reads robots.txt and follows Disallow rules for its own token. Rules take effect on the next fetch of the file, which can be hours or days after you publish them.
You cannot, at least not from the request itself. Runs from an AWS customer account, so the source IP belongs to whoever configured the Bedrock knowledge base rather than to AWS as a crawler operator. Compare the source IP against hosting and datacenter ranges instead, and rate limit anything that behaves like a crawler.
Add the bedrockbot token to robots.txt with Disallow: /. If the crawler ignores robots.txt, match the user agent at your CDN or reverse proxy and return 403 there instead.
Blocking bedrockbot keeps your pages out of the datasets it builds from future crawls. It does not remove anything collected earlier, and how each operator uses or shares its data varies, so check their policy.