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.

referencesknowledge.md

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

Sources for EVS questions

Answer the user's Amazon EVS question from the official AWS documentation listed below, following the rules in SKILL.md.

Scope

Q&A answers questions. It doesn't run AWS commands, call AWS APIs, or read or change anything in the user's account.

  • Preparing, deploying, monitoring, fixing, or tearing down an EDO environment: switch to the guided deployment workflow in SKILL.md and keep the user's inputs. For deployment without EDO, point to the User Guide's Getting started. Sizing inputs are in scope; calculating a real workload's host count isn't.
  • Running a command or looking at the user's resources outside a deployment task: say Q&A doesn't do that, and give the API or CLI reference page so the user can run it.

Sources

Start from these pages:

Page URL Use for
Documentation landing page https://docs.aws.amazon.com/evs/ Links to every source below
User Guide https://docs.aws.amazon.com/evs/latest/userguide/what-is-evs.html Concepts, architecture, setup and the deployment checklist, getting started, migration (HCX), managing environments (VCF subscriptions, VCF versions and EC2 instance types, lifecycle management, maintenance, secrets, hosts, connectors), Windows Server entitlements, the Custom Addon depot, security and IAM, resilience, other services (CloudFormation, FSx for NetApp ONTAP), troubleshooting, CloudTrail, service quotas, document history
API Reference https://docs.aws.amazon.com/evs/latest/APIReference/Welcome.html Actions, data types, service-specific errors, common parameters, common error types
AWS CLI v2 evs reference https://awscli.amazonaws.com/v2/documentation/api/latest/reference/evs/index.html Exact aws evs command names and options (to cite, not to run)
CloudFormation AWS::EVS reference https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_EVS.html AWS::EVS resource types and their properties
AWS General Reference: Amazon EVS endpoints and quotas https://docs.aws.amazon.com/general/latest/gr/evs.html The Regions where Amazon EVS is available, service endpoints, and default service quota values. The User Guide's Service quotas page links here for the numbers

Stay within these pages and the pages their indexes link to. When an EVS page defers to another page on docs.aws.amazon.com (for example, EC2 Capacity Reservations, Direct Connect, IPAM, or Secrets Manager), that page counts as documentation: follow the link, and any further links on that page that stay on the question's topic, and cite it. Do this before saying you don't know.

Some EVS pages link outside the AWS documentation, for example to Broadcom's VCF documentation or to an AWS pricing page. What the EVS page itself says is a source you can cite. Don't answer from the linked page. If it's where the rest of the answer lives, give the link and say it's outside the Amazon EVS documentation.

One exception: for what Amazon EVS bills, what each billed item is called (including what the AWS Pricing Calculator calls it), and its listed price, read and cite the Amazon EVS pricing page. Follow SKILL.md's price rule: quote prices as the page states them, tell the user to confirm them there and in the AWS Pricing Calculator, and compute no totals.

Find and read pages

Answering

  • Cite the pages you used, with their .html URLs.
  • When a fact differs by deployment mode (EVS-deployed or self-deployed), say which mode it applies to; EDO uses self-deployed mode.
  • For what EDO supports or does, read the matching release README (core.md, "Use the matching EDO release"); it wins over the User Guide. Also read the User Guide's page on it, and if they differ, cite both and say which applies.
  • For supported versions, Regions, instance types, and limits, also check the User Guide's Document history.
  • Match the user's level: if they aren't technical, explain each technical term the first time you use it.
  • If the documentation doesn't cover something, say so plainly, name the pages you checked, and don't fill the gap from memory.

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