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.0 Release Notes
PrimeKey is proud to announce the release of EJBCA Cloud 2.0.
This is a significant release for EJBCA Cloud and introduces a configuration wizard for CloudHSM and Relational Database Service (RDS) installation.
The new configuration wizard assists users to more easily configure the instance and allows you to:
- Configure a Subject Alternative Name (SAN) to a certificate upon install. This SAN is domain validated for the correct format (it is not looked up in the Domain Name System (DNS)).
- Install directly to an RDS database of MariaDB format.
- Set a custom superadmin password and username during installation.
- Import a CA certificate to have the instance be used as a Registration Authority (RA) or Validation Authority (VA).
- Configure the CloudHSM to configure the ManagementCA keys in a CloudHSM cluster. Note that this cannot be validated before installation due to AWS restrictions. If the install fails, it will fall back to a soft key install.
For more information on configuring an EJBCA Cloud AWS instance, see the AWS Launch Guide.
EJBCA Enterprise Upgrade
The EJBCA Enterprise 188.8.131.52 maintenance release resolves vulnerabilities found in EJBCA during penetration testing.
For more information, refer to EJBCA 184.108.40.206 Release Notes.
EJBCA Enterprise Cloud VA in AWS
The EJBCA Enterprise version in the VA specific instance in the AWS Marketplace is upgraded to 220.127.116.11. For more information, refer to EJBCA Release Notes.
The EJBCA Enterprise Cloud Validation Authority (VA) version in AWS is now 2.1. For more information, see EJBCA Cloud AWS VA.
New Features and Improvements
New Features and Improvements in AWS
The following lists new features and other changes included in the release: