Keep AWS Private CA for workloads. Add attested device identity with Smallstep.
AWS Private CA issues to callers IAM authorizes and enrolls managed devices through its SCEP and Active Directory connectors. Smallstep adds CA-verified hardware attestation on supported enrollment paths and manages certificate delivery and renewal across a mixed fleet.
Trusted by

An IAM-authorized caller, or a device in a managed fleet?
AWS Private CA signs for whoever IAM allows to call it, under a certificate template, and its connectors extend that to Active Directory autoenrollment, SCEP, and Kubernetes. That suits workloads and AWS services. What AWS does not document is one workflow that combines MDM inventory, CA-verified hardware attestation, and certificate delivery across a mixed endpoint fleet. Smallstep provides that on supported paths.
- AWS Private CA: IAM permission plus template; connectors: domain or SCEP challenge
- Smallstep: attestation on supported paths plus an MDM-synced inventory
- Workload PKI versus fleet certificate management

AWS with Intune SCEP, or attested Windows enrollment
AWS Connector for SCEP has an Intune type: Intune issues and validates a dynamic challenge per request and AWS Private CA signs, and Intune can require TPM key storage on Windows. TPM-backed is not CA-verified attestation. On Smallstep's attested Windows path, the agent proves the key was created in the TPM and the CA checks that against inventory before signing. For other MDMs, AWS's general-purpose connector uses a static challenge, which AWS warns can issue any certificate with any subject.

Who gets the certificate onto the endpoint?
With AWS Private CA, delivery belongs to something else: Intune deploys the SCEP certificate and Wi-Fi profile, Active Directory autoenrollment handles domain-joined Windows, ACM places certificates on AWS services, and your code handles the rest. Smallstep manages delivery and renewal itself for supported Wi-Fi, VPN, and SSH workflows. Some workflows use the attested device identity to obtain a separate application credential; key protection depends on the platform and application.

Let attested devices call AWS with IAM Roles Anywhere
IAM Roles Anywhere exchanges an X.509 certificate for temporary AWS credentials and accepts an external CA as its trust anchor. Register a Smallstep authority and a device certificate issued on an attested path can obtain short-lived credentials, with no long-term access keys on the laptop. Scope the trust anchor and role policies to device certificate attributes, and confirm the signing helper can use the device's key on each platform.

Neither replaces the other
Smallstep does not place certificates on load balancers, CloudFront, or API Gateway through ACM, does not offer an Active Directory autoenrollment connector, and does not issue ML-DSA certificates today, which AWS Private CA does. AWS does not document ACME device attestation, or a workflow combining an MDM-synced inventory, hardware attestation, and credential deployment for Wi-Fi, VPN, and apps across a mixed fleet. Keep your existing X.509 trust anchor and sign a Smallstep intermediate beneath it.

When AWS Private CA is the right starting point
If the certificates are for AWS services, EKS and EC2 workloads, or domain-joined Windows through Active Directory autoenrollment, AWS Private CA is a sound choice. If AWS Private CA and Intune SCEP already meet your fleet's requirements, keep them. Add Smallstep when you need CA-verified hardware attestation or consistent certificate lifecycle management across a mixed fleet.
- AWS services and workloads: begin with AWS Private CA
- Fleet enrollment that Intune SCEP already covers: keep it
- CA-verified attestation or one lifecycle across a mixed fleet: add Smallstep
- Run both under one root when the estate needs both
What Smallstep adds to an AWS Private CA estate
Attestation checked against the fleet inventory
On supported paths, the TPM or Secure Enclave attestation is checked against inventory before issuance.
An inventory that gates issuance
Devices sync from your MDM or the API. Devices not in the inventory get no certificate.
Delivery to the endpoint
MDM profiles and the Smallstep agent install and renew the certificate.
Client profiles deployed too
Wi-Fi, VPN, and SSH are configured on the device to use the certificate.
Short lifetimes without per-certificate math
Device certificates renew often by design; Smallstep's cost model does not count certificates issued.
Keep your existing trust anchor
Your existing root, in AWS Private CA or elsewhere, signs the Smallstep intermediate.
Keep AWS Private CA for workloads. Add attested device identity with Smallstep.
Attested enrollment against your MDM-synced inventory on supported paths, credentials delivered and renewed on the endpoint for Wi-Fi, VPN, and SSH, and device certificates IAM Roles Anywhere can trust.


