Secure API Key Vault, Quota Management, and Rotation

1. Overview & Technical Architecture#

API keys for external cloud providers are stored with AES-256 encryption at rest and in memory.

1. Key Vault Operations#

1. Open Settings → Technical → Parameters → System Parameters.
2. Encrypted keys are tagged with prefix muk_ai.secret.*.
3. Keys are never logged in plain text or rendered in client-side HTML DOM trees.

2. Automated Key Rotation Runbook#

Every 90 days, the security cron (muk_ai.ir_cron_rotate_api_keys) alerts administrators to deposit refreshed keys into the secondary pool slot before retiring the primary key.

2. Prerequisites & Infrastructure Requirements#

• Runtime Environment: Python 3.12+, PostgreSQL 16 with pgvector extension.
• Security Access Group: Ashewa AI / Administrator (Technical ID: muk_ai.group_ai_manager)
• Hardware Profile: Minimum 16 GB System RAM (CPU inference) or NVIDIA GPU with 8+ GB VRAM.

3. Step-by-Step Configuration & Verification#

Step 1: Navigating to Model Management#

1. Access your SmartERP instance at https://smarterp.et/odoo.
2. Open Settings → Technical → Ashewa AI → Model Registry.
3. Select the custom model profile.

{screenshot:80-api-key-governance-and-quota-management-step1-navigation}

Step 2: Testing Endpoint Health & Response Verification#

1. Click the Run Diagnostic Health Check button.
2. Verify token generation speed (tokens/sec) and latency benchmarks.
3. Review sample response in the diagnostic console.

{screenshot:80-api-key-governance-and-quota-management-step2-verification}

4. Advanced Configuration Points#

• Automated Tasks: muk_ai.ir_cron_model_health_monitor runs every 15 minutes.
• Multi-Tenant Boundaries: Custom model fine-tuning adapters are strictly segregated per tenant database.

5. Comprehensive Troubleshooting Matrix#