> ## Documentation Index
> Fetch the complete documentation index at: https://docs.runlayer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Infrastructure Skill

> Use your local AI agent to prepare Runlayer ECS or EKS deployments and upgrades with current public documentation

The Runlayer Infrastructure Upgrader helps your local AI agent prepare a new
deployment or upgrade an existing installation. It reads current public deployment
and release docs, asks about your environment, and produces configuration for review.
This skill covers AWS ECS and EKS. GKE/GCP deployments require a separate workflow;
see [Kubernetes deployment](/deployment/kubernetes) for public guidance.

[Download v0.3.0](https://downloads.runlayer.com/skills/runlayer-infra-upgrader-0.3.0.zip)
· [SHA-256 checksum](https://downloads.runlayer.com/skills/runlayer-infra-upgrader-0.3.0.zip.sha256)

## Install

Extract the ZIP and keep the `runlayer-infra-upgrader` folder together. Extraction
alone does not register the skill with your agent. Choose one installation method:

| Agent / method | Location and invocation |
| - | - |
| Claude Code, this repository | Place the extracted folder at `.claude/skills/runlayer-infra-upgrader/`, then invoke `/runlayer-infra-upgrader`. |
| Claude Code, all local projects | Place it at `~/.claude/skills/runlayer-infra-upgrader/`, then invoke `/runlayer-infra-upgrader`. |
| Other local agents | Use the agent's documented skill installation directory, or give it the absolute path to the extracted `SKILL.md`. |

Check for an existing installation before copying; replace it deliberately rather
than leaving multiple versions. Claude Code's [skill locations](https://code.claude.com/docs/en/skills#choose-where-skills-load)
are separate from this repository's `.agents` source and module-bundle paths.
Do not assume `.agents/runlayer-infra-upgrader/` will be discovered automatically.

For an agent with local file access, this explicit-path prompt works without
automatic skill discovery (replace `/path/to` with the actual extracted location):

```text theme={null}
Read /path/to/runlayer-infra-upgrader/SKILL.md.
Help me prepare a new Runlayer ECS deployment in this repository.
Use current public docs and ask for missing environment decisions.
Generate and validate configuration; stop before applying infrastructure.
```

For an upgrade, replace the request with your deployment type and current/target
versions. For EKS, the skill uses the Runlayer Operator and `RunlayerInstance`.
It identifies legacy installations before proposing a migration.

New ECS Terraform module archives also include this skill under
`.agents/skills/runlayer-infra-upgrader/`. Older archives may contain the previous
skill under `.claude/skills/`; use this standalone download for the revised workflow.
If you installed the previous skill globally, replace that installation to avoid
loading both copies. Installation paths vary by agent.

The skill needs no Runlayer MCP connection or access to Runlayer's source repository.
Your agent needs HTTPS access to public docs and local file access to generate files.
Validation also needs the selected platform's tools, artifact access and your cloud
identity. Your agent's data handling and permission settings still apply.

## Prepare

Have your deployment type, account/region, network and DNS ownership, state/backend
conventions, availability requirements and existing repository ready. For upgrades,
also identify installed versions and customizations. You can start with missing
information; the agent will label unresolved values and access requirements.

Get onboarding inputs through [Runlayer-provided inputs](/deployment/runlayer-provided-inputs).
Deliver secret values through your secret manager or environment, never the chat.
This includes the Distribution reader credential and its registration requirements.

## What the skill does

* Discovers guidance through [llms.txt](https://docs.runlayer.com/llms.txt).
* Recommends latest published releases for new setups, respects explicit pins and
  checks compatibility against the selected module or chart.
* Prepares ECS Terraform or EKS infrastructure/operator configuration using the
  current public examples, rather than a bundled snapshot of deployment defaults.
* Maps upstream changes to customized installations for upgrades.
* Reports generated files, source URLs, chosen versions, validation results and
  unresolved prerequisites in a deployment handoff.

The download includes workflow instructions and a license, not a copy of the
deployment manuals. If current documentation cannot be retrieved, the agent can
prepare a draft but must identify what it could not verify.

Applying infrastructure, changing state or migrating controllers requires explicit
authorization. Formatting, rendering or a successful plan does not establish runtime
health. Follow [ECS deployment](/deployment/terraform), [Runlayer Operator](/deployment/runlayer-operator)
and [Updates](/operations/updates) for deployment and verification.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.