Amazon ELB
Amazon ELB is a developer or operator tool operated by Amazon. It runs on behalf of a site owner for monitoring, uptime checks, performance audits, or internal QA.
If you run the site, you are probably the customer of whoever is running this agent. Blocking it would hide your own monitoring data from yourself.
If you are an end-user surprised to see this in your logs, it is almost always something a third-party SaaS is doing on behalf of someone who manages your site.
See Amazon ELB on your own site
Match the User-Agent header on incoming requests against the pattern below.
regex
Verify by IP
For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.
Renders JavaScript
No
IP verification
Published IP ranges
Crawl frequency
Scheduled probes
Honors robots.txt
Yes
Honors Crawl-delay
Varies
Amazon runs 38 bots in total. Each one is a separate user-agent so you can allow or block them independently.
Live-Fetch AI
11- Amzn-User
- Amazon Bedrock AgentCore Browser (AP Northeast)
- Amazon Bedrock AgentCore Browser (AP South)
- Amazon Bedrock AgentCore Browser (AP Southeast 1)
- Amazon Bedrock AgentCore Browser (AP Southeast)
- Amazon Bedrock AgentCore Browser (EU Central 1)
- Amazon Bedrock AgentCore Browser (EU West 1)
- Amazon Bedrock AgentCore Browser (US East 1)
- Amazon Bedrock AgentCore Browser (US East 2)
- Amazon Bedrock AgentCore Browser (US West 2)
- Amazon Buy For Me
Training Crawler
7Brand Intelligence
3Agentic Browser
3AI Search Index
2Generic Crawler
2DevOps & Monitoring
2- Amazon ELBYou are here
- Amazon Route53 Health Check
Shopping Bot
2Search Engine
1Task Automation
1Ad Verification
1Ads Network Bot
1Link Unfurler
1AI Coding Tool
1Should I let Amazon ELB through?
In most cases, yes. Almost always run by you or your vendor. Blocking hides your own monitoring data. If volume gets noisy, rate-limit it before you block it outright.
Does blocking Amazon ELB affect my Google rankings?
No. Amazon ELB is not a search-engine crawler. Your ranking on Google or Bing is unaffected by what you do here.
How do I confirm a request is really from Amazon ELB?
Two checks. The User-Agent header should match a known Amazon ELB string, and the request's source IP should fall inside Amazon's published ranges. The User-Agent alone is trivially spoofable, so the IP check is what gives you confidence. Amazon publishes the ranges so you can validate at the CDN or edge.
What's the best way to understand what Amazon ELB is doing on my site?
Look at which URLs it hits, how often, and what time of day. The request pattern usually tells you whether it's building an index, watching for a specific change, or trying to pull data in bulk. The User-Agent name alone rarely tells the full story.
How is Amazon ELB different from Amazon's other bots?
Amazon splits work across multiple user-agents so site owners can decide on each one independently. Training crawlers, live-fetch agents, search indexers, and agentic browsers each get their own name. Worth scanning the rest of the Amazon family above to see which ones actually matter for your site.
What's the cleanest way to control Amazon ELB?
Two layers. Robots.txt for the polite crawlers that read it, and rules at your CDN or edge for the ones that don't. Rankly's Agent Experience handles both from a single config, so you can allow, block, rate-limit, or serve a stripped-down version per bot. Agent Analytics handles the observation half so you know which bots are actually worth a rule.
Verify everything above against the operator's own documentation.