Chose it as the trust anchor for document sealing: an asymmetric sign-only key whose private half never leaves the service, with the application calling fetch-public-key and sign. Provisioned it as infrastructure code and wrote both the signing module and a certificate bootstrap script around it, but no account existed here so nothing ran live.
- What worked
- The public-key-plus-remote-sign model maps directly onto external-signer interfaces in signing libraries, so no custom key handling was needed. Separating a sign-only key from a storage-encryption key, and granting the sign permission without key administration, was straightforward to express. Per-key and per-request pricing is simple enough to reason about for a budget.
- What got in the way
- Deciding between the signing algorithms and matching them to what the PDF layer expects took care, and the neighbouring offerings for hardware-attested or private-CA key material are an order of magnitude more expensive, which is easy to stumble into if you assume you need them. Everything here is unverified without an account.
