Deploy on AWS

Deploy a Virtual Signer in your own Amazon Web Services account with CloudFormation

Deploy a full Virtual Signer stack in your own Amazon Web Services (AWS) account with a CloudFormation template. The button below opens the template in the AWS console.

Deploy in eu-west-1 (Europe, Ireland) or us-east-2 (US East, Ohio). The Virtual Signer's Multi-Party Computation (MPC) Core needs AMD Secure Encrypted Virtualization–Secure Nested Paging (SEV-SNP), which AWS offers only in these regions.

Before you begin

  • Get your Virtual Signer credentials from io.finnet support: a client ID, client secret, and your organisation ID. See Deployment.
  • Generate your disaster recovery key pair, and have the public key ready. See Virtual Signer disaster recovery.
  • Choose your approval mode. For api-approval, have your custom policy server URL ready.

Deploy the stack

  1. In the AWS console, check the template, review the infrastructure, and click Next.
  2. Set the parameters below, check them, and click Next. Ignore the ID suffix on each parameter name.
  3. Acknowledge the CloudFormation template, and click Next to go to the final review page.
  4. Submit the wizard, and wait for CloudFormation to deploy the stack.
ParameterValue
AuthClientIdThe client ID io.finnet support issued for this Virtual Signer.
AuthClientSecretThe matching client secret.
OrganisationIdYour organisation ID, from io.finnet support.
InitialDeviceNameThe name the Virtual Signer registers under. It must be unique in your organisation.
DrPublicKeyPemBase64Your disaster recovery public key, as a single line of base64. Encode the PEM file with base64 -w0 mlkem768_pub.pem.
ApprovalModeThe approval mode for your Virtual Signer: api-approval or always-approve.
ApprovalExternalPolicyBaseUrlFor api-approval only. The URL the Virtual Signer calls for vault reshares and signatures. See Custom policy server for details and examples.
ApprovalHttpSignaturePublicKeyHexFor api-approval only. The hex-encoded public key the Virtual Signer uses to verify your policy server's signed responses.

The template also has parameters with working defaults, such as InstanceType (c6a.xlarge) and LoggerLevel (info). Change InstanceType only to another SEV-SNP instance type: m6a, c6a, or r6a.

The approval modes work as follows:

  • api-approval: your own API decides whether to approve or reject each request.
  • always-approve: the Virtual Signer approves every request with no policy checks. Development only. Never use it for a vault that holds real assets.

When the stack is deployed, check it with Testing the deployment.

For the architecture of the stack, including its security features and components, see AWS architecture.

Components

The stack's resources, and the usage assumed for each when estimating its running cost:

Resource componentConfiguration assumption
EC2 instance1 c6a.xlarge instance, running 24/7 with AMD SEV-SNP enabled. It runs both the Broker and the MPC Core. AWS charges extra for SEV-SNP instances.
NAT Gateway1 NAT Gateway, running 24/7 (hourly fee).
CloudWatch Logs10 GB of data ingested and stored each month.
AWS KMS1 customer-managed key.
Secrets Manager1 secret stored.
Amazon S3Minimal storage (less than 10 MB) and requests.
Variable data costsData transfer, log storage, and similar usage charges.

Did this page help you?