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.

referencesedomonitor.md

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

Monitor and verify the deployment

Use the rules in SKILL.md and the rules and progress record in core.md. Establish the live target and deployed release before observing an existing deployment. Read that release README's "Monitoring & recovery" and "Notifications" for commands, stages, timing, and completion signals.

Observe and report

Discover logs through the actual stack and confirm its environment. Use the orchestrator log as primary progress evidence; runner tags may be stale after a separate resume. Stack creation alone is not deployment completion.

Report stage changes, errors, and observed success. Agree on an appropriate update cadence within the harness's capabilities; do not hard-code stage counts or expected durations. Use the release's expectations when explaining progress. Investigate an overrun without treating elapsed time alone as failure.

Within one reply, check once (a few minutes at most), report, and say when to check again; don't keep watching until something changes. Nothing runs between replies unless the harness supports scheduled checks, so never promise an update you can't send ("I'll report every 30 minutes"). If they aren't supported, provide the resolved README monitoring commands and configured notification path, and explain how to return for a status check. Keep unverified completion pending. Do not provision additional monitoring services to replace a harness capability.

Credential expiry affects observation; after the user refreshes and identity is verified, continue monitoring without relaunching. On a failure, preserve evidence and use recover.md.

Verify and hand over

Verify the README's completion signal and the intended environment/host state read-only. Distinguish tool completion from UI/application access you have not tested.

Report outcome, account/Region, stack/environment IDs, release, log location, access route, and continuing charges. For access or cleanup help, use operate.md. Record completion evidence and stop monitoring tasks/streams you started. A status request ends with the observed status.

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