EC2 → nodes
RunInstances creates a QEMU node. Start, stop and terminate operate on its lifecycle.
Separate commercial plugin / labtris-aws
Your AWS clients.
Your local infrastructure.
Run supported AWS operations against endpoints on your Labtris host. EC2 creates real guests; network resources use the same infrastructure as your network labs.
If you are looking for a LocalStack-style development environment, start with the operations your application needs. Labtris AWS is its own implementation, with service-by-service coverage and separate access.
How the resources fit together
One host, a shared network underneath.
The AWS API is another way to create and inspect Labtris compute and network objects. Other service endpoints expose the operations implemented by the cloud plugin.
AWS API → Labtris resourcesConceptual topology
Your AWS clients
AWS CLI · boto3 · Terraform · Pulumi
labtris-aws
/_aws/ec2 · /_aws/s3 · /_aws/dynamodb · …
VPC → Labtris lab
Compute and network resources use the network emulator.
Subnet → network segment
Linux bridge, interfaces and packets
EC2 / node A
QEMU/KVM guest
EC2 / node B
QEMU/KVM guest
Service endpoints
Supported operations reach their own backing runtime. These services are not all represented as canvas nodes.
S3
DynamoDB
RDS
Lambda
VPC → labs
The lab scopes compute and networking resources. Subnets map to Labtris network objects.
Inspect the packet path
Use Labtris network tooling for the interfaces and links it manages. Service runtime traffic is not automatically a complete canvas graph.
Coverage, by behavior
Check the operation, as well as the service.
The documented coverage snapshot reports 148 registered services and 24 verified against live backends. Registration alone does not mean a service runs a workload or matches every AWS operation.
Coverage snapshot: September 26, 2026. These are the existing project test results; this page does not claim a fresh verification of every service.
Verified operations
A real client round-tripped the implemented operation against a live backend.
Persistent state
Implemented operations retain state, but do not run a backing workload.
API façade
Some endpoints return SDK-shaped responses without state or work. Check the documented tier.
Compute and access
EC2, SSM, STS and IAM read operations
Storage and databases
S3, DynamoDB, RDS, ElastiCache, OpenSearch, DocumentDB, Redshift and Neptune
Functions and messaging
Lambda, SQS, SNS, MQ, MSK and Kinesis Data Streams
Operations
Route 53, CloudWatch Logs, CloudWatch metrics, Timestream, KMS and Secrets Manager
The groups above name services with documented verified operations. They do not imply complete AWS fidelity. Validate your own SDK calls, failure handling and persistence requirements. Azure, GCP and OCI are planned.
Use the tools you already have
Change the endpoint.
With the plugin installed, point your client at its local endpoint. The example uses the plugin’s development credentials; replace the hostname with your instance.
export AWS_ACCESS_KEY_ID=test
export AWS_SECRET_ACCESS_KEY=test
export AWS_DEFAULT_REGION=labtris-1
aws --endpoint-url https://labtris.local/_aws/sts \
sts get-caller-identity
aws --endpoint-url https://labtris.local/_aws/ec2 \
ec2 describe-instancesTerraform, boto3 and Pulumi examples, authentication modes and per-service endpoint settings are in the AWS compatibility guide. The network emulator installer alone does not install this plugin.
Access and terms
Ask for the AWS plugin.
The network emulator is MIT licensed. labtris-aws is a separate commercial product in its own repository, with separate access and terms.
Tell us the services and operations you need, and the host you plan to use.