Studio Project workflows for Amazon EC2 VPC/networking and instance lifecycle management
Amazon EC2 (Elastic Compute Cloud) provides scalable virtual compute capacity in the AWS cloud, enabling you to launch and manage server instances alongside the VPC networking that surrounds them.
This project provides two complementary ways to automate against EC2:
-latest spec is a curated subset covering common CRUD for compute and networking automation — see OpenAPIs below.| Asset | Description |
|---|---|
| OpenAPIs/ | EC2 API OpenAPI specs — curated -latest plus the full dated spec |
| Studio Projects/ | Itential Platform project containing VPC/networking and instance lifecycle workflows |
| Golden Configurations/ | Security Group golden configuration |
| Requirement | Version |
|---|---|
| Itential Platform | 6.x |
| AWS EC2 Adapter | Required for the Studio Project workflows below |
| AWS EC2 Integration Model | Required only if building new automation directly against the OpenAPI specs |
Install the AWS EC2 Adapter and configure an instance in Admin > Adapters, then update the adapterId value in each workflow task to match your instance name before importing.
To build automation directly against the EC2 API instead, import one of the OpenAPI specs from OpenAPIs/ as an Integration Model in Admin > Integrations, then create an integration pointing at your AWS region endpoint (e.g. ec2.us-east-1.amazonaws.com).
Authentication is AWS Signature Version 4 — sign requests with an AWS access key ID and secret access key.
The instance's authentication/server properties should look like this once configured (sessionToken is only needed for temporary/STS credentials):
{
"authentication": {
"hmac": {
"accessKeyId": "<your-aws-access-key-id>",
"secretAccessKey": "<your-aws-secret-access-key>",
"sessionToken": ""
}
},
"server": {
"protocol": "https",
"host": "ec2.us-east-1.amazonaws.com",
"base_path": ""
}
} | Folder | Workflows | Scope |
|---|---|---|
| Provision VPC with Networking / Create VPC | Create VPC | Create a VPC |
| Provision VPC with Networking / Create Route | Create Route | Create a route in a route table |
| Provision VPC with Networking | Create VPC Subnet, Add Ingress Rule to Security Group, Create Security Group with Ingress Rules, Create and Attach Internet Gateway, Provision VPC with Networking | Build out VPC networking end to end |
| Create EC2 Instance | Create EC2 Instance | Launch an EC2 instance |
| Destroy VPC and EC2 Instance / Delete Security Groups | (child workflow) | Delete security groups by VPC |
| Destroy VPC and EC2 Instance / Delete Subnets | (child workflow) | Delete subnets by VPC |
| Destroy VPC and EC2 Instance | Destroy VPC and EC2 Instance, Detach and Delete Internet Gateways by VPC | Tear down a VPC and its instances |
| Dependency | Notes |
|---|---|
| AWS EC2 Adapter | Required. Update adapterId in each workflow task to match your instance name. |
| Spec | Version | Operations | Description |
|---|---|---|---|
amazon_ec2-latest.json | latest (curated) | 212 | Trimmed to 212 of 1254 upstream operations covering common CRUD for compute and networking automation — see breakdown below |
amazon_ec2-2016-11-15.json | 2016-11-15 | 1254 | Full spec for the EC2 API version 2016-11-15. |
amazon_ec2-latest.jsonActively-maintained spec (x-vendor-api-version: 2016-11-15). Trimmed to 212 of 1254 upstream operations (106 of 627 actions) covering common CRUD for compute and networking automation. The full upstream service model covers the entire EC2 API surface, including Transit Gateway, Client VPN, IPAM, Spot Fleet, Reserved Instances, Capacity Reservations, Outposts, and dozens of other specialized areas — none of those are included here. Pull the full spec from amazon_ec2-2016-11-15.json below, or see AWS's official EC2 API reference, if you need one of the excluded areas.
Resources included, by category:
amazon_ec2-2016-11-15.jsonFull spec for EC2 API version 2016-11-15 (627 actions, 1,254 GET/POST operations) — covering the entire upstream API surface as AWS defines it. See amazon_ec2-latest.json above for the curated subset if you just need common CRUD automation.