input-configurations
Input template configuration for Elastic integrations. Covers agent stream templates (agent/stream/.yml.hbs) for all non-CEL input types: HTTPJSON, AWS S3, CloudWatch, Azure Blob, Azure EventHub, GCS, GCP Pub/Sub, TCP, UDP, HTTP Endpoint, Filestream, Logfile, Journald, Winlog, and WebSocket. Also covers Federated Identity (Cloud Connectors) for agentless AWS integrations, including the auth.aws / usecloudconnectors block on CEL stream templates. For CEL program logic, use the cel-programs skill.
- Installs
- 504
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/elastic/integration-skills --skill input-configurations- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads input-configurations automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
input-configurations
When to use
Load this skill whenever tasks include:
- building, modifying, or reviewing
agent/stream/*.yml.hbstemplates for non-CEL input types - configuring request, response, pagination, cursor, or authentication blocks in HTTPJSON templates
- wiring up cloud storage inputs (AWS S3, GCS, Azure Blob, Azure EventHub)
- setting up network inputs (TCP, UDP, HTTP Endpoint, WebSocket)
- configuring file-based inputs (Filestream, Logfile, Journald, Winlog)
- enabling Federated Identity (Cloud Connectors) on an AWS integration package
When not to use
Do not use this skill as the primary guide for:
- CEL program development (
cel-programs) -- CEL program structure, state model, and mito workflow. Exception: theauth.aws/use_cloud_connectorstemplate block for Federated Identity is owned here viareferences/federated-identity-aws.md - ingest pipeline processor design (
ingest-pipelines) - field mappings and ECS compliance (
ecs-field-mappings) var_groups/provider_permissionsschema andformat_versionfloors alone (package-spec) -- use this skill for the end-to-end federation procedure that applies them
Mandatory first read
Always load references/common-input-patterns.md first. It covers patterns that apply to every input type (tags, processors passthrough, variable conventions, forwarded/publisher_pipeline.disable_host coupling). These patterns are prerequisites for all type-specific guides.
Type routing table
Detect the input type from the filename pattern in agent/stream/ or from the data stream manifest input: field, then load the matching guide.
| Input type | Filename pattern | Guide |
|---|---|---|
| HTTPJSON | httpjson.yml.hbs | references/httpjson-guide.md |
| AWS S3 | aws-s3.yml.hbs | references/aws-s3-guide.md |
| CloudWatch | aws-cloudwatch.yml.hbs | references/aws-cloudwatch-guide.md |
| Azure Blob Storage | azure-blob-storage.yml.hbs | references/azure-blob-storage-guide.md |
| Azure Event Hub | azure-eventhub.yml.hbs | references/azure-eventhub-guide.md |
| GCS | gcs.yml.hbs | references/gcs-guide.md |
| GCP Pub/Sub | gcp-pubsub.yml.hbs | references/gcp-pubsub-guide.md |
| TCP | tcp.yml.hbs | references/tcp-udp-guide.md |
| UDP | udp.yml.hbs | references/tcp-udp-guide.md |
| HTTP Endpoint | http_endpoint.yml.hbs | references/http-endpoint-guide.md |
| Filestream | filestream.yml.hbs | references/filestream-logfile-guide.md |
| Logfile | log.yml.hbs | references/filestream-logfile-guide.md |
| Journald | journald.yml.hbs | references/journald-guide.md |
| Winlog | winlog.yml.hbs | references/winlog-guide.md |
| WebSocket | websocket.yml.hbs | references/websocket-guide.md |
Load only the guide for the detected input type, not all guides.
For Federated Identity tasks (any eligible input type, including cel), load
references/federated-identity-aws.md regardless of which input type is
involved.
Handoff
- For CEL program logic, hand off to the
cel-programsskill. Keep this skill loaded for Federated Identityauth.aws/use_cloud_connectorsedits oncel.yml.hbs. - For manifest schema (
var_groups,provider_permissions,format_version/ conditions floors), hand off to thepackage-specskill (references/var-groups-and-provider-permissions.md). - For pipeline issues discovered while reviewing input templates, hand off to the
ingest-pipelinesskill. - For field mapping issues found in template variable wiring, hand off to the
ecs-field-mappingsskill.
References
references/common-input-patterns.md-- tags, processors passthrough, variable conventions, review flags (applies to ALL input types)references/httpjson-guide.md-- HTTPJSON template syntax, structure, validation rules, pagination patterns, authentication, cursor persistencereferences/aws-s3-guide.md-- S3 bucket/SQS notification collectionreferences/aws-cloudwatch-guide.md-- CloudWatch log group collectionreferences/azure-blob-storage-guide.md-- Azure Blob Storage collectionreferences/azure-eventhub-guide.md-- Azure Event Hub collectionreferences/gcs-guide.md-- Google Cloud Storage collectionreferences/gcp-pubsub-guide.md-- GCP Pub/Sub collectionreferences/tcp-udp-guide.md-- TCP and UDP (syslog-style) listenersreferences/http-endpoint-guide.md-- HTTP Endpoint (webhook receiver)references/filestream-logfile-guide.md-- Filestream and legacy Logfile inputsreferences/journald-guide.md-- Journald collectionreferences/winlog-guide.md-- Windows Event Log collectionreferences/websocket-guide.md-- WebSocket streaming (may embed CEL)references/federated-identity-aws.md-- AWS Federated Identity procedure: input classification, federation vars,auth.aws/use_cloud_connectors, input gating (schema lives inpackage-spec)
FAQ
What does the input-configurations skill do?
Input template configuration for Elastic integrations. Covers agent stream templates (agent/stream/.yml.hbs) for all non-CEL input types: HTTPJSON, AWS S3, CloudWatch, Azure Blob, Azure EventHub, GCS, GCP Pub/Sub, TCP, UDP, HTTP Endpoint, Filestream, Logfile, Journald, Winlog, and WebSocket. Also covers Federated Identity (Cloud Connectors) for agentless AWS integrations, including the auth.aws / usecloudconnectors block on CEL stream templates. For CEL program logic, use the cel-programs skill.
How do I install input-configurations?
Run npx skills add https://github.com/elastic/integration-skills --skill input-configurations in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/input-configurations/ (personal) or .claude/skills/input-configurations/ (project).
Which AI agents can use input-configurations?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is input-configurations safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains input-configurations?
It is published by elastic in elastic/integration-skills. It has 504 recorded installs.
More from elastic/integration-skills
ingest-pipelines
elastic/integration-skills
Use when designing or modifying Elasticsearch ingest pipelines, including single-path parsing, branching logic, sub-pipelines, enrichment processors, and robust onfailure handling.
integration-testing
elastic/integration-skills
Use when creating, running, or debugging elastic-package tests — pipeline fixture authoring and expected output, system tests with mock API wiring, and script tests for failure paths and upgrades. Load the reference file for the test type you are working on.
research-integration
elastic/integration-skills
Research a vendor, product, or feature to collect all information needed before building an Elastic integration. Investigates data collection methods, API or log documentation, sample data formats, field schemas, ECS mapping candidates, and configuration requirements. Outputs a structured research brief to researchresults/ /. Invoke manually with /research-integration.
dashboard-review
elastic/integration-skills
Use when reviewing dashboard JSON changes in a PR or branch. Extracts structured descriptions with kbdash, compares before/after, and checks guideline compliance.
ecs-field-mappings
elastic/integration-skills
Use when defining field mappings for data streams, populating ecs.yml with ECS field references, selecting ECS categorization values, choosing custom field types, or troubleshooting mapping validation failures.
anonymize-logs
elastic/integration-skills
Anonymize and sanitize customer-provided log files. Performs a line-by-line review and replaces all sensitive values inline, preserving log structure and format exactly — never reformats, re-indents, or restructures content. Use when sanitizing customer logs, sample events, or test fixtures. Invoke manually with /anonymize-logs.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.