Overview

Product video
EJBCA PKI for Enterprises - A powerful and flexible certificate issuance and management system to issue and enable full life-cycle control of digital certificate and Certificate (CA), Registration (RA) and Validation Authorities (VA); enabling multiple use cases and standards compliance. EJBCA now includes support for CloudHSM and AWS KMS, has introduced support for the ACME protocol and has a REST API. Please visit the EJBCA Enterprise Cloud documentation for CloudHSM and AWS KMS integration guides. This instance includes Standard Standard Support but is functionally identical to the Premium listing.
Version 2.0 and above now feature a web based configuration wizard so options to install directly into an RDS database or even have the ManagementCA keys be generated directly into CloudHSM can be chosen.
Please contact us for discounts on annual and multi-node enterprise pricing at sales@keyfactor.com !
Highlights
- Multiple CAs and levels of CAs, build a complete infrastructure (or several) within one instance of EJBCA.
- Unlimited number of Root CAs and SubCAs. Request cross certificates and bridge certificates from other CAs and Bridge CAs. Issue cross certificates to other CAs.
- Support all common PKI Architectures, as well as many uncommon. Store keys in CloudHSM, AWS KMS, in a PKCS11 connected HSM, or in the database (for demo).
Details
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Free trial
Dimension | Cost/hour |
|---|---|
t3a.large Recommended | $2.97 |
m3.large | $2.97 |
t2.2xlarge | $6.33 |
t2.medium | $2.29 |
t2.xlarge | $4.43 |
t3.medium | $2.29 |
t3.large | $2.97 |
t3.xlarge | $4.43 |
t3.2xlarge | $6.33 |
c5n.2xlarge | $6.33 |
Dimensions summary
Top-of-mind questions for buyers
Vendor refund policy
Custom pricing options
How can we make this page better?
Compliance
Compliance profile
- Source
- Drata Trust Center











Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Additional details
Usage instructions
Resources
Support
Vendor support
Product Support: To register with Keyfactor Support, please send an email to marketplace-support@keyfactor.com and note that you are an AWS customer. Please note that Keyfactor Support has no other way to identify you as a Keyfactor customer unless you first contact us at marketplace-support@keyfactor.com . You will then be asked to fill out a questionnaire so that we can identify you in our system. Please do not expect a response from support without completing this process first.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
FedRAMP
GDPR
HIPAA
ISO/IEC 27001
PCI DSS
SOC 2 Type 2
Standard contract
Customer reviews
Centralized certificate automation has improved security but still needs clearer error handling
What is our primary use case?
The main use case for EJBCA Enterprise in Dell PW is public key infrastructure and certificate lifecycle management. In simple terms, EJBCA Enterprise acts as a certificate authority that creates, signs, manages, and validates digital certificates used to establish trust between PW components and services. The main use cases involve certificate issuance and renewal before expiration. Keyfactor's jobs run daily to check for any expiring certificates and provide alerts if jobs fail, along with the status of certificates due for expiration.
For example, in a real-world enterprise scenario using Dell PW, a telecom company deploys a private 5G network for a large manufacturing plant with multiple services running on Kubernetes in AKS that need secure communication. Since the company does not want each application generating and managing its own certificate, EJBCA Enterprise becomes essential, acting as a certificate authority where a PW service needs certificates.
For example, Hermes needs a certificate to communicate securely with another PW service, with Keyfactor managing the certificate request and EJBCA Enterprise signing the certificates before deployment, which ensures secure communications between Hermes servers and clients.
We use EJBCA Enterprise in our PW enterprise application to establish secure communications between the Hermes client deployed on the client side and our Hermes server, which allows us to check and renew certificates.
What is most valuable?
The best features EJBCA Enterprise offers, in my opinion, include high availability and clustering, REST API and certificate automation, audit logging, role-based access control, and support for multiple CA and RA architectures.
In my day-to-day work, high availability and certificates have made the biggest difference.
EJBCA Enterprise has positively impacted my organization by improving security, reducing operational risk, and enhancing production reliability. This is particularly true in a large enterprise, where my application supports private wireless infrastructure and multiple interconnected services through secure connection establishment and certificate renewal.
Before automation, when we deployed across multiple environments such as dev, SIT, prod, and UAT, manually creating certificates took considerable time. With EJBCA Enterprise, we save almost three hours on customer-related tasks, create certificates faster, and reduce manual work for the testing teams.
What needs improvement?
EJBCA Enterprise could be improved in terms of certificate lifecycle management and error handling in Keyfactor jobs, which sometimes throw unclear error codes. More specific details should be provided for failures, along with enhanced security through more granular RBAC and approval policies, better searchable audit history, and reporting.
Unclear error codes when jobs fail are a frustration for me.
For how long have I used the solution?
I have been using EJBCA Enterprise for four and a half years.
What do I think about the stability of the solution?
EJBCA Enterprise is stable.
What do I think about the scalability of the solution?
EJBCA Enterprise provides excellent scalability, supporting large-scale certificate management, multiple CA configurations, clustering, and high availability deployments. It is capable of scaling to accommodate an increasing number of application services and infrastructure components.
How are customer service and support?
Customer support is reliable and responds promptly depending on the severity of the issues raised, especially if they impact production.
I would rate customer support as a 10.
Which solution did I use previously and why did I switch?
I do not believe we have used any different solutions. We have always started with EJBCA Enterprise and Keyfactor.
How was the initial setup?
EJBCA Enterprise was first deployed on Azure AKS clusters. Last year, we deployed EJBCA Enterprise and Keyfactor in-house, which means we have a mixed deployment in our organization.
We exclusively use Azure for our deployments.
What was our ROI?
We see potential operational benefits from EJBCA Enterprise through centralized certificate management, improved security, reduced manual handling activities, and increased operational reliability through fewer manual renewals needed.
What's my experience with pricing, setup cost, and licensing?
Pricing, setup costs, and licensing are not handled by us, as they are managed by higher management in our large organization.
Which other solutions did I evaluate?
Before choosing EJBCA Enterprise, we evaluated other PKI and certificate authority solutions such as Microsoft AD CS, HashiCorp Vault PKI, and OpenSSL-based solutions. We evaluated them based on security, scalability, and certificate lifecycle management before deciding to go with EJBCA Enterprise.
What other advice do I have?
I would rate EJBCA Enterprise as a seven on a scale of 1 to 10.
I chose seven due to its strong certificate authority, PKI management, HSM integration, high availability, rapid customer support response, and the areas for improvement I have already shared.
Regarding EJBCA Enterprise's AI capabilities, we handled a project deploying in the US government port on Azure AKS clusters where security was well maintained. Although the project is not live yet, I feel EJBCA Enterprise handles security effectively, and I distinguish between its secure capabilities and its AI capabilities, though I cannot confirm deployment specifics.
I advise others looking into using EJBCA Enterprise to acknowledge how it reduces human effort, enhances security, and provides high availability while evaluating certificate management requirements and integration with existing infrastructure before implementation.
Centralized certificate management has reduced costs and supports open-source goals
What is our primary use case?
My main use case for EJBCA Enterprise is setting up our internal certificate authority where all website certificates, specifically internal website certificates, are managed. Anybody in any business unit within our organization needing any SSL or TLS certificate for their web servers can do so by logging into Venafi or making API calls to get the certificate from our internal certificate authority. I have EJBCA Enterprise certificate authority set up behind Venafi, allowing anyone to request a certificate.
I decided on setting up EJBCA Enterprise as our internal certificate authority because it is open source and compared to Microsoft certificate authority, it has a cheaper licensing cost, particularly with Windows servers. Since EJBCA Enterprise is open source and Linux-based, the cost is lower and there are no licensing costs. In our use case, we use Microsoft certificate authority for user-based certificates because with the help of group policy, we can deploy a certificate to user laptops. For this scenario, Microsoft certificate authority is effective. However, for web server certificates which are generally not part of a domain, especially on many Linux servers that are not part of Active Directory, EJBCA Enterprise is the best choice due to lower costs and better fit.
I have additional thoughts about my main use case and how I'm using EJBCA Enterprise, especially since it has integration with Venafi which prevents direct exposure. Users feel they are using Venafi, and based on their certificate request type, the request is redirected to the best working certificate authority. This has worked well for us because EJBCA Enterprise supports API calls, allowing anyone needing a certificate to do so via API calls. Most users today request certificates via API calls due to the rise of DevOps practices. Moreover, EJBCA Enterprise works well with Docker containers or Kubernetes pods, and we have integrated cert-manager with Venafi. Now anybody needing a certificate for their pods or containers can request it, and EJBCA Enterprise is performing effectively for us.
How has it helped my organization?
EJBCA Enterprise positively impacts my organization by aligning with our initiative to promote open-source software. My culture encourages using open-source software, which has helped us significantly. While we still utilize Microsoft certificate authority in certain scenarios, such as user-based or laptop-based certificates, employing EJBCA Enterprise allows us to contribute to our organizational goals and KPIs, particularly because it is open source, which was a major goal for us.
EJBCA Enterprise has definitely resulted in cost savings for my organization. It has also saved us time.
What is most valuable?
EJBCA Enterprise offers several best features, particularly when compared with Microsoft certificate authority, which has its native database that restricts the use of third-party databases. EJBCA Enterprise allows the use of third-party databases, such as Microsoft SQL, enabling additional benefits in creating and running SQL queries that help in reporting and dashboard creation.
Using third-party databases with EJBCA Enterprise has significantly improved our reporting and dashboards. Most developers or operational engineers proficient in infrastructure are skilled with SQL and can run SQL queries effectively. When issues arise, I generally have read-only access or sometimes admin access, enabling me to remove stale entries or edit user details when necessary. For instance, I recall an occasion when a certificate name in Venafi was renamed, but the corresponding name in EJBCA Enterprise was unchanged. In such scenarios, I can rename the common name of the certificate, showcasing the advantages of using third-party databases, as 99% of users know how to execute SQL queries.
I would add that EJBCA Enterprise works effectively with API calls, offering capabilities for certificate requests, renewals, and revocations. We can create customized dashboards depending on our use case, though this does require some development effort. Notably, EJBCA Enterprise now supports post-quantum algorithms, which I appreciate as they keep their product up-to-date. Additionally, being Linux-based contributes to its security, and as an admin proficient in Linux, I favor Linux-based deployments. Given that EJBCA Enterprise and Microsoft are the two main vendors in this space, EJBCA Enterprise stands out as the best choice for a Linux-based deployment.
What needs improvement?
EJBCA Enterprise is performing very well overall. However, one area for improvement could be the addition of a native dashboard capability within EJBCA Enterprise to facilitate reporting. Currently, I rely on Venafi for reporting or have created a custom dashboard by establishing a read replica from the actual database, which requires running ETL jobs to pull new data every day for analytics, causing some headaches. Having native dashboard features directly in EJBCA Enterprise would be beneficial.
I think EJBCA Enterprise is good as it currently stands. They are doing very well, but perhaps future improvements related to AI could be beneficial, although I'm unsure of specifics at this moment.
For how long have I used the solution?
I have been using EJBCA Enterprise for seven years.
What do I think about the stability of the solution?
EJBCA Enterprise is very reliable, thanks to its deployment model. During upgrades, I have had nearly zero outages; when upgrading a number of servers, I upgrade them one by one and disable them from the load balancer to ensure the other servers can manage user requests. Once I upgrade a portion, I test it and re-enable them before proceeding with the remaining servers. This architecture ensures reliability and user satisfaction during upgrades, which is why I appreciate this product.
EJBCA Enterprise is stable.
What do I think about the scalability of the solution?
EJBCA Enterprise scales very well; autoscaling is part of the cloud EC2 setup without vendor reliance. On-premises, EJBCA Enterprise creates a cluster; in my cluster, I had eight to ten servers. I initially started with four servers, and as traffic increased, I deployed additional servers and easily added them to the cluster based on demand, providing options for scalability.
How are customer service and support?
Customer support has been good; it's a mixed experience. For critical incidents, knowledgeable experts provide support, but for minor issues, my experience has been that inexperienced support agents may struggle. EJBCA Enterprise is complex, and support effectiveness often hinges on the experience level of the agent.
I would rate customer support a seven out of ten.
Which solution did I use previously and why did I switch?
I have used Microsoft certificate authority in a previous organization, but not in this one. The choice depends on the organization; EJBCA Enterprise's setup complexity requires someone with significant Linux experience, while Microsoft certificate authority is generally easier to deploy due to its UI-based setup, which many prefer.
How was the initial setup?
I consider EJBCA Enterprise a good product given my seven years of experience using it. The product is very secure; however, I believe that deploying EJBCA Enterprise can be challenging for someone with only a Microsoft Windows-based deployment background. I struggled initially, but once I understood the full architecture and deployment process, it became easier, and I now enjoy deploying EJBCA Enterprise. It remains a complex product that is not easy to grasp at first. I know it is secure because I use it, and EJBCA Enterprise has excelled in essential aspects such as post-quantum cryptography, particularly with the release of EJBCA Enterprise 9.3, which supports post-quantum cryptography algorithms.
I have deployed EJBCA Enterprise on-premises thus far, but I have also conducted a proof of concept on cloud, which worked as well.
For my proof of concept, I used AWS.
As mentioned, EJBCA Enterprise is open-source software, so I conducted the proof of concept and procured the software from the vendor. If you have an EC2 instance with RHEL, deploying it is straightforward.
What was our ROI?
I have absolutely seen a return on investment with EJBCA Enterprise. I have managed around 500,000 certificates in my organization; users can request certificates easily. Licensing is not based on the number of certificates; once setup is complete, the majority of costs are just server-related, making it less expensive compared to Microsoft solutions. This has greatly saved me money.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup costs, and licensing indicates EJBCA Enterprise is comparatively cheaper than Microsoft. The licensing costs are lower, and another notable aspect is the flexibility to choose databases, including MariaDB, SQL, or PostgreSQL, which is advantageous.
Which other solutions did I evaluate?
Before choosing EJBCA Enterprise, I evaluated Microsoft certificate authority. There are limited options in this area, mainly Microsoft and EJBCA Enterprise.
What other advice do I have?
I would rate EJBCA Enterprise a nine out of ten.
I choose nine out of ten for EJBCA Enterprise because it performs very well, but the only area needing improvement is the dashboard functionality; if that is added, it would be a perfect ten out of ten.
My advice for those considering EJBCA Enterprise is to use Microsoft-based deployment for small use cases since EJBCA Enterprise is complex to set up. It is essential to have a very experienced individual for EJBCA Enterprise deployment, ideally with eight to ten years of experience and some architectural background. In contrast, someone with just three to five years of experience can install and configure Microsoft certificate authority more easily. For large enterprises with significant certificate needs, open-source EJBCA Enterprise can provide substantial savings, but expert help is necessary.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Unified certificate management has secured device identities and streamlined code signing
What is our primary use case?
Our main use case for EJBCA Enterprise is internal certificate management.
t.
What is most valuable?
The best features EJBCA Enterprise offers include user-convenient management system, along with detailed profiles for certificate management.
Vault integrations and PQC enablement stand out for me.
What needs improvement?
Include templated profiles for compliance-based certificates. Additional improvements needed for EJBCA Enterprise include pushing more services to SaaS with PQC enablement.
For how long have I used the solution?
We have been using EJBCA Enterprise for the last four years to manage our PKI system.
What do I think about the stability of the solution?
EJBCA Enterprise is stable.
What do I think about the scalability of the solution?
EJBCA Enterprise's scalability is positive, and it is easily scalable, even with respect to certificate growth.
How are customer service and support?
The customer support for EJBCA Enterprise is good, and while there can be delays sometimes due to representatives not fully understanding the system, the overall turnaround time is fast.
I rate the customer support as eight.
Which solution did I use previously and why did I switch?
No
What was our ROI?
I have not evaluated the return on investment in detail, but my impression is that we save time and need fewer employees for certain tasks.
What's my experience with pricing, setup cost, and licensing?
I would not say it is too costly, but I believe the pricing is on the higher side, justified by the user convenient portals and proactive support system.
Which other solutions did I evaluate?
We evaluated couple of market leaders
What other advice do I have?
I gave EJBCA Enterprise a nine due to room for improvement, as not every user who will operate the system is tech-savvy.
My advice for others considering EJBCA Enterprise is to proceed if they have assessed the technical compatibility and use cases required.
Certificate security for MFA has improved and now saves time across multiple organizations
What is our primary use case?
My main use case for EJBCA Enterprise is the creation, registering, and verification of certificates for MFA.
I work for an IAM organization where I use EJBCA Enterprise for browser verification of a device or the device itself, and for that we use the certificates.
I use EJBCA Enterprise to create self-signed certificates for multiple organizations, as many customers who are contracted want to create their self-signed certificates.
How has it helped my organization?
Since using EJBCA Enterprise, I see my organization becoming more upgraded and easier to use, and the console is significantly better now.
It is time-saving; earlier it used to take me more than four or five minutes to create a certificate and its intermediate certificate, but now within two or three minutes I can create the root and certificate if I have the attributes available.
What is most valuable?
The best features EJBCA Enterprise offers, in my opinion, are its superior security compared to some other MFAs which are not anti-phishing.
When I say it is better in terms of security, I mean that for a phone, if you are using a cell phone as MFA, it is not necessary that you always have your cell phone with you, but the certificates are always installed in your browser, and you just have to match the certificate when you are trying to log in. Multiple users can install the certificate in the same device or in the same browser.
I have always used EJBCA Enterprise for security itself.
What needs improvement?
EJBCA Enterprise could be improved because when I started with EJBCA, I did not have many useful courses for creating an intermediate certificate.
Documentation for EJBCA Enterprise is getting better, but there are still some improvements needed to verify each and every tag used in EJBCA Enterprise console, and better descriptions could also help.
I choose a rating of eight because EJBCA Enterprise console takes a lot of time to load and keeps buffering when I click on a certain link.
For how long have I used the solution?
I have been using EJBCA Enterprise for more than a year.
What do I think about the stability of the solution?
EJBCA Enterprise is stable in my experience.
What do I think about the scalability of the solution?
The scalability of EJBCA Enterprise was not that good earlier, but now it is better.
Which solution did I use previously and why did I switch?
EJBCA Enterprise was my first choice; I did not use a different solution before.
What was our ROI?
I believe the time-saving aspect of using EJBCA Enterprise is valuable; I appreciate it in terms of MFA, and it does save money because using alternatives such as Twilio or other MFA options is more cost-efficient and handy.
Which other solutions did I evaluate?
I did evaluate other public infrastructure options before choosing EJBCA Enterprise; I think one was related to Microsoft, but I find EJBCA Enterprise better.
What other advice do I have?
I would rate EJBCA Enterprise an eight overall.
I think EJBCA Enterprise is doing a great job regarding its AI capabilities, and I believe they should keep implementing it.
I find EJBCA Enterprise's accuracy and reliability of output to be good, though it depends on the prompts a person gives.
I would advise others looking into using EJBCA Enterprise to make the console faster, as it takes a lot of time for the request-response cycle.
Automation has improved certificate lifecycles and still needs simpler integration and troubleshooting
What is our primary use case?
One of the most important pain points in certificate life management is that certificates have defined validity periods, so they need to be issued correctly, renewed before their expiration time, and revoked in case of any compromise or when someone is no longer trusted. When these processes are handled manually, it becomes very difficult to maintain all these different certificates together. From my exposure, I understand that this matters in an enterprise and telecom environment where systems need to communicate securely and reliably, and certificate trust is an important part of EJBCA Enterprise.
How has it helped my organization?
The security teams definitely need to understand what certificates have been issued, which certificate authority is responsible for them, and whether the certificate management activities follow the organization's policies. EJBCA Enterprise helps the team in those fields.
What is most valuable?
It is important when systems depend on secure communication and trusted identities that certificate management has a direct impact on both security and operational reliability. Even though the automation and scalability are important, they definitely impact security and how trusted communications are handled in an enterprise.
What needs improvement?
Troubleshooting and observability can be made more accessible. When a certificate-based connection fails, the cause may be an expired certificate, an incomplete trust chain, or an incorrect certificate. If more context is provided, EJBCA Enterprise can be improved.
For how long have I used the solution?
I have had exposure to EJBCA Enterprise in the context of my cyber security internship, and my familiarity is with PKI concepts, digital certificates, and secure communication. I have familiarity from practical work during the internship where I learned about the role EJBCA Enterprise plays in maintaining certificate authorities and certificate lifecycles. I am happy to discuss those things and the technical aspects required for my area of expertise.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
What other advice do I have?
I chose a seven or eight for my rating because, as I mentioned, the integrations should be much easier and the troubleshooting for certificate management needs improvement. If those tips I provided on how to improve EJBCA Enterprise are applied, the rating would definitely go higher.
If other organizations are planning to use EJBCA Enterprise, they should definitely look into some important factors.