Index of every page on this site: llms.txt
All skills
aws avatar

/amazon-evs-agent-skill

@33a173e
Run it yourself

Guide Amazon EVS deployments with the EVS Deployment Orchestrator (EDO): prepare and validate a plan, run approved actions with the user's credentials, and monitor or recover the deployment. Support existing blueprints, readiness checks, access, host changes, and teardown. Also answer factual Amazon EVS questions from official documentation.

  • 13 files
  • 61.7 KB
  • Updated 4 days ago
  • GitHub
Use this Skill: https://skilld.dev/gh/aws/solutions-for-amazon-evs/amazon-evs-agent-skill

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesedoplan.md

≈1.5k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Validate the configuration and present the plan

Read the matching README's blueprint/reference guidance, "Choosing the ESXi build", "Check the blueprint", quota check, "Other checks before launch", upload/launch instructions, and "Teardown" with "What's left after teardown". These supply validation rules and commands. State what teardown deletes, keeps, and keeps billing only from that README section, in discovery as well as in the plan.

Prepare review files

Use a dedicated review directory. Write the blueprint, launch parameters, and plan even while blockers remain: blockers stop the launch, not the review files. If the user supplied a blueprint, validate it and work on a copy only when changes are needed. Retain valid choices and optional fields; resolve missing or incompatible fields. Otherwise build a blueprint from the release reference, the user's answers, and the starting configuration in discover.md, including every section the release validator requires, even when disabled. Label each value as requested, discovered, or default. Prepare launch-parameters.json from the matching template and launch instructions.

Run the README's structure validator and manual checks (except the OVA content check, which the user runs), ESXi/artifact checks, quota tool with the actual AZ and BYO arguments, and applicable account/name checks for this configuration. Reuse still-applicable evidence; after an edit, repeat affected local checks before account checks that consume the blueprint. Run documented checks rather than writing new validators or quota arithmetic.

Also check what the documented tools may miss:

  • The ESXi build EDO would select matches the OVA version, for supplied blueprints too; pin evs.esx_version when they differ.
  • Blueprint compatibility explicitly covers the selected runner release through requires.edo when supported; otherwise state the limitation. Check unique DNS labels and sizing values against the release reference.
  • Proposed S3 keys and template-derived key-pair names do not collide with existing resources; never upload over an existing object without the user's agreement. Optional/billable choices match the requested scope.
  • Compare a supplied artifact checksum. Warn that EDO doesn't check the OVA at launch, so a wrong file fails hours later at VCF bringup, and give the README's OVA check for the user to run; don't run it yourself.
  • The confirmed names are unused: stacks, EVS environments, and a Route 53 hosted zone named dns.fqdn. Say the hosted-zone check is there because EDO creates a new private zone with that name in this account for the VCF hostnames, and that it doesn't use DNS the user runs elsewhere.
  • The release ref exists publicly (git ls-remote); otherwise launch is blocked. A template of up to 51,200 bytes is validated read-only now. A larger one can only be validated after an S3 upload, so before approval report its size only, and list "create the bucket (if needed), upload the template, validate it" as numbered plan steps that run after approval, then launch with --template-url.
  • Launch parameters carry every selected value whose omission changes the configuration; do not rely on example-command defaults.
  • evs.terms_accepted reflects the user's own confirmation in this conversation. Never copy true from a reference, example, or CI blueprint; keep it false until the user confirms the terms.

Record results and their evidence. For each gap, identify the responsible person/action and whether it blocks launch. Planned setup is not a completed prerequisite; a quota request is not granted headroom. Required failed/unknown checks and unresolved user requirements remain launch blockers.

Present the approval plan

Re-read formats.md's Plan block now; the reply must copy it line for line. Write deployment-plan.md and initialize the progress record described in core.md. Present a readable summary of:

  • Target account/principal/profile, Region/AZ, release/commit, and goal.
  • The configuration, including hosts, software versions, network/addressing, optional components, access, artifacts, and secret references.
  • Verified checks, warnings, missing user actions, and launch blockers.
  • The EVS terms: quote the current termsAccepted description from the CreateEnvironment API Reference with that link and the resulting physical core count, and ask the user to confirm it themselves unless they already did so in this conversation. A true in a supplied blueprint still needs this confirmation, and a change to host count or instance type resets it to false until the user confirms the new core count. Record it in the progress record; without it, launch is blocked.
  • The exact sequence of proposed AWS changes, resource names, permissions, resolved commands, billing implications, and whether each can be undone (in words; the teardown command goes in the plan's Teardown line, outside the steps being approved).
  • Monitoring capability, expected duration, completion evidence, and resources retained or still billable after the intended cleanup scope.

Use the matching README and its official sources for technical/cost claims. Separate agent actions from customer tasks. For identifiers produced by an approved action, describe the output binding used by later commands. Show proposed defaults and meaningful changes to supplied configuration.

Present it and request agreement in the formats in formats.md. When blockers remain, make clear which named preparation actions can run and why launch must wait. Preserve the reviewed files and approval in the shared record. Continue with run.md for an approved deployment; otherwise hand over the requested files or readiness report without AWS changes. If the user declines or defers, change nothing, and use the decline format in formats.md.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 33a173e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 4 days ago
What it can do
Runs commands
metadata
{
  "version": "1.1.0"
}
All 1 allowed tools
Bash(aws sts get-caller-identity *) Bash(aws evs get-versions *) Bash(aws evs list-environments *) Bash(aws evs list-environment-hosts *) Bash(aws evs get-environment *) Bash(aws ec2 describe-instance-type-offerings *) Bash(aws ec2 describe-vpcs *) Bash(aws ec2 describe-subnets *) Bash(aws ec2 describe-internet-gateways *) Bash(aws ec2 describe-route-tables *) Bash(aws ec2 describe-key-pairs *) Bash(aws ec2 describe-availability-zones *) Bash(aws support describe-severity-levels *) Bash(aws secretsmanager list-secrets *) Bash(aws secretsmanager describe-secret *) Bash(aws s3api list-buckets *) Bash(aws s3api get-bucket-location *) Bash(aws s3api head-bucket *) Bash(aws s3api list-objects-v2 *) Bash(aws s3 ls *) Bash(aws sns list-topics *) Bash(aws route53 list-hosted-zones-by-name *) Bash(aws cloudformation describe-stacks *) Bash(aws cloudformation validate-template *) Bash(aws service-quotas get-service-quota *) Bash(aws service-quotas list-service-quotas *) Bash(aws fsx describe-file-systems *) Bash(aws fsx describe-volumes *) Bash(aws fsx describe-storage-virtual-machines *) Bash(aws ec2 describe-security-groups *) Bash(git ls-remote *) Bash(git rev-parse *) Bash(git status *) Bash(aws cloudformation describe-stack-resource *) Bash(aws cloudformation get-template *) Bash(aws cloudformation list-stacks *) Bash(aws ec2 describe-instance-types *) Bash(aws ec2 describe-instances *) Bash(aws ec2 describe-nat-gateways *) Bash(aws ec2 describe-managed-prefix-lists *) Bash(aws ec2 describe-tags *) Bash(aws logs filter-log-events *) Bash(aws logs tail *) Bash(aws route53 get-hosted-zone *) Bash(aws route53 list-resource-record-sets *) Bash(aws service-quotas list-requested-service-quota-change-history *) Bash(aws ssm describe-instance-information *)
Other metadata
compatibility
Q&A needs network access to https://docs.aws.amazon.com and a web fetch tool (or curl). Deployment uses AWS CLI v2 or the AWS MCP server for read-only checks, and also needs git, python3 3.10 or later (with boto3 and pyyaml), AWS credentials for the target account, and network access to AWS and GitHub.

README badge

README badge for aws/solutions-for-amazon-evs