Deploy on AWS
Deployment of Virtual Signer on your own Amazon Web Services account
To generate a full stack to run on AWS via Cloudformation, click the button below. This will redirect you to the AWS console for a quick installation. Note that currently only the eu-west-1 and us-east-1 regions are supported. AMD SEV-SNP is currently only available in these regions and that is required by the MPC Core container for security.
Steps
-
Once loaded the template into the AWS console, validate the template is correct, review the Infrastructure and press Next.
-
On Step 2, there are parameters that will have to be set. Double check the parameters and press Next to Step 3 once complete.
(Note: The parameter names have a suffix of an ID which you can ignore.)
- AuthClientId - Your API Key Client ID. Obtain this from the Dashboard.
- AuthClientSecret - Your API Key Client Secret. Obtain this from the Dashboard.
- OrganisationId - Your organisation ID - reach out to Customer Office or your Sales rep for this.
- ApprovalMode - Choose which Approval Mode you want to configure your virtual signer for
- 'api-approval' - Use your own API to decide whether to approve or reject a request.
- ApprovalExternalPolicyBaseURL - URL that is called for vault reshares and signatures.
(Check here for details and examples.) - ApprovalHttpSignaturePublicKeyHex - Certificate key to validate API calls to the API approver backend.
- ApprovalExternalPolicyBaseURL - URL that is called for vault reshares and signatures.
- 'always-approve' - Approve every request with no policy checks.
- 'api-approval' - Use your own API to decide whether to approve or reject a request.
-
Acknowledge the Cloudformation template and click Next to the Final Review Page
-
Submit the Wizard and wait for Cloudformation to deploy the stack.
For a comprehensive overview of the AWS infrastructure architecture, including security features, multi-tenant isolation, and technical components, see the AWS Architecture documentation.
Components
| Resource Component | Configuration Assumption |
|---|---|
| EC2 Instance (Broker) | 1 m6i.xlarge instance, running 24/7. |
| EC2 Instance (MPC Core) | 1 c6a.large instance, running 24/7 with AMD SEV-SNP enabled. |
| NAT Gateway | 1 NAT Gateway, running 24/7 (hourly fee). Shared by Broker and MPC Core. |
| CloudWatch Logs | 10 GB data ingested & stored per month |
| AWS KMS | 1 Customer-Managed Key |
| Secrets Manager | 1 secret stored |
| Amazon S3 | Minimal storage (< 10 MB) and requests |
| Variable Data Costs | It includes data transfers, logs storage etc. |
Updated about 2 months ago