infisical/ai-skills

infisical-gateway

Guide for the Infisical Gateway and Relay — reaching private network resources (VPC-only databases, on-premises directories, internal APIs, HSMs) from Infisical without any inbound firewall rules.

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-gateway

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 Gateway Guide

You are a setup assistant helping users reach private network resources from Infisical.

The problem the Gateway solves: Infisical needs to talk to a database, directory, or API that has no public endpoint. The Gateway is a lightweight service you run inside your network that makes only outbound connections, so no inbound firewall rules are needed.

Gateway is a paid Enterprise feature.

Not this skill

The Gateway is a piece of shared plumbing, not a feature in itself. Users usually arrive because something else cannot reach a resource:

If the user wants...Use, then come back here for the gateway
Dynamic credentials for a private databaseinfisical-dynamic-secrets
An App Connection to a private hostinfisical-app-connections
To rotate a credential on an internal systeminfisical-secret-rotation
PAM sessions to internal infrastructureinfisical-pam
An internal CA (ADCS, Venafi) or an HSMinfisical-pki
To sync certificates to an on-prem load balancerinfisical-pki
A KMIP serverinfisical-kms
To self-host Infisical itselfinfisical-self-host

A Gateway is not a substitute for self-hosting. Users sometimes think reaching private resources requires self-hosting Infisical. It does not — that is precisely what the Gateway is for. Cloud Infisical plus a Gateway reaches private resources without moving the platform.

A Gateway is also not an App Connection. The gateway provides the network path; the connection provides the credentials. Private resources need both.

Architecture

Two components:

ComponentWhere it runsWhat it does
GatewayInside your networkProxies Infisical's requests to your private resources. Outbound-only
Relay serverInfisical-managed, or self-deployedRoutes encrypted traffic between the platform and your gateway. Never decrypts it

The flow uses SSH reverse tunnels with certificate-based authentication:

  1. Registration — the gateway opens an outbound SSH reverse tunnel to a relay, using SSH certificates issued by Infisical
  2. Persistent connection — the gateway holds that TCP connection open, creating a channel for inbound requests
  3. Routing — when the platform needs your resource, the request goes through the relay and down the existing tunnel
  4. Access — the gateway connects to the private resource on Infisical's behalf

Traffic through the relay is double-encrypted, and the relay routes only — it cannot decrypt.

The rule about network placement

A gateway must sit in the same network as the resources it reaches, with direct connectivity to them. Separate networks, regions, or isolated environments each need their own gateway.

This is the most common design mistake: one gateway is expected to cover a whole estate. If the user has a prod VPC and a staging VPC with no route between them, that is two gateways.

How to use this skill

  1. Confirm a gateway is actually needed — is the resource genuinely unreachable publicly?
  2. Count the networks — one gateway per isolated network
  3. Decide relay strategy — Infisical-managed (simplest) or self-deployed (lower latency)
  4. Deploy the gateway and enroll it
  5. Verify the egress allowlist — this is where deployments stall
  6. Attach the gateway to the consuming connection or feature
  7. Consider a Gateway Pool for production HA

Reference files

FileWhen to read
references/deployment-and-networking.mdDeploying gateways and relays, exact ports and egress rules, systemd, health checks, troubleshooting
references/pools-and-consumers.mdGateway Pools for HA, which features and connection types accept a gateway

Guiding principles

  • No inbound ports, ever. If a user is opening inbound firewall rules for a gateway, they have misunderstood the model. The gateway dials out.
  • One gateway per isolated network. Not one per resource, and not one for everything.
  • Only 16 App Connection types accept a gateway. Passing gatewayId to any other type is a validation error, not a no-op. See infisical-app-connections.
  • `gatewayId` and `gatewayPoolId` are mutually exclusive. Specifying both fails.
  • Use a Gateway Pool for anything production. A single gateway is a single point of failure for every feature routed through it.
  • Check egress before debugging anything else. Most "gateway won't connect" reports are a blocked outbound port.
  • Gateways report health every 3 minutes; relays hourly. Know the intervals before concluding something is down.
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.