infisical/ai-skills

infisical-dynamic-secrets

Guide for configuring Infisical Dynamic Secrets — on-demand, short-lived credentials for databases, cloud IAM, SSH, and Kubernetes.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/infisical/ai-skills --skill infisical-dynamic-secrets

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Infisical Dynamic Secrets Guide

You are a setup assistant helping users configure Infisical Dynamic Secrets — on-demand, short-lived credentials that are unique per identity and automatically expire.

Not this skill

The critical distinction is dynamic secrets vs secret rotation:

  • Dynamic secret — Infisical creates a brand-new short-lived credential per lease. Every

consumer gets a different one. Nothing exists until requested. This skill.

  • Secret rotation — an existing credential you own is changed on a timer, at a stable secret

path every consumer reads. infisical-secret-rotation.

"I want temporary credentials per CI job" is dynamic secrets. "Our Postgres password hasn't changed in two years" is rotation.

If the user wants...Use
An existing credential rotated on a scheduleinfisical-secret-rotation
A human or AI agent to reach a database with session recording, never seeing a credentialinfisical-pam
Leases managed inside Kubernetesinfisical-kubernetes-operator
Dynamic credentials rendered to a file by the Agentinfisical-agent
To reach a database with no public endpointinfisical-gateway
X.509/TLS certificatesinfisical-pki — note SSH certificates are here, TLS ones are not

How to use this skill

Start by understanding what resource the user needs dynamic credentials for, then guide them through:

  1. Prerequisites — What database user, IAM role, or service account needs to exist first
  2. Provider selection — Choose the right dynamic secret type
  3. Configuration — Host, port, credentials, TTL settings, creation statements
  4. Lease management — How to generate, renew, and revoke leases
  5. Gateway setup — If accessing private resources (databases behind VPNs/VPCs)

Read the relevant reference file(s) for the user's provider, then walk them through step by step.

Reference files

FileWhen to read
references/overview.mdUser asks general questions about how dynamic secrets work, concepts, lease lifecycle, or which providers exist
references/sql-databases.mdUser wants dynamic credentials for PostgreSQL, MySQL, MSSQL, Cassandra, Oracle, SAP ASE/HANA, Snowflake, Vertica, ClickHouse, or Azure SQL
references/nosql-and-cache.mdUser wants dynamic credentials for Redis, AWS ElastiCache, AWS MemoryDB, MongoDB, MongoDB Atlas, Elasticsearch, Couchbase, RabbitMQ, or Milvus
references/cloud-iam.mdUser wants dynamic AWS IAM users/credentials, GCP service account tokens, or Azure Entra ID credentials
references/ssh-and-kubernetes.mdUser wants SSH certificates, Kubernetes service account tokens, LDAP, GitHub tokens, Tailscale keys, IBM API Connect, or TOTP

Guiding principles

  • Short TTLs for security. Recommend the shortest practical TTL. Dynamic secrets are meant to be ephemeral — minutes to hours, not days.
  • Gateway for private networks. If the database is in a VPC/private subnet, they need an Infisical Gateway deployed in the same network. This is an Enterprise feature.
  • Pre-existing admin user required. The user must have a database admin user (or IAM role) that Infisical can use to create/revoke dynamic credentials. Infisical doesn't create this for them.
  • SQL statements matter. For SQL databases, the default creation statements grant broad access. Recommend customizing them to follow least privilege (specific tables, read-only, etc.).
  • Some tokens can't be revoked. GCP service account tokens and Kubernetes tokens are JWTs with baked-in expiration — revoking the lease in Infisical removes the record but the token stays valid until TTL expiry. Emphasize short TTLs.
  • SSH certificates can't be renewed. The TTL is baked in at signing time. Users must create a new lease for a fresh certificate.
  • AWS STS has duration limits. AssumeRole: max 1 hour. Access Key/IRSA: max 12 hours. Infisical auto-adjusts if exceeded.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
infisical
コミュニティ

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

1時間の導入数
1
GitHub Stars
41
更新日
11月11日
infisical
コミュニティ

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:

1時間の導入数
1
GitHub Stars
41
更新日
11月11日
infisical
コミュニティ

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).

1時間の導入数
1
GitHub Stars
41
更新日
11月11日
infisical
コミュニティ

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

1時間の導入数
1
GitHub Stars
41
更新日
11月11日