AWS Lambda
AWS Lambda is a single-page fetcher operated by Amazon. It fetches one page (or a small set) when triggered by a user action, typically a link being shared on social media, a messaging app, or an RSS reader.
Volume tracks shares and clicks rather than crawl schedules. A trending link can produce a sudden spike, but AWS Lambda will not crawl the rest of your site.
Blocking it usually means the link previews on the corresponding platform stop showing your title, image, and description.
See AWS Lambda 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
Per user action
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
2Shopping Bot
2Search Engine
1Task Automation
1Ad Verification
1Ads Network Bot
1Link Unfurler
1- AWS LambdaYou are here
AI Coding Tool
1Should I let AWS Lambda through?
In most cases, yes. Fetchers power link previews and feed readers. Blocking breaks the user experience on social and messaging platforms. If volume gets noisy, rate-limit it before you block it outright.
Does blocking AWS Lambda affect my Google rankings?
No. AWS Lambda 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 AWS Lambda?
Two checks. The User-Agent header should match a known AWS Lambda 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 breaks if I block AWS Lambda?
Link previews, embeds, and unfurls on whatever surface AWS Lambda feeds will stop rendering. Users sharing your URLs into Amazon will see a bare link instead of a rich card. Usually that's the first thing people regret blocking.
How is AWS Lambda 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 AWS Lambda?
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.