Safe Cloud Services

Amazon-Bedrock-AgentCore

Operated by Amazon

Quick Facts

User-Agent:
Amazon-Bedrock-AgentCore
Category:
Cloud Services
Operator:
Amazon
Safety:
Safe
Blocking Impact:
Low - No SEO ranking impact
SEO Impact Score:
2/10
Official docs:
docs.aws.amazon.com

What is Amazon-Bedrock-AgentCore?

Amazon-Bedrock-AgentCore fetches a page when an AWS Bedrock agent needs live web content to answer a request, so it visits on demand rather than crawling continuously.

Amazon-Bedrock-AgentCore fetches a page when an AWS Bedrock agent needs live web content to answer a request, so it visits on demand rather than crawling continuously. Amazon-Bedrock-AgentCore identifies itself with the user-agent token Amazon-Bedrock-AgentCore. You can control it with a User-agent: Amazon-Bedrock-AgentCore group in robots.txt. Robots.txt is voluntary, so for hard enforcement combine it with server-level blocking.

What happens if you block Amazon-Bedrock-AgentCore?

✅ Blocking Amazon-Bedrock-AgentCore has no effect on search rankings, because it does not build a search index and does not crawl on a schedule. It fetches a page only when an AWS Bedrock agent needs live content to answer a specific user request. Blocking it means those agents cannot read your pages when a user asks them to.
Safe to allow or block, depending on whether you want agent traffic.

How to control Amazon-Bedrock-AgentCore with robots.txt

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

Block completely (robots.txt)
User-agent: Amazon-Bedrock-AgentCore Disallow: /
Allow all (robots.txt)
User-agent: Amazon-Bedrock-AgentCore Allow: /
Block private only (robots.txt)
User-agent: Amazon-Bedrock-AgentCore Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Block Amazon-Bedrock-AgentCore if ($http_user_agent ~* "Amazon-Bedrock-AgentCore") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Block Amazon-Bedrock-AgentCore SetEnvIfNoCase User-Agent "Amazon-Bedrock-AgentCore" 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 Amazon-Bedrock-AgentCore safe to allow?

Yes, Amazon-Bedrock-AgentCore is a **safe and legitimate** crawler. It is operated by Amazon and documented publicly, and it identifies itself honestly with the token Amazon-Bedrock-AgentCore. Safe to allow or block, depending on whether you want agent traffic.
Verify by confirming the request comes from Amazon's published IP ranges rather than trusting the user-agent alone.

What does Amazon-Bedrock-AgentCore do?

Understanding what Amazon-Bedrock-AgentCore is for helps you decide whether to allow or block it.

  • Fetches live pages for AWS Bedrock agents
  • Visits on demand when an agent needs context
  • Does not crawl continuously or build an index
  • Content is used to answer a specific request
  • Respects robots.txt directives

Frequently Asked Questions

What is the user-agent string for Amazon-Bedrock-AgentCore?
Amazon-Bedrock-AgentCore uses the token Amazon-Bedrock-AgentCore. Match it case-insensitively in robots.txt and in any server-level rule.
Is Amazon-Bedrock-AgentCore safe?
Yes. Amazon-Bedrock-AgentCore is operated by Amazon and is documented publicly. Amazon-Bedrock-AgentCore fetches a page when an AWS Bedrock agent needs live web content to answer a request, so it visits on demand rather than crawling continuously.
Will blocking Amazon-Bedrock-AgentCore hurt my SEO?
Blocking Amazon-Bedrock-AgentCore has no effect on search rankings, because it does not build a search index and does not crawl on a schedule. It fetches a page only when an AWS Bedrock agent needs live content to answer a specific user request. Blocking it means those agents cannot read your pages when a user asks them to.
How do I block Amazon-Bedrock-AgentCore in robots.txt?
Add these lines to /robots.txt:
User-agent: Amazon-Bedrock-AgentCore
Disallow: /
To restrict only part of your site, disallow specific paths and allow the rest.