Your suggested change has been received. Thank you.


Suggest A Change….


Install Virtual CipherTrust Manager

Amazon Web Services Deployment


Please Note:

Amazon Web Services Deployment

You can deploy a CipherTrust Manager image within Amazon Web Services (AWS).

Minimum Requirements

To deploy a CipherTrust Manager instance, the following minimum requirements apply:

  • System volume: 50 GB for evaluation, 100 GB for production

  • Memory: 16 GB

  • vCPUs: 2

  • NICs: 1

These minimum system requirements are for a system with light to moderate load. For applications that heavily load the system, additional memory and CPU allocation are required. The system volume holds all data as well as backups.

Provisioning the AMI

An AWS region-specific, and confidential Virtual CipherTrust Manager image (AMI) is obtained by provisioning. Provisioning places a CipherTrust Manager AMI in your target AWS account. Separate provisioning requests must be made if you need multiple CipherTrust Manager instances in one or multiple regions.

Use the SafeNet Cloud Provisioning System, to customize a CipherTrust Manager AMI for a specific region.

Only authorized Technical Support Customer Portal users can access the SafeNet Cloud Provisioning System.

Steps to provision a Virtual CipherTrust Manager
  1. Visit the SafeNet Cloud Provisioning System Login page:

    Cloud Provisioning System Login

  2. Enter your Gemalto Service Portal Username and Password, and click Login.

    The New Provisioning Request page loads.

    New Provisioning Request

    You can use the Request List tab to check on the status of your submitted requests.

  3. Select the product CipherTrust Manager AWS and click Next.

  4. Select Select Product Version and click Next. Generally, we recommend that you select the latest version at the top of the list.

    The following Provisioning Credentials screen is displayed:

    Provisioning Credentials

  5. Select your AWS Region and enter your AWS Account Number. Then click Submit.

    An Image request created confirmation message is displayed with a Request reference ID as show here.

    Image request confirmation

    You will also receive a short 'do-not-reply' email from Gemalto.

  6. Using the Requests List tab, you can track the request using the reference ID under the Request ID column. Initially the status shows pending, then it is changed to dispatched and finally it displays created.

    After the image is provisioned, you will see your CipherTrust Manager AMI ID in the Request List table. You may need to refresh you screen to see the updated table.

    You will also receive another 'do-not-reply' email with the CipherTrust Manager AMI ID. The provisioned AMI will then be shared with your AWS account for a minimum two weeks.

Deploying in AWS

This section provides the steps for deploying a Virtual CipherTrust Manager instance in AWS.


  • A Virtual CipherTrust Manager AMI provisioned using the SafeNet Cloud Provisioning System.

  • If using a Windows client use PuTTY or similar utility to SSH to your CipherTrust Manager instance as KeySecure Administrator (ksadmin).

    If needed, use PuTTYgen or similar utility to format the SSH Key Pair. We support OpenSSH format and RSA key algortihm for the public key, and OpenSSH, PKCS1, or PKCS8 format for the private key. We recommend RSA 4096, with RSA 2048 as a minimum size for adequate security.

  • If using a Linux client use SSH to login as KeySecure Administrator (ksadmin).

To launch a CipherTrust Manager instance in AWS

More detailed descriptions of the launch instance wizard settings are available in Amazon EC2 documentation.

  1. Sign in to your AWS account at the AWS portal at:

  2. In the Compute group, select EC2 service.

  3. On the AWS top bar and to the right, make sure you select the AWS Region you provisioned for your AMI.

    AWS Region

  4. Under the Instances>Launch Instance

    1. Provide a Name and Tags for the new instance, if desired.

    2. Select My AMIs and search for the AMI (e.g. ami-1f6b5b60) that was provisioned for you by the SafeNet Cloud Provisioning System.

  5. Next to the image name, click on Select.

    The AWS instance launch page opens.

  6. In the Instance Type section, choose a size that meets the minimum requirements.

  7. Select which Key Pair (login) option to use. We support OpenSSH for the public key format, and OpenSSH, PKCS1 or PKCS8 for the corresponding private key format. Valid options are:

    • Choose an existing key pair from the drop-down list. If your key pair is not on this list, you can import it here:

      Services > EC2 > Network and Security > Key Pairs

    • Create a new key pair. (This option allows you to download your own key pair.)

    It is important that you have access to the key pair you select, otherwise you will not have permissions to perform administrator operations like performing upgrades, advanced logging or an appliance reset.

  8. In the Network Settings section.

    1. If applicable to your AWS account settings, you are presented with a setting for Networking platform, which allows you to choose Virtual Private Cloud (VPC) or EC2-Classic. Virtual CipherTrust Manager is supported in both platforms.

    2. In most cases, select an existing VPC and Subnet. You can also create a new Subnet. For EC2-Classic, you specify an Availability Zone.

    3. Set Auto-assign Public IP to Enabled.

    4. Under Firewall (security groups), create a new security group or re-use a previously created group.

      Refer to Network Security Groups. Consider adding all of the recommended rules.
      To launch the CipherTrust Manager, you need at a minimum Port 22 inbound/outbound for ksadmin's SSH connection and Port 443 for an HTTPS connection to the GUI.

  9. In the Configure Storage section, select the desired Size (GiB).

    • Enter 100 GiB if this is for production.

    • Enter 50 GiB if this is for evaluation.

  10. At the bottom of the screen there is a section Advanced Settings.

    Any information that you need configured before the first boot must be entered here in the User data area. See Plan Configuration Settings for Cloud Init.

  11. In the Summary section to the right:

    1. Review your launch configuration settings.

    2. Make any changes necessary on the sections to the left.

    3. After your review, select Launch instance.

      It can take a several minutes for your instance to launch.

  12. Select View Instances to view the state of your instance as it is being launched. You may need to search for the name of your instance in the Instances table if it is among many others.

    At this point, if you wish to connect as System Administrator (ksadmin) to perform system level duties, duties such as performing network configurations, system upgrades, continue with the next step.

    Refer to Groups for a more detailed list of ksadmin duties.

    Otherwise, browse to step 18 to connect to the CipherTrust Manager Web Page.

  13. Select your instance in the table and then select Connect.

    Connect to Instance

    The Connect To Your Instance dialog box appears:

    Connect to your instance

  14. Copy the instance Public DNS string, for example:

  15. If using PuTTY, begin a new session.

    1. Paste the Public DNS in the Host Name (or IP address) field and preface this string with "ksadmin@".

    2. Set the Connection Type to SSH.

      Putty Configuration

  16. In the Category pane:

    1. Select Connection > SSH > Auth.

    2. Select Browse and navigate to the folder with your Private Key.

    3. Select your Public Key file name. The file name and path is automatically places in the Private key file for authentication field.

      Private key Putty config

    4. Select Open. The following ksadmin screen appears:

      KS Admin Screen

      If you are unable to connect to your instance using PuTTY, go to: for further assistance.

  17. Connect to the CipherTrust Manager Web Page.

    1. Copy the IPv4 Public IP or IPv6 IP address shown in the Instances > Description tab of your AWS instance.

      Instance IP

    2. Browse to HTTPS://. The Log In screen appears.

      AWS Login

  18. Log in using the initial default credentials: Username = admin, Password = admin

    The following notice is displayed:

    Password change

    If the default credentials do not work, you may need to retrieve an autogenerated password, as described in Changing the Initial Password.

  19. Enter a new password using this default Password Policy:

    Min length: 8
    Max length: 30
    Min number of upper cases: 1
    Min number of lower cases: 1
    Min number of digits: 1
    Min number of other characters: 1

    A new Login screen appears.

  20. Using your new password, log in again. The CipherTrust Manager Web Page appears.

    Home Screen

  21. At this point, it's strongly recommended to configure an NTP server.

    1. Navigate to Admin Settings > NTP.

    2. Enter in an NTP Server hostname.

    3. For an authenticated NTP Server, enter in a symmetric key value in the NTP Key field.

    4. Click the +Add NTP Server button.

    See Network Time Protocol Server Configuration for more details.

Congratulations! You have successfully deployed your Virtual CipherTrust Manager instance.

Virtual CipherTrust Manager launches in Community Edition, with some restrictions on functionality. You can activate a 90 day trial evaluation for full functionality. To activate your instance with a trial evaluation, or a term or perpetual license, see Licensing.

Enhanced Networking

The CipherTrust Manager AMI ships with Elastic Network Adapter (ENA) enabled. ENA provides high-performance networking on supported EC2 instance types. For more information visit