AWS architecture
Understand the infrastructure a Virtual Signer runs on in your Amazon Web Services (AWS) account
The Virtual Signer on AWS runs in your own AWS account, on hardware-based confidential computing. An AWS CloudFormation stack deploys and manages it.
Key components
The Virtual Signer infrastructure combines the following AWS services.
Networking layer
Amazon VPC provides network isolation with private subnets and controlled egress through a NAT Gateway. Security Groups enforce firewall rules that control inbound and outbound traffic, permitting only authorised connections. All Virtual Signer instances operate within private subnets with no direct internet access.
Compute layer
Amazon ECS on EC2 orchestrates the containers. The deployment uses EC2 rather than Fargate because AMD Secure Encrypted Virtualization–Secure Nested Paging (SEV-SNP) hardware security features require access to the underlying instance. Each Virtual Signer identity runs as a single instance. For more signing capacity or availability, register additional signers rather than scaling one signer out; see Self-hosted architecture.
Storage layer
Amazon S3 provides encrypted, versioned storage buckets for each Virtual Signer instance. Each Virtual Signer has its own AWS KMS key, so one instance can't read another's data. CloudWatch Logs stores encrypted logs with configurable retention policies.
Security layer
The security layer provides defence in depth by combining hardware protection, encrypted storage, and strict access controls.
- AMD SEV-SNP encrypts all Virtual Signer memory at the hardware level, making it inaccessible even to the hypervisor.
- Bottlerocket OS provides a hardened container host with an immutable root filesystem and kernel lockdown in confidentiality mode.
- AWS Key Management Service (KMS) with customer-managed keys (CMKs) encrypts all data at rest including S3 buckets. Each Virtual Signer has its own key.
- IAM Roles enforce least-privilege access, limiting each component to only its required permissions.
- AWS Secrets Manager holds the Virtual Signer's API key credentials.
The Virtual Signer seals its approval mode, policy URL, recovery public key, and channel security when it first registers. You can't change them afterwards. See Virtual Signer disaster recovery.
One stack per Virtual Signer
Each Virtual Signer runs in isolation from any others you deploy.
Per-instance resources
Every instance has its own:
- Customer-managed KMS key for encryption
- Isolated S3 bucket
- Independent CloudWatch log group encrypted with the instance's KMS key
- Unique ECS service with its own task definition
- Distinct IAM role scoped to access only that instance's resources
Hardware and operating system
AMD SEV-SNP
AMD SEV-SNP encrypts all Virtual Signer memory with a unique hardware-generated key. It enables cryptographic attestation of the execution environment before any key operations run. This protects against infrastructure-level threats, including potentially malicious hypervisors, because the security guarantees come from AMD processor features rather than software alone.
Bottlerocket OS
The EC2 instances run Bottlerocket, a purpose-built container operating system. Its root filesystem is immutable, preventing runtime modifications and rootkits. Updates use atomic operations with automatic rollback on failure. The OS includes only essential components and runs with kernel lockdown in confidentiality mode.
Data flow and security
Request processing
- Outbound only. The Broker opens connections to the io.sign signing service and to your approval policy. It accepts no inbound traffic from outside the VPC.
- Authentication. The Broker authenticates to io.sign with the machine-client credentials issued for your environment.
- Authorisation. Your approval policy approves or rejects each key generation, signing, and reshare request before the Broker takes part.
Cryptographic operations
- Key generation. The Virtual Signer creates key shares within AMD SEV-SNP protected memory.
- Secure storage. KMS encrypts key shares before the Virtual Signer writes them to S3.
- Runtime protection. The Virtual Signer decrypts key shares only in SEV-SNP-protected memory during signing.
- Audit trail. The Virtual Signer logs all operations to encrypted CloudWatch logs.
Data protection
KMS-managed keys encrypt all data at rest. Network connections use TLS. AMD SEV-SNP encrypts data in memory, so it stays protected during computation.
Infrastructure as code
You define and deploy the Virtual Signer infrastructure with AWS CloudFormation.
CloudFormation
We provide a one-click deployment through the AWS Console. It runs in the AWS regions that offer AMD SEV-SNP: eu-west-1 and us-east-2. Template parameters let you adjust key settings without changing the underlying infrastructure code. The template turns on AMD SEV-SNP on the EC2 instances it creates.
Updated 17 days ago