Bot intelligence record

Amazon Kendra

Review first

Use the amazon-kendra- identifier to separate Amazon security scanning or verification traffic from normal visitor requests in server logs.

Security Verified Bot Confidence: Medium Verified: Yes robots.txt: No
Operator
Amazon
Family
Amazon
Type
Security
Source type
Verified Directory
Last checked
2026-05-20

User-Agent Pattern

Amazon
amazon-kendra-
Verification note

User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.

Robots.txt Snippet

Click snippet to copy
User-agent: amazon-kendra- Disallow: /

Click the snippet to copy it, or highlight the text manually.

Handling Guidance

Depends

Use this record as bot intelligence, then verify the request source and behavior before allowing, blocking, or rate limiting.

Security scanning, malware checks, abuse prevention, compliance review, or vulnerability monitoring.

Record Details

Structured data
Operator
Amazon
Family
Amazon
Type
Security
Purpose
Security
Identity type
Verified Bot
Confidence
Medium
Last verified
2026-04-01
Last checked
2026-05-20
Source type
Verified Directory
Verification
Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
Spoofing risk
User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.

Notes

Amazon Kendra is listed in the Botcrawl directory as a security scanner from Amazon. The primary identifier for log review is amazon-kendra-.

Identification

  • User-agent pattern: amazon-kendra-
  • Family: Amazon
  • Type: Security
  • Kind: Scanner

Common use

Security scanning, malware checks, abuse prevention, compliance review, or vulnerability monitoring.

Verification and handling

Confirm the user-agent against server logs and use published operator documentation, IP ranges, reverse DNS, or other trust signals when available.

Directory guidance marks the risk level as Neutral and the blocking decision as Depends. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.

Robots.txt handling: No.

Evidence and Source

  • Validate the identifying user-agent or signature against the operator documentation before creating hard allow rules.
  • Match `amazon-kendra-` as a case-insensitive substring in HTTP user-agent logs. Review bot_aliases for alternate names or product labels. Use bot_http_agent for full user-agent examples when the client sends a longer browser-like string. Do not treat a user-agent match alone as proof of identity for allow-listing.
  • Security scanning, malware checks, abuse prevention, compliance review, or vulnerability monitoring.
  • User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.

Monitor This Bot In Edge

Botcrawl Edge

Use Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.