Move to production
Production checklist
This page provides recommendations and best practices for preparing your Pinecone indexes for production, anticipating production issues, and enabling reliability and growth.
For high-scale use cases, consider using the Pinecone AWS Reference Architecture as a starting point, and read up on code best practices.
Prepare your project structure
One of the first steps towards building a production-ready Pinecone index is configuring your project correctly.- Consider creating a separate project for your development and production indexes, to allow for testing changes to your index before deploying them to production.
- Ensure that you have properly configured user access to the Pinecone console, so that only those users who need to access the production index can do so.
- Ensure that you have properly configured access through the API by managing API keys and using API key permissions.
Test your query results
Before you move your index to production, make sure that your index is returning accurate results in the context of your application by identifying the appropriate metrics for evaluating your results.Target indexes by host
Before moving your project to production, make sure that you are targeting indexes by host rather than by name.Backup up your indexes
In order to enable long-term retention, compliance archiving, and deployment of new indexes, consider backing up your production indexes by creating a backup or collection.Enforce security
Use Pinecone’s security features to protect your production data:- Data security
- Private endpoints
- Customer-managed encryption keys (CMEK)
- Authorization
- API keys
- Role-based access control (RBAC)
- Organization single sign-on (SSO)
- Audit logs
- Bring your own cloud