Amazon Web Services Deployment
You can deploy a Thales Data Platform image within Amazon Web Services (AWS).
Minimum Requirements
To deploy a Thales Data Platform instance, the following minimum requirements apply:
The minimum requirements for each node are:
System volume: minimum of 200 GB
Memory: 32 GB
vCPUs: 8
We recommend a 5-node cluster:
2 nodes as namenodes, Knox gateway,
3 nodes as datanodes and Node Manager.
The configuration recommended for each node when a 5-node cluster is build is the following:
Instance | vCPU | Mem (GiB) | Storage | CPU Credits/hour | Network Performance |
---|---|---|---|---|---|
t2.2xlarge | 8 | 32 | EBS-Only | 81 | Moderate |
Note
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
AWS region-specific and confidential Virtual Thales Data Platform images (AMI) are obtained by provisioning. Provisioning places a Thales Data Platform AMI in your target AWS account in the target region(s).
Use the Thales Customer Support Portal to request provisioning for a Thales Data Platform AMI.
Note
Only authorized Customer Support Portal users can make provisioning requests.
Login to the Thales Customer Support Portal.
Navigate to the My Provisioning Requests page, through the Tools > Provisioning Requests menu.
Click Create Provisioning Request.
Select Thales Data Platform from the Product Name dropdown.
Select the desired Product Version from the dropdown.
Note
We recommend deploying the most recent version for the latest security fixes and most current features.
Select the desired AWS Region from the dropdown.
Provide your AWS Account Number.
(Optional) If desired, type in the names of Additional Regions in the text field, to deploy AMIs in more than one region.
(Optional) If desired, adjust the Priority. The default priority is 3-Medium.
Click Submit.
A Thales client services engineer will receive and work on the request.
When your provisioning request is completed, you will an email notification with the subject line Cloud Provisioning Request Complete. Alternatively, you can periodically check the provisioning request status directly on the My Provisioning Requests page.
Retrieve the AMI ID from the completed provisioning request.
Navigate to the My Provisioning Requests page, through the Tools > Provisioning Requests menu.
Click on the name of the completed provisioning request. The Status column indicates requests that are completed.
Proceed to deploy the Virtual Thales Data Platform image.
Deploying in AWS
This section provides the steps for deploying a Virtual Thales Data Platform instance in AWS.
Prerequisites
A Virtual Thales Data Platform AMI provisioned using the Thales Customer Support Portal, as described above in Provisioning the AMI.
If using a Windows client use PuTTY or similar utility to SSH to your Thales Data Platform instance as root.
If needed, use PuTTYgen or similar utility to format the SSH Key Pair.
If using a Linux client use SSH to login as root.
To launch a Thales Data Platform instance in AWS
Sign in to your AWS account at the AWS portal at: https://aws.amazon.com
In the Compute group, select EC2 service.
On the AWS top bar and to the right, make sure you select the AWS Region you provisioned for your AMI.
In the left pane, under the Images, select AMIs and search for the AMI (e.g. ami-04d5de93aaa02ceef) that was provisioned for you by the SafeNet Cloud Provisioning System.
Select your image and then click on Launch instance from image.
In the Choose an Instance Type screen select the desired Instance Type:
Select “t2.2xlarge”, if you’re installing a node that will be part of a 5 node cluster.
Select Next: Configure Instance Details.
In the Configure Instance Details screen,
Key in the number of instances required for the Number of instances. For example, 5 for a 5-node cluster.
Select Next: Add Storage.
In the Add Storage screen, select the desired Size (GiB).
Select Next: Add Tags.
In the Add Tags screen, select Add Tag
Enter Tag: Name
Value: Something meaningful to the operator; for example "Thales Data Platform for lab use"
Select Next: Configure Security Group.
In the Configure Security Group screen:
Create a new security group or re-use a previously created group.
Refer to Security Group Rules. Consider adding all of the recommended rules.
Note
To launch the Thales Data Platform, you need at a minimum Port 22 inbound/outbound for TDP SSH connection and Port 443 for an HTTPS connection to the GUI.
Select the Review and Launch screen.
In the Review Instance Launch screen:
Review your launch configuration settings.
Make any changes by selecting the Edit ... at the right of each section.
After your review, select Launch.
You are presented with this dialog box to select a key pair.
Select which Key Pair option to use. The key pair should be in Linux (PEM) format, not OpenSSH 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.)
After selecting the Key Pair, check off the acknowledge statement at the bottom of the dialog box, confirming that you have access to the selected private key file.
Warning
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.
Select Launch Instances.
The Launch Status screen appears. You can review the launch process on this screen.
Note
It can take a several minutes for your instance to launch.
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.
Select your instance in the table and then select Connect.
The Connect To Your Instance dialog box appears:
Copy the instance Public DNS string, for example:
ec2-54-89-148-184.compute-1.amazonaws.com
If using PuTTY, begin a new session.
Paste the Public DNS in the Host Name (or IP address) field and preface this string with "root@".
Set the Connection Type to SSH.
In the Category pane:
Select Connection > SSH > Auth.
Select Browse and navigate to the folder with your Private Key.
Select your Public Key file name. The file name and path is automatically places in the Private key file for authentication field.
Select Open.
Note
If you are unable to connect to your instance using PuTTY, go to: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html for further assistance.
Please follow instructions in Changing the Initial Password and all its following steps: Network Configuration, Configuring Services After Deployment, and Post Install to continue configuring your Thales Data Platform cluster.