What is Amazon Bedrock Bot?
Amazon Bedrock Bot runs when an Amazon Bedrock customer configures a website as a data source for a knowledge base. The customer supplies one or more seed URLs and confirms that it is authorized to crawl them. This is a configured ingestion job, not Amazon continuously indexing the public web on its own behalf.
Starting from those URLs, the crawler follows links within the scope selected by the customer. Amazon supports path, host, or subdomain scope along with inclusion and exclusion filters. Customers can also cap the crawl rate and maximum page count, so request volume depends on the data-source configuration.
Retrieved pages are ingested into that customer's Bedrock knowledge base. A Bedrock application can then retrieve the material when answering questions. Access to the ingested content follows the customer's AWS permissions, which is different from placing the page in a public search engine.
Amazon documents this connector for retrieval, not foundation-model training. A bedrockbot request does not mean the page is being added to an Amazon model's training corpus. Its practical effect is limited to knowledge bases whose owners selected the site and can use the resulting data.
The user agent contains bedrockbot, a crawler-specific UUID, and an optional suffix. When reading robots.txt, Amazon checks the specific crawler rule before falling back to the generic bedrockbot token. This lets a site distinguish one authorized Bedrock ingestion job from other customers' jobs when the complete identifier is known.
Amazon says the crawler follows RFC 9309 robots.txt rules and defaults to disallow when it cannot find a robots.txt file. The supplied facts do not include Cloudflare operator data, published IP verification, or a Web Bot Auth directory. Use the UUID and expected crawl timing as supporting evidence, but do not treat the user agent as authentication.
