Integration Checklist

A checklist to work through before taking a Sentinel integration to production.

1. Configuration

Manually set the required environment variables instead of relying on auto-generated secrets — see ENV Variables.
Configure Security Groups for public and API-only access.
Enable Autopilot for automatic traffic management, or set rate limits manually.
Generate new API keys (rotate any legacy keys if this replaces an existing setup).
Enable an IP resolver for geolocation/IP-based analytics.
Set up Storage Providers for secure handling of file uploads and database snapshots.
Review high-risk country settings if your users are in the US, China, Russia, Israel, or India.

Enforce TLS 1.2+ encryption.
Change default credentials (the root password) and enable MFA — see Users & Accounts.
Review user roles and permissions — ensure proper access controls, and enforce MFA for all users.
Restrict access to the application and administrative endpoints to whitelisted IPs/network masks — see APP_IP_WHITELIST in ENV Variables.

Schedule database snapshots, and test the restore process — see Backups & Recovery.
Configure automated volume backups.
Set monitoring alerts for downtime or abnormal activity, integrated with your external tooling — see Monitoring & Logging.

Validate API endpoints functionally with a tool like Postman or cURL.
Test compatibility across Chrome, Firefox, Safari, and mobile platforms.
Conduct load/stress testing to simulate traffic spikes — see Performance Tuning & Benchmarks.

Review compliance standards relevant to you (GDPR, HIPAA, etc.) — see Privacy Protection.
Update your privacy policy to document data flows and retention practices.
Document your integration steps as an internal runbook.
Establish SLAs with stakeholders regarding uptime and response times.

Get Started — the initial setup this checklist follows on from.
License — confirm a license is configured before relying on this in production.