Skip to content

Crossplane EC2

Crossplane EC2

Category: Virtual Machine Type: Workload Template Tags: virtualization · virtual-machine · crossplane · AWS Compatibility: genesis-deployment>=3.0.2 · orion-deployment>=3.1.0

Overview

Crossplane EC2 is a workload template that provisions and manages AWS EC2 instances through the Juno platform, giving cloud VMs the same lifecycle management as containerised workstations. Once an instance is provisioned, endpoints like SSH and RDP are automatically discovered and surfaced in Hubble.

This plugin requires Crossplane and Crossplane AWS Provider to be installed first.

How It Works

Workload Template — Installs the EC2 workload schema into Genesis. Once installed, the EC2 type appears in Genesis on the Workloads page, where it can be authored into a workload template. Users can then launch and provision AWS EC2 instances on demand within a project through Hubble.

Prerequisites

  • Crossplane plugin installed
  • Crossplane AWS Provider plugin installed and configured with valid AWS credentials
  • An AWS VPC, subnet, and security groups already configured in AWS
  • Platform versions: genesis-deployment >= 3.0.2, orion-deployment >= 3.1.0

Installation

  1. Install the Crossplane and Crossplane AWS Provider plugins first
  2. Open Terra and navigate to the Plugin Marketplace
  3. Search for "Crossplane EC2"
  4. Click Install
  5. Click Confirm to deploy (no install-time fields required)

Once installed, the EC2 schema is available in Genesis. From the Workloads page, author the template — users can then launch and provision EC2 instances on demand through Hubble.

Configuration

Install-Time Fields

No install-time configuration is required for this plugin.

Workload Launch Fields

These fields are configured when authoring the workload template in Genesis and used each time a user provisions an EC2 instance through Hubble:

Field Details
ami_image_id string · Required
AWS AMI image ID for the EC2 instance
security_group_ids list · Required
List of AWS security group IDs to attach
block_device_mappings list · Required
Block devices to attach (mount path + size in GB)
subnet_id string · Required
AWS Subnet ID for the instance
instance_type string · Required · Default: t3.micro
EC2 instance type (e.g. t3.medium, m5.large)
delete_on_termination boolean · Required · Default: true
Whether to delete EBS volumes when the instance is terminated
region string · Required
AWS region to launch the instance in (e.g. us-east-1)
provider_config_ref string · Required · Default: aws-provider-argocd-provider-config
Name of the Crossplane ProviderConfig to use

Notes

  • EC2 instances are tracked as workloads — stopping a workload in Genesis will terminate the EC2 instance
  • The delete_on_termination field controls whether EBS volumes are destroyed with the instance — set to false to preserve data across launches
  • Network endpoints (SSH, RDP, etc.) are automatically discovered once the EC2 instance is running and surfaced in Hubble
plugins/crossplane-ec2/terra.yaml
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
resource_id: crossplane-ec2
name: Crossplane EC2
icon: https://raw.githubusercontent.com/juno-fx/Terra-Official-Plugins/refs/heads/main/plugins/crossplane-ec2/scripts/assets/logo.png
description: |
  A Crossplane AWS EC2 workload. This plugin will install a Crossplane EC2 XRD, as well as a EC2 workload schema.
  Providing both a Crossplane Composition and EC2Instance claim. Allowing for Kuiper to launch and track AWS EC2
  resources via Crossplane.
category: VirtualMachine
compatibility: genesis-deployment>=3.0.2,orion-deployment>=3.1.0
tags:
  - virtualization
  - virtual-machine
  - crossplane
  - cluster-level
  - AWS
  - workload
fields: []