winterbaume-ec2instanceconnect

EC2 Instance Connect service implementation for winterbaume.

This crate is part of the winterbaume workspace — a suite of in-process AWS service mocks for Rust. Use the umbrella winterbaume crate to pull in all services at once, or depend on this crate directly for EC2 Instance Connect only.

Winterbäume is not affiliated with, endorsed by, or sponsored by Amazon Web Services, Inc. or Amazon.com, Inc. Amazon Web Services, AWS, and related marks are trademarks of Amazon.com, Inc. or its affiliates. All other trademarks are the property of their respective owners.

Coverage

Coverage is generated from .agents/docs/API_COVERAGE.md by update_readme.py. The winterbaume row counts only operations with real, state-backed logic; stubs counts handlers that route the request and return an empty/default response without real behaviour. Operation-count coverage is a prioritisation signal, not a behavioural guarantee.

See the workspace README.md for setup, usage, and the full cross-service coverage table.

Server-mode usage

Start winterbaume-server and point the AWS CLI at it:

cargo run -p winterbaume-server -- --host 127.0.0.1 --port 5555

export AWS_ENDPOINT_URL=http://localhost:5555
aws ec2-instance-connect send-ssh-public-key --instance-id i-00000000 --instance-os-user ec2-user --ssh-public-key file://key.pub

Current Network Resource Stub Semantics

EC2 Instance Connect stores endpoint networking as service-local endpoint records.

• Endpoint state records include subnet ID, VPC ID, security group IDs, preserve-client-IP mode, DNS name, FIPS DNS name, and network interface IDs.
• Created endpoints mint their own endpoint and network-interface-looking identifiers, and describe/list responses echo the stored fields.
• Endpoint lifecycle is not reflected into EC2 network interface state.
• The implementation does not consult winterbaume-ec2 state for these identifiers, so it does not check that referenced VPCs, subnets, security groups, VPC endpoints, network interfaces, or load balancers exist, belong to the same VPC, or are in a usable lifecycle state.

Example

use aws_sdk_ec2instanceconnect::config::BehaviorVersion;
use winterbaume_core::MockAws;
use winterbaume_ec2instanceconnect::Ec2InstanceConnectService;

#[tokio::main]
async fn main() {
    let mock = MockAws::builder()
        .with_service(Ec2InstanceConnectService::new())
        .build();

    let config = aws_config::defaults(BehaviorVersion::latest())
        .http_client(mock.http_client())
        .credentials_provider(mock.credentials_provider())
        .region(aws_sdk_ec2instanceconnect::config::Region::new("us-east-1"))
        .load()
        .await;

    let client = aws_sdk_ec2instanceconnect::Client::new(&config);

    // EC2 Instance Connect sends SSH keys to running instances.
    // This example demonstrates client setup for the EC2 Instance Connect service.
    println!("EC2 Instance Connect client ready. Use send_ssh_public_key() to push an SSH key.");
    let _client = client;
}

Implemented APIs (2)

• SendSSHPublicKey
• SendSerialConsoleSSHPublicKey