EJBCA Cloud AWS
- AWS Launch Guide
Quick Start Guide
- Create Crypto Tokens
- Create Root CA Certificate Profile
- Create Issuing CA Certificate Profile
- Create Certificate Authorities
- Create User and Workstation Profiles
- Create End Entity Profiles
- Request Certificate
- Create Another Administrator Account
- Import Certificate to Mozilla Firefox
- Configure Health Checks
- Create CRL Updater Service
- AWS Backup Guide
- AWS Restore and Upgrade Guide
- AWS TLS Certificate Generation Guide
- AWS RA Configuration and Administration Guide
- AWS VA Configuration and Administration Guide
AWS Cluster Configuration Guide
- Cluster AWS Operating Environment
- Multi Node Clusters
- Cluster Security Groups
- Clustering with RDS Database
- Clustering with Galera on Local Nodes
AWS CloudHSM Integration Guide
- Multiple Crypto Tokens with AWS CloudHSM
- 1 - Create CloudHSM Cluster
- 2 - Use OpenSSL to Validate the HSM
- 3 - Initialize the CloudHSM
- 4 - Assigning the Security Group to the EJBCA Instance
- 5 - Configure the cloudhsm-client
- 6 - PKCS11 PIN
- 7 - Activate the Cluster
- 8 - Create a CloudHSM Crypto User
- 9 - Create a Keystore in the HSM with clientToolBox
- 10 - Test with EJBCA ClientToolbox
- 11 - Create a CryptoToken in EJBCA
- Appendix A - Restoring an HSM Backup to a New Instance
- Appendix B - Troubleshooting HSM Issues
AWS Certificate Manager Integration Guide
- Provisioning an EJBCA Instance and setting up CloudHSM
- Create Root CA Keys
- Create CloudHSM Crypto Token for Root CA
- Create the Root and Issuing CA Certificate Profiles
- Create End Entity Sub CA Profile
- Create Root CA that uses the CloudHSM Crypto Token
- Create AWS ACM Certificate Authority CSR
- Add ACM PCA End Entity
- Generate the ACM PCA Certificate for AWS
- Fulfill the Pending ACM PCA Certificate Request
- AWS S3 Publisher Configuration Guide
- AWS KMS Configuration Guide
- How to Create Support Package
- EJBCA Cloud AWS VA
EJBCA Cloud Azure
- Azure Launch Guide
- Azure Backup Guide
- Azure Restore and Upgrade Guide
- Azure TLS Certificate Generation Guide
- Azure RA Configuration and Administration Guide
- Azure VA Configuration and Administration Guide
- Azure Cluster Configuration Guide
- Azure Key Vault Integration Guide
- How to Create Azure Support Package
- EJBCA Cloud Release Notes
EJBCA Cloud 2.1 Release Notes
PrimeKey is pleased to announce the release of EJBCA Cloud 2.1.
EJBCA Cloud 2.1 adds more robust RDS/Aurora database integration options.
Improved Database Configuration
You can now select to join a node to an existing EJBCA database, provided you already have a database with an existing EJBCA installation.
The configuration wizard also performs a check for an existing database with the name provided. If the database already exists, the installation will not proceed and you are given a Database Exists error. To resolve the issue, either change the database name or drop the existing database that was manually created.
For more information, see Database Configuration.
New Features and Improvements
The following lists new features and other changes included in the release.
EC-145 - Wizard now allows for a "cluster join" and gives the option to join an existing installation.
EC-146 - Wizard will now not only check for database connectivity, but checks to make sure the database does not already exist for normal installations.
2.1.1 Minor Update to AWS
EC-147 - Database permissions not applied correctly on certain RDS instances where external IPs were not utilized.
EC-148 - Script that turns EJBCA Cloud node into an RA, VA or Root doesn't apply reqcertindb property properly.
EC-149 - Script that turns node into an RA, VA or Root doesn't execute SQL commands correctly due to whitespace in source file.
The following provides important information on changes and requirements to be aware of when upgrading.