Safe Official docs AI & LLM Bots

AWS Bedrock Bot

Operated by Amazon

Quick Facts

User-Agent:
bedrockbot
Category:
AI & LLM Bots
Operator:
Amazon
Safety:
Safe
Blocking Impact:
Low - No SEO ranking impact
SEO Impact Score:
2/10
Official docs:
docs.aws.amazon.com

Confirmed by the operator

Amazon names bedrockbot on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

What is AWS Bedrock Bot?

AWS Bedrock Bot is an AI data-collection crawler operated by Amazon. It gathers public web content to build or refine training datasets for large language models. Like other AI training crawlers, AWS Bedrock Bot does not influence your search-engine rankings, so you can block it via robots.txt without any SEO penalty if you wish to opt out of AI training.

AWS Bedrock Bot is an AI data-collection crawler operated by Amazon. It gathers public web content to build or refine training datasets for large language models. Like other AI training crawlers, AWS Bedrock Bot does not influence your search-engine rankings, so you can block it via robots.txt without any SEO penalty if you wish to opt out of AI training.
AWS Bedrock Bot uses the user-agent token bedrockbot. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.

What happens if you block AWS Bedrock Bot?

✅ No SEO Impact - Blocking AWS Bedrock Bot does not affect your rankings in Google, Bing, or any other search engine. AWS Bedrock Bot is an AI crawler, not a traditional search indexer. You can freely block it via User-agent / Disallow: / without any SEO penalty.
Generally safe to allow; provides legitimate crawling value.

Want to see whether AWS Bedrock Bot actually visits you? Read how do I monitor AI bot traffic to my website?

How to block AWS Bedrock Bot with robots.txt

<code>User-agent: bedrockbot</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)
User-agent: bedrockbot Disallow: /
Allow all (robots.txt)
User-agent: bedrockbot Allow: /
Block private only (robots.txt)
User-agent: bedrockbot Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Hard-block AWS Bedrock Bot if ($http_user_agent ~* "bedrockbot") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Hard-block AWS Bedrock Bot SetEnvIfNoCase User-Agent "bedrockbot" bad_bot Order Allow,Deny Allow from all Deny from env=bad_bot
Meta robots tag
<meta name="robots" content="noindex, nofollow">
X-Robots-Tag header
X-Robots-Tag: noindex, nofollow

Is AWS Bedrock Bot safe to allow?

Yes, AWS Bedrock Bot is a safe and legitimate crawler operated by Amazon. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.
Verify by reverse-DNS lookup: legitimate AWS Bedrock Bot requests resolve to Amazon's domain.

What does AWS Bedrock Bot do?

Understanding AWS Bedrock Bot's purpose helps you decide whether to allow or block it.

  • Collects public web content to train large language models
  • Builds and refreshes AI training datasets
  • Harvests text, code, and structured data for model improvement
  • Does NOT affect search-engine rankings
  • Can be blocked to opt out of AI training without SEO loss

AWS Bedrock Bot in context

AWS Bedrock Bot is a user-triggered agent operated by Amazon. In plain terms, it collects pages to train AI models. Our database files it under AI and LLM crawlers and ranks it Tier 2, important crawlers from established AI and search operators. 74 of the 104 AI and LLM crawlers in our database share this tier.

Its safety rating is safe and its blocking impact is low. So the decision about AWS Bedrock Bot rests on what you want from Amazon, not on its behaviour. How we rate safety and impact.

How site owners treat AWS Bedrock Bot

Our robots.txt study of the Tranco top 10,000 did not track bedrockbot as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

AWS Bedrock Bot's operator says it follows robots.txt, so a correctly written AWS Bedrock Bot group is enough to control it.

Amazon crawlers and close alternatives

AWS Bedrock Bot is one of 8 Amazon crawlers in our database. A User-agent: bedrockbot group controls AWS Bedrock Bot only; the other Amazon tokens below need their own lines.

  • bedrockbot: this crawler (Tier 2)
  • Amazon Kendra: Amazon Kendra, harvests pages for a dataset or data product (Tier 6)
  • amazon-QBusiness: Amazon Q Business, builds a search or answer index (Tier 3)
  • Amazonbot: Amazon Nova AI, collects pages to train AI models (Tier 2)
  • AmazonBuyForMe: Amazon Buy For Me, fetches a page when a person asks an assistant or app to open it (Tier 2)
  • Amzn-SearchBot: Amzn-SearchBot, builds a search or answer index (Tier 3)
  • Amzn-User: Amazon User Agent, fetches a page when a person asks an assistant or app to open it (Tier 2)
  • NovaAct: Amazon Nova Act, harvests pages for a dataset or data product (Tier 2)

To give AWS Bedrock Bot the same answer as its siblings, stack User-agent: bedrockbot with their lines above one set of rules; to treat AWS Bedrock Bot differently, give it its own group.

Other AI and LLM crawlers that do the same job (collects pages to train AI models) include ClaudeBot from Anthropic, Google-Extended from Google, GPTBot from OpenAI, Meta-ExternalAgent from Meta, AI2Bot from Allen Institute for AI, aiHitBot from aiHit. Deciding about AWS Bedrock Bot is usually a decision about the whole group, so check how your file treats these too.

We first recorded bedrockbot on June 18, 2026. Amazon documents it on docs.aws.amazon.com, and we recheck that page before each release.

Which rule AWS Bedrock Bot actually follows

AWS Bedrock Bot reads exactly one group in robots.txt, the most specific one that names bedrockbot, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: bedrockbot
Disallow: /drafts/
  1. Find the group. AWS Bedrock Bot looks for a group naming bedrockbot. One exists, so it ignores User-agent: * completely.
  2. Apply only that group. It is refused /drafts/ and nothing else.
  3. The surprise. /private/ is open to AWS Bedrock Bot, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.
Test yourself: does a rule under User-agent: * apply to AWS Bedrock Bot if the file also has a User-agent: bedrockbot group?

No. Once a group names it, AWS Bedrock Bot reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking AWS Bedrock Bot remove your pages from AI answers?

Often, yes. AWS Bedrock Bot is a user-triggered agent, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: bedrockbot the same as User-agent: bedrockbot?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow AWS Bedrock Bot? Decide by situation

Recommended setting for AWS Bedrock Bot by type of site
If you are...Recommended setting
You publish content and want AI answers to cite itAllow it. AWS Bedrock Bot fetches pages for answers, so blocking it can remove you from them.
You license content and want to stop AI trainingBlocking it does not stop training, because AWS Bedrock Bot is a user-triggered agent. Block the operator's training crawler instead.
You run an online shopAllow it on product and category pages, which are the pages shoppers ask assistants about.
Your server is under load from botsRate-limit before blocking. It is rated safe in our database.

Check AWS Bedrock Bot on your own site

  1. Open /robots.txt on your domain and search for bedrockbot. If it is not named, it follows User-agent: *.
  2. List the Disallow lines in the group AWS Bedrock Bot follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
  3. Look beyond the file. A firewall or bot manager can refuse AWS Bedrock Bot even when robots.txt allows it, and that never shows in the file.
  4. Run our GPTBot and ClaudeBot access check to see how AWS Bedrock Bot and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with AWS Bedrock Bot

The errors we see most often with AWS Bedrock Bot in the files and firewalls we test:

  1. Assuming a robots.txt rule will stop AWS Bedrock Bot. User-triggered fetches act for a person, and some operators say robots.txt may not apply to them. Check the operator's statement above.
  2. Blocking AWS Bedrock Bot as if it were a bulk crawler. It fetches one page because a person asked; blocking it means that person's assistant cannot read your page.
  3. Counting AWS Bedrock Bot visits as crawl volume. Each request maps to a real user question, which makes the paths it requests a useful signal of what people ask about you.

All three hide inside a file that looks correct, so check AWS Bedrock Bot from outside after every change.

Spotting AWS Bedrock Bot in your logs

robots.txt says what AWS Bedrock Bot may do; your access logs show what it actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "bedrockbot" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "bedrockbot" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the AWS Bedrock Bot user-agent, so confirm the source before acting on a match:

  • bedrockbot: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable AWS Bedrock Bot request with caution.

Frequently Asked Questions

What is the official user-agent string for AWS Bedrock Bot?
The official user-agent string for AWS Bedrock Bot is: bedrockbot. Use this exact string in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. Matching in robots.txt is case-insensitive. Verify a request genuinely comes from AWS Bedrock Bot by performing a reverse-DNS lookup on the source IP.
Is AWS Bedrock Bot safe?
Yes, AWS Bedrock Bot is a safe and legitimate crawler operated by Amazon. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.
Will blocking AWS Bedrock Bot hurt my SEO?
✅ No SEO Impact - Blocking AWS Bedrock Bot does not affect your rankings in Google, Bing, or any other search engine. AWS Bedrock Bot is an AI crawler, not a traditional search indexer. You can freely block it via User-agent / Disallow: / without any SEO penalty.
How do I block AWS Bedrock Bot in robots.txt?
Add the following lines to your /robots.txt file:
User-agent: bedrockbot
Disallow: /

This instructs AWS Bedrock Bot not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).
Does AWS Bedrock Bot respect robots.txt?
AWS Bedrock Bot is operated by Amazon and is expected to fetch and parse /robots.txt before crawling, following RFC 9309. For hard enforcement, combine robots.txt with server-level IP or user-agent blocking.
How do I verify if AWS Bedrock Bot is crawling my site?
Search your web server access logs for the string bedrockbot (case-insensitive: grep -i "bedrockbot" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).

Related Bots

WhatsApp us