AWS Signer vs SignPath
AWS Signer
aws.amazon.com
SignPath
signpath.ioSide by side
| Figure | AWS Signer | SignPath |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 2 | 4 |
| Spec score · Code Signing Software | 9.1 (#1) | 8.4 (#4) |
| Access controls | Administrators use AWS Identity and Access Management policies to control which users, groups, and roles can access Signer resources and actions. | Role-based access controls define who can sign which artifacts, when, and with which certificate. |
| Container signing | Signer works with the Notation CLI to sign OCI images in registries such as Amazon ECR, storing signatures alongside images. | Container images can be signed through Notation, Cosign, GPG or the REST API, with OCI layout and registry workflows documented. |
| Purpose | AWS Signer is a fully managed code-signing service that helps verify code integrity and publisher trust. | SignPath provides code signing and software integrity tools that enforce policies across software builds and releases. |
| What it does | AWS Signer is a fully managed service that digitally signs code so recipients can check integrity and publisher identity. | SignPath verifies software origin, applies development and release policies, signs releases and records proof across the delivery pipeline. |
Plans
SignPath
- Open Source Code SigningFree
- Open Source Code SigningFree
- Code GovernancePriced on request
- Software Integrity PlatformPriced on request
In their own words
AWS Signer
AWS Signer is a managed code-signing service for verifying code integrity and publisher trust. It supports signing AWS Lambda deployment packages, code for supported IoT devices, and OCI container images using Notation. Lambda verifies signatures and package integrity when signed code is deployed. For containers, Signer works with Notation in registries such as Amazon ECR, with signatures stored alongside images for verification.
Administrators control access to Signer resources and actions through AWS Identity and Access Management policies. Signing profiles can be managed in the Signer console, AWS CLI, or API. Signer manages certificates and keys for Lambda and container workflows; IoT workflows can use a code-signing certificate imported into AWS Certificate Manager. Documentation also lists integrations with AWS Certificate Manager and CloudTrail, plus Amazon EKS image verification. Notation CLI and Signer plugin installers are listed for Linux, macOS, and Windows. API actions have per-second quotas by account and Region, with no minimum request rate. Use with specified AWS services has no additional charge, though related charges may apply.
SignPath
SignPath provides code signing and software integrity controls for builds and releases. Its format-aware signing covers executables, packages, installers, containers, scripts, manifests, SBOMs, and configuration files. Before trusting a release, it can verify source repositories, branches, build systems, approvals, and CI/CD context. SignPath can produce signed, machine-readable attestations, including SLSA provenance, validation summaries, and signed SBOMs. Listed integrations include plugins and REST API connections for GitHub Actions, GitLab, Jenkins, Azure DevOps, and TeamCity. SignPath says private keys remain in FIPS-compliant hardware security modules and are never exposed or shared. Role-based controls determine who can sign which artifacts and with which certificate. Signing records include the user, file, certificate, policy, and result; reports can be exported, with optional WORM-style log archiving. Deployment options are SaaS, self-hosted, or hybrid. The free Open Source Code Signing plan has eligibility conditions: projects must be actively maintained and released, use an OSI-approved open source license, and have no proprietary components.