This guide will provide instructions on how to deploy the Turbonomic AWS Marketplace template on EC2.
For AWS Marketplace 1-Click Launch process please click here
Note: The process outlined in this article is manual deployment, for a fully orchestrated process using AWS CloudFormation please click here
For Deploying Turbonomic on Azure, please visit this article
To deploy Turbonomic on AWS you will need:
- Access to AWS Console and an active AWS Account with an ability to deploy instances to EC2
- Valid Turbonomic license
- Access the AWS portal (https://aws.amazon.com/) and log in using your AWS credentials and click on the EC2 Option
- Confirm that the Availability Zone you wish to deploy the instance by selecting it from the drop-down menu on the top-right corner
- Click on Launch Instance
- In the Instance launch wizard, click on AWS Marketplace, and search for Turbonomic, you should see a result similar to the below, click on Select
- In Step 2: Choose an Instance Type, you will be presented with 3 supported Instance Types, select the one you wish to use. For most deployments, m4.xlarge is recommended. Click on Next: Configure Instance Details
- In Step 3: Configure Instance Details, you will need to define the network elements of the instance, subnet, and public IP assignment.
NOTE: Please ensure to select the proper settings defined by your organization standard around connectivity and security. For most secure deployment, if you have a VPC that is connected to your network via VPN, ensure to select that VPC and do not assign Public IP.It is also recommended to set Shutdown behavior to Stop, enable Termination protection and CloudWatch monitoring.
Click on Next: Add Storage to move to the next step.
Recommendation: Turnonomic recommends to setup and use of IAM Instance Profiles (Instance Roles) for authentication. Instance Roles are much easier to manage for compliance purposes and are natively supported by the AWS SDK. Further, Turbonomic recommends enabling cross-account access for your Instance roles by following the steps
found here: https://aws.amazon.com/blogs/security/how-to-enable-cross-account-access-to-the-aws-management-console/
- In Step 4: Add Storage, you can resize the disk if needed (the default 150 GB is sufficient for most deployments). Click Next: Add Tags
- In Step 5: Add Tags, you may optionally add tags or if your organization requires it. Click Next: Configure Security Group.
- In Step 6: Configure Security Group, if the instance will be facing the Internet using a Public IP, ensure that HTTPS is allowed -- it is recommended to remove the HTTP port and even the SSH port and enable it only when needed. To enhance security, it is only recommended to define a custom CIDR if possible, Click on Review and Launch.
- In Step 7, Review Instance Launch, ensure to review all warnings displayed in the console and review all settings for this instance. Click Launch to move to the last step.
- Before Launching an instance on EC2, you define an SSH key pair - please create or use an existing key and click Launch Instance. Ensure the acknowledgment checkbox is checked and click Launch Instance.
- During the deployment process you will be presented with the following screens:
Click on the Instance name once displayed.
- In the EC2 Console, wait until the instance is running and then copy its Public IP or DNS name, and paste it in a new browser tab using the https:// prefix. IMPORTANT: Make a note of the instance ID displayed in this screen, it is the default password for the Turbonomic administrator user.
You will be presented with an HTTPS certificate error which is normal. Click to proceed (the process will differ based on Browser used).
- You should see the below login screen, please with the user administrator and the respected instance-id as password
Congratulations, you have deployed Turbonomic on AWS and it is now ready to be used. The next steps will include:
- Apply for your Turbonomic License
- Perform online or offline upgrade to the latest available Turbonomic release
- Add your targets, which most likely will be Public Cloud Targets - Please visit this page for more details on public cloud targets
Other useful tips and information:
- To SSH to the Turbonomic instance on AWS, use the username ec2-user along with the SSH private key associated with the instance
- Consider utilizing auto-scaling for HA/recovery purposes