Choose Nitro to isolate the signer's execution from the parent host and its software. Choose Docker or Kubernetes to use your existing container infrastructure, trusting its administrators with access to the signer.
AWS Nitro Enclaves runs the API Signer in a hardware-isolated environment within your EC2 instance. The enclave has no persistent storage, external network interface, or interactive access. Even root on the parent instance cannot directly read its memory. It communicates with AWS and Fordefi through the parent instance.
Signer state is encrypted in your S3 bucket, with its encryption key protected by AWS KMS. The supplied policies require attestation from an enclave signed with the approved Fordefi certificate before KMS permits decryption. Decrypted state stays inside the enclave. The host can still interrupt service. Administrators who can change KMS policies remain trusted: they can remove the restrictions that protect stored secrets.
| Docker and Kubernetes | AWS Nitro Enclaves | |
|---|---|---|
| Secrets | Stored in host volumes or Kubernetes Secrets; used in container memory. | Encrypted state in S3; decrypted only inside the enclave under the supplied policies. |
| Administrative access | Sufficient host or cluster privileges can expose signer secrets. | Host access alone cannot read enclave memory. KMS policy administrators remain trusted. |
| Setup | Use your existing Docker host or Kubernetes cluster. | Supply an AWS account, network, and deployment permissions; the template creates compute, runtime IAM role, KMS keys, and S3 bucket. |
| Runtime | Docker or Kubernetes. | One active EC2 instance on a supported x86-64 type. No continuously available standby; recovery and upgrades incur downtime. |
Auto Scaling replaces failed instances, but service is unavailable during recovery.
Fordefi provides the signed image, deployment CLI, and CloudFormation template in one downloadable release. You deploy and operate it in your AWS account. Start with Prepare AWS, then Deploy and manage.