Repository navigation
Releases
v1.1.0
Adds support for r7i.metal-24xl and r7i.metal-48xl hosts, which have no local disks, by using Amazon FSx for NetApp ONTAP for the VCF management datastore. Also adds VCF 9.1.1, and the Amazon EVS Agent Skill, which enables an AI agent to assist with Amazon EVS questions and use the tooling in this GitHub repository.
EVS Deployment Orchestrator (EDO)
Added
r7i.metal-24xlandr7i.metal-48xlhosts, with Amazon FSx for NetApp ONTAP as the management cluster's datastore. Set it in the new, optionalstoragesection of the blueprint:storage.principal.type: "fsxn", with the FSx settings in astorage.principal.fsxnblock. Withoutstorage, or withtype: "vsan", the orchestrator deploys vSAN as before. Diskless instance types needtype: "fsxn", because vSAN needs local NVMe. With FSx for NetApp ONTAP, a simple deployment needs only 2 hosts.- The EVS Deployment Orchestrator (EDO) can create the FSx for NetApp ONTAP file system for you. To have EDO create it, leave out
fsxn.volume_idand set every field in thefsxnblock:file_system_name,storage_capacity_gb,throughput_capacity_mbps,storage_efficiencyands3_access. The file system is Single-AZ, in the VPC the stack creates, and is created before any host is deployed. - Use an existing FSx for NetApp ONTAP volume by providing a valid
fsxn.volume_idand an existing VPC (ExistingVpcId). The orchestrator checks the volume, its VPC, its Availability Zone, and its security group rules before creating any host. It will never change or delete the existing volume. Creation fields are ignored with a warning if thefsxn.volume_idis present. - Once a deployment succeeds, the stack that holds the orchestrator-created file system gets CloudFormation termination protection.
destroy.pyand the runner's--destroykeep the orchestrator-created file system, which keeps billing. Add--delete-storageto delete it with the datastore and every VM on it.destroy.py --allneeds--delete-storagewhen that file system exists. Teardown deletes the volume without a final backup, so no FSx backup is left billing, and waits up to 2 hours for the file system to delete. Backups you made yourself are never touched.check-quotas.pychecks FSx for ONTAP quotas when the orchestrator will create a file system.- VCF 9.1.1 (
evs.vcf_version: "9.1.1"), with the 9.1.1 SDDC Manager OVA. - The README adds sections on monitoring a deployment, troubleshooting, and adding or removing hosts.
Fixed
- The README's CLI launch uploads the template to your S3 bucket and creates the stack with
--template-url. The template is larger than the 51,200 bytes CloudFormation accepts with--template-body, so the documented command failed.
Security
urllib32.8.0 in the VCF deployment stage, for the HTTPS proxy TLS and chunked-response issues fixed in that release.
Agentic experience
Added
- Amazon EVS Agent Skill (
skills/amazon-evs-agent-skill/) follows the Agent Skills specification. It works with agents that support Agent Skills.- Q&A: answers factual Amazon EVS questions from the Amazon EVS documentation and cites the page for each answer. When the documentation doesn't cover a question, it says so instead of answering from model knowledge.
- EDO deployments: drives an EDO deployment end to end with the user's AWS credentials, in four phases:
- Prepare: read-only discovery of the account, Region, EVS versions and instance types, VPCs, quotas, artifacts, and the depot secret. It then creates a validated blueprint, launch parameters, and a deployment plan for review.
- Run: after the user approves the plan, performs the setup and stack launch the plan names.
- Monitor: follows progress in the orchestrator log, confirms completion, and diagnoses failures with the README's documented recovery steps.
- Operate: access to the environment, adding or removing hosts, and teardown.
- Guardrails: the skill asks you to approve each change before it makes it in your AWS account, never reads secret values, and saves its progress in a local, git-ignored folder so a later session can continue.
- Release pinning: the skill reads EDO's README at the release it deploys, so its commands and prerequisites match that release.
SKILL.mdlists the read-only AWS CLI commands the skill runs inallowed-tools, so agents that honor the field can pre-approve them.AGENTS.mdroutes Amazon EVS requests in this repository to the skill.- Requirements: Q&A needs a web fetch tool and access to
docs.aws.amazon.com. Deployments need AWS CLI v2 or the AWS MCP server,git, and Python 3.10 or later withboto3andpyyaml. - Install: copy
skills/amazon-evs-agent-skill/to your agent's skills folder.skills/amazon-evs-agent-skill/README.mdhas the details.
Full history: CHANGELOG.md
v1.0.0
First stable release of EVS Solutions. It contains one tool, the EVS Deployment Orchestrator. The VCF 9 Phased Deployment is removed.
Versions and how they work
From this release, EVS Solutions has version numbers that follow Semantic Versioning 2.0.0.
- Versions available.
v1.0.0is the first stable release and is marked Latest. v0.1.0 is the earlier, historical release with the VCF 9 Phased Deployment; it is unsupported. Every later release follows the rules below. - Unified versions. All tools in EVS Solutions share one version number, and each release includes every tool. Tools from the same release were tested together.
- What the numbers mean. A version has three numbers,
MAJOR.MINOR.PATCH:
| Release | What it means for you | Examples in EVS Solutions |
|---|---|---|
MAJOR, such as 2.0.0 |
Something you use is removed or works differently. The release notes explain what to do | A tool or example blueprint is removed; a blueprint field is renamed or becomes required; a template parameter or stack output changes |
MINOR, such as 1.1.0 |
Something new is added. What you already use keeps working | A new tool; a new supported instance type or VCF version; a new optional blueprint field |
PATCH, such as 1.0.1 |
Fixes only. Inputs and outputs don't change | A bug fix in a deployment or teardown; a README correction |
- Finding your version. The
VERSIONfile at the repo root, with a copy in each tool's folder, holds the version, such as1.0.0. For the EVS Deployment Orchestrator, the stack's template description in the CloudFormation console starts with it, such as "Amazon EVS Deployment Orchestrator v1.0.0". - When releases come out. Releases go out when changes are ready, not on a fixed schedule. Before a MAJOR release, a release candidate such as
v2.0.0-rc.1is published as a Pre-release so you can test it first. - Older versions. Released versions never change, and every release stays on the Releases page with its tag, such as
v1.0.0. You can download any release as it was, or check it out withgit checkout v1.0.0. - Removals are announced first. A tool or feature is marked deprecated in a MINOR release. It's removed in a later MAJOR release.
- Upgrading. Before you move to a newer version, read the notes of every release in between. A MINOR or PATCH upgrade keeps what you already use working. A MAJOR upgrade can need changes, and its notes say what to do.
All tools
Added
- Release notes and history. A root
CHANGELOG.mdrecords every release, grouped by tool, and every release is on the Releases page. - Stay informed. To hear about new releases, choose Watch, Custom, Releases on the repo page.
- Support matrix and help. The root README lists the VCF versions and instance types each release supports, and has a "Get help" section.
EVS Deployment Orchestrator
Deploy/EVS-Deployment-Orchestrator/. From a single CloudFormation stack, it creates the EVS environment and its bare-metal ESXi hosts, installs VCF 9 (vCenter Server, NSX Manager, SDDC Manager and VCF Operations), and deploys an NSX edge cluster. A deployment runs unattended and takes about 4-7 hours.
Supported versions
- VCF: 9.0.2 and 9.1.0. The SDDC Manager OVA version must match
evs.vcf_versionin the blueprint. - Instance types:
i4i.metal,i7i.metal-24xlandi7i.metal-48xl.
Breaking changes
- The four instance-type example blueprints are removed. These were
i4i.metalandi7i.metal-24xl, each for VCF 9.0.2 and 9.1.0. To build a blueprint, copyblueprints/custom.all-options.example.yamland setevs.instance_type,evs.vcf_versionand the other fields markedREQUIRED.
Added
- Version in the CloudFormation console. The template's description starts with the version, such as "Amazon EVS Deployment Orchestrator v1.0.0", so the console shows which release a stack came from.
- Blueprint version check. A blueprint can name the orchestrator releases it works with, such as
requires: { edo: ">=1.0.0, <2.0.0" }. If the orchestrator's version is outside that range, it stops at launch, before it deploys anything, and names the release you need. A blueprint withoutrequiresis treated as written for v1.0.0, so it runs on every 1.x release. The orchestrator also logs its version and warns about top-level blueprint sections it doesn't use.
Changed
- The template runs the release it came from. The template checks out the
v1.0.0tag, notmain, so a stack launched or updated later runs the code its template was tested with. To get newer code, use the template from a newer release. - ESXi build matches the VCF version. When the blueprint doesn't set
evs.esx_version, the orchestrator picks the newest ESXi build with the same major.minor.patch as the VCF version, so VCF 9.1.0 gets an ESXi 9.1.0 build and not a newer patch the VCF Installer rejects. If no build matches, the deployment stops and lists the available builds. - The README documents
i7i.metal-48xland starts every deployment fromblueprints/custom.all-options.example.yaml.
What it includes
These were already in v0.1.0 and are listed here because v1.0.0 is the first stable release.
- Networking: a new VPC with the required DNS, NAT gateway, Route Server and security group, or your own VPC (BYO-VPC) if it meets the requirements in the README.
- Credentials: appliance passwords are generated and stored in AWS Secrets Manager.
- Pre-launch check:
check-quotas.pycompares the blueprint's needs with your service quotas and current usage, and prints the commands to fix any shortfall. - Teardown:
destroy.pyremoves the environment, the infrastructure or everything, back to a state that no longer bills. - Progress: CloudWatch Logs, and optional SNS notifications through
SnsTopicArn. - Access: an optional Windows jumpbox (
jumpbox.enabled) for reaching the vCenter, NSX and SDDC Manager UIs inside the VPC.
VCF 9 Phased Deployment
Breaking changes
- Removed. The EVS Deployment Orchestrator replaces it. There is no in-place upgrade: start a new deployment with the orchestrator. The last version with the phased deployment is v0.1.0.
Full history: CHANGELOG.md
v0.1.0
Historical release, not supported. This is EVS Solutions as it was just before the VCF 9 Phased Deployment was removed. It receives no fixes. Use v1.0.0 or later for new deployments.
This version number was given to it afterwards, when EVS Solutions started using versions in v1.0.0. It has no VERSION file, and its template description doesn't show a version.
To get it, download the source archive from this release, or check out the tag: git checkout v0.1.0.
VCF 9 Phased Deployment
Deploy/VCF9-Phased-Deployment/. It stands up an Amazon EVS environment and brings up VCF 9 in three phases that you run one after another:
- Phase 1: creates the base infrastructure with Terraform: VPC, subnets, Route 53, Route Server, Transit Gateway and an optional Windows jumpbox.
- Phase 2: a Python CLI creates the EVS environment and hosts.
- Phase 3: a Python CLI brings up VCF through the VCF Installer and deploys the NSX edge cluster.
EVS Deployment Orchestrator
Deploy/EVS-Deployment-Orchestrator/. An early version that deploys VCF 9.0.2 or 9.1.0 from a single CloudFormation stack, on i4i.metal or i7i.metal-24xl hosts. It includes four example blueprints, one for each instance type and VCF version.