infisical/ai-skills

infisical-self-host

Deploy and operate Infisical self-hosted instances with Docker, Docker Compose, and Kubernetes.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/infisical/ai-skills --skill infisical-self-host

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

Infisical Self-Hosted Deployment

This skill guides you through deploying, configuring, and operating Infisical in self-hosted environments. Whether you are running Infisical on Docker, Docker Compose, or Kubernetes, this resource covers essential setup, security hardening, scaling, and maintenance patterns.

Not this skill

If the user wants...Use
To deploy the Kubernetes Operator (also a Helm chart, different thing)infisical-kubernetes-operator
To reach a private resource from Infisicalinfisical-gateway
To configure SSO or SCIM on their instanceinfisical-sso
Roles, permissions, audit log streamsinfisical-access-control
To use Infisical once it is runninginfisical-setup
An external KMS or HSM backing the root keyinfisical-kms

The Helm confusion is worth pre-empting: the secrets-operator chart installs the operator; this skill covers the chart that installs the platform. Both come from the same Cloudsmith repo.

Guiding Principles

  1. ENCRYPTION_KEY is Critical: This key encrypts all secrets at rest and cannot be recovered if lost. Back it up and rotate it carefully following Infisical's rotation procedures.
  • Standard deployments: a random 16-byte hex string — openssl rand -hex 16
  • FIPS-enabled deployments: a 256-bit base64 key instead — openssl rand -base64 32
  1. AUTH_SECRET is Required: This key is used for session and JWT signing. It is 32 bytes (base64), generated with openssl rand -base64 32, and must be stable across restarts.
  1. Database Requirements: PostgreSQL is the only supported database. Use 14+ for compatibility; Infisical is extensively tested on 16. Always backup your database before upgrading Infisical. Schema migrations run automatically on boot (since v0.111.0-postgres).
  1. Redis is a hard dependency, not just a cache: Beyond caching it holds the background job queue, distributed locks, cross-instance coordination state, and rate-limit counters. The instance will not start unless one of `REDIS_URL`, `REDIS_SENTINEL_HOSTS`, or `REDIS_CLUSTER_HOSTS` is set, and a running instance is degraded while Redis is unreachable.
  • Use Redis 6.x or 7.x; at least 6.2 is advised
  • All three topologies are supported: standalone, Sentinel, and Cluster
  • Active-passive is recommended. Active-active has not been tested and may behave in undocumented ways
  • Set the eviction policy to `noeviction`. This is required, not a tuning suggestion — evicting keys under memory pressure would silently drop queued work
  • Enable persistence (AOF, or at minimum RDB snapshots) and back Redis up. Pending secret rotations, syncs, and webhook deliveries live there; a Redis that comes back empty loses them
  • Give Redis the same availability target as the app instances — an unreplicated Redis is a single point of failure for the whole deployment
  1. Stateless Architecture: Infisical is stateless. Scale horizontally by adding more replicas. All state lives in PostgreSQL and Redis. Each instance needs no more than 2–4 CPU cores and 4–8 GB memory; add containers rather than growing one.
  1. FIPS Compliance: Infisical is compliant with FIPS 140-3. Deploy the separate `infisical/infisical-fips` Docker image (an Enterprise-only image, not a tag on the standard repo) and set FIPS_ENABLED=true. Remember the ENCRYPTION_KEY format changes to 256-bit base64 in FIPS mode.

Quick Start

  • Docker Standalone: Pull infisical/infisical:<version>, set environment variables, run on port 8080.
  • Docker Compose: Use docker-compose.prod.yml from the repository with PostgreSQL and Redis services.
  • Kubernetes: Deploy via Helm chart infisical-standalone-postgres from Cloudsmith registry with optional managed databases.

Reference Guides

Environment Variables

Complete reference for all configuration environment variables, including:

  • Required keys (ENCRYPTIONKEY, AUTHSECRET, database, Redis)
  • Database and replication setup
  • Redis with Sentinel support
  • SMTP configuration
  • OAuth/SSO providers
  • FIPS and telemetry settings
  • Security options

Docker Deployment

Docker and Docker Compose deployment patterns, including:

  • Standalone container setup
  • Docker Compose production stack
  • Image variants (standard and FIPS)
  • Production hardening with security capabilities and read-only filesystems
  • Health checks

Kubernetes Deployment

Kubernetes and Helm deployment guide, including:

  • Helm chart installation and configuration
  • Secret creation and management
  • Optional PostgreSQL and Redis (Bitnami charts)
  • Pod security and RBAC
  • Networking policies and Ingress/TLS

Scaling and High Availability

Production scaling patterns and HA architecture, including:

  • Horizontal scaling (adding replicas)
  • Sizing guidelines for Infisical, PostgreSQL, and Redis
  • Database read replicas
  • Redis Sentinel for HA
  • Backup and upgrade procedures
  • License server firewall rules

Verwandte Aufgaben

aus demselben Repository

Weitere Skills

Alle Skills
infisical
Community

infisical-access-control

Guide for Infisical access control and governance — org and project roles, custom roles with subject/action permissions, granular secret permissions that separate describing a secret from reading its value, attribute-based access control (ABAC) driven by user metadata and machine identity attributes, additional privileges, assume-privilege, temporary (time-bound) access, access requests, change-approval and access-approval policies, and audit logs including streaming to Splunk, Datadog, Azure, C

Installationen / 1h
1
GitHub Stars
41
Aktualisiert
11. Nov.
infisical
Community

infisical-agent

Guide for configuring the Infisical Agent — a client daemon that manages token lifecycle and renders secrets via Go templates without modifying application code. Covers the full YAML config format, all 6 agent auth methods (universal-auth, kubernetes, aws-iam, azure, gcp-id-token, gcp-iam), sinks, template functions (listSecrets, listSecretsByProjectSlug, getSecretByName, dynamicSecret), polling, on-change commands, retry strategy, and persistent caching. Use this skill when someone asks about:

Installationen / 1h
1
GitHub Stars
41
Aktualisiert
11. Nov.
infisical
Community

infisical-api

Interact with the Infisical REST API to manage secrets, projects, environments, machine identities, and more. Supports secret CRUD operations, machine identity authentication, pagination, and rate limiting on cloud deployments. Not for the CLI/SDKs (infisical-setup), KMS crypto endpoints (infisical-kms), certificate endpoints (infisical-pki), or human SSO login (infisical-sso).

Installationen / 1h
1
GitHub Stars
41
Aktualisiert
11. Nov.
infisical
Community

infisical-app-connections

Guide for creating and managing Infisical App Connections — the reusable authenticated links between Infisical and third-party services that Secret Syncs, Secret Rotations, PKI certificate authorities, PKI Syncs, and Secret Scanning data sources all depend on. Covers all 83 connection types and their exact auth methods (AWS assume-role vs access-key, GitHub OAuth vs GitHub App vs PAT, Azure OAuth vs client-secret vs certificate, GCP service account impersonation, and more), platform-managed cred

Installationen / 1h
1
GitHub Stars
41
Aktualisiert
11. Nov.