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.
One of the first steps towards building a production-ready Pinecone index is configuring your project correctly.
Consider how best to manage the API keys associated with your production project. In order to make calls to the Pinecone API, you must provide a valid API key for the relevant Pinecone project.
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.
Before moving your project to production, make sure that you are targeting indexes by host rather than by name.
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.
Use Pinecone’s security features to protect your production data:
Before serving production workloads, identify ways to increase search relevance, increase throughput, and decrease latency.
Prepare to monitor the production performance and availability of your indexes.
Use Pinecone in CI/CD to safely test changes before deploying them to production.
If you need help, contact Support, or talk to the Pinecone community. Ensure that your plan tier matches the support and availability SLAs you need. This may require you to upgrade to Enterprise.
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.
One of the first steps towards building a production-ready Pinecone index is configuring your project correctly.
Consider how best to manage the API keys associated with your production project. In order to make calls to the Pinecone API, you must provide a valid API key for the relevant Pinecone project.
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.
Before moving your project to production, make sure that you are targeting indexes by host rather than by name.
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.
Use Pinecone’s security features to protect your production data:
Before serving production workloads, identify ways to increase search relevance, increase throughput, and decrease latency.
Prepare to monitor the production performance and availability of your indexes.
Use Pinecone in CI/CD to safely test changes before deploying them to production.
If you need help, contact Support, or talk to the Pinecone community. Ensure that your plan tier matches the support and availability SLAs you need. This may require you to upgrade to Enterprise.