- Complete Quickstart to understand basic operations
- Ensure you have LLM Providers configured
- Have S3 credentials and access to an S3 bucket
What S3 Storage Does
- Ingest from S3: Pass
s3://...paths tocognee.add()to load data directly from S3 - Store Cognee data on S3: Set your data/system roots to S3 URLs to keep all files on S3
- S3-compatible: Works with MinIO and other S3-compatible services
Prerequisites
Install with AWS extra if needed (boto3/s3fs) and add credentials to.env:
Option A: Ingest from S3
Pass S3 URIs (files or prefixes) directly toremember(). Directories/prefixes expand to files when credentials are set.
Legacy guide
Legacy guide
s3:// URI. remember() expands prefixes, reads the S3 objects, and builds retrieval-ready memory for each target dataset.
This simple example uses S3 paths for demonstration. In practice, you can mix S3 files with local files, use dataset scoping, and apply custom loaders. The same
remember() flow works with S3 paths.Option B: Store Cognee Data on S3
Keep Cognee’s generated files (text copies, system files) on S3 by pointing roots to S3 URLs. Add this to your.env:
Cognee chooses S3 storage when roots start with
s3:// (or when STORAGE_BACKEND=s3 and both roots are S3 URLs). Credentials from .env are required.Core Concepts
Understand knowledge graph fundamentals
Setup Configuration
Configure providers and databases
API Reference
Explore API endpoints