As a transitional step, this site will temporarily be made Read-Only from July 8th until the new community launch. During this time, you can still search and read articles and discussions.

While the community is read-only, if you have questions or issues requiring TIBCO review/response, please access the new TIBCO Community and select "Ask A Question."

You will need to register or log in or register to engage in the new community.

Deploying TIBCO LogLogic® LMI Enterprise Virtual Appliance on Amazon Web Services

By:
Last updated:
8:16am Jul 23, 2021

Back to HomePage


TIBCO LogLogic® provides the industry's first enterprise-class, end-to-end log management solution. Using LogLogic log management solutions, IT organizations can analyze and archive network log data for the purpose of compliance and legal protection, decision support for network security remediation, and increased network performance and improved availability.


This page provides step by step instructions on where can users find TIBCO LogLogic LMI Enterprise Virtual Appliance pre-packaged VM instance, how to download and deploy this VHD on Amazon Web Services. This article assumes users have an account with AWS and have the privileges to deploy EC2 instances.

How to Download LMI VHD File

In order to deploy TIBCO LogLogic Enterprise Virtual Appliance, users need to first download the VHD file for AWS to deploy the EC2 instance. In order to do this, follow the steps below.

  • Go to edelivery.tibco.com website and login using your credentials.
  • Using the search bar, look for "TIBCO LogLogic Enterprise Virtual Appliance", you should then be presented with the following page

edelivery.tibco.com, LMI, UC, LogLogic, Log Management

  • Depending on the latest version available, the current version is pre-populated in the Version field. 
  • Make sure to click on EULA hyperlink and read through the agreement before downloading the software. Once you have read the document choose to Accept the terms option.
  • Selecting the platform is the next step to download the VM. To get the VSphere format of VM, choose Enterprise Virtual Appliance for VMWare ESX as follows

VMware, VMWare ESX, LMI on ESX, VM for LMI

  • Once the platform selection is done, choose the Individual File Download Option. This gives you multiple options.
  • Expand the TIBCO LogLogic Enterprise Virtual Appliance Software option. 
  • Here download the file named as TIB_logeva_x.x.x.vhd.zip file (where x.x.x would be the version of LMI). For example on an LMI 6.1.1 EVA, this is what the list would show:

  • Once the zip file is downloaded, unzip it. At this point, users should have a VHD file that's ready to be uploaded to the Amazon S3 bucket. 

Setting Up The Local System To Upload Files

In order to deploy an instance on Amazon Web Services, it's necessary to upload the VM's VHD file to an Amazon S3 bucket. This can be done in 2 ways. 

Method 1: Using AWS Management Console

Users who have access to the AWS Management Console UI can follow the steps below to upload the VHD to an Amazon S3 bucket.

  • Login to the Management Console and Click Services tab.
  • Choose S3 under Storage Section as follows:

    AWS, AWSs3, EC2, VM. Amazon
  • If there isn't a bucket created already, users will have to create a new one by selecting the Create bucket Option as follows:

    S3 Bucket, Amazon, AWS, AWS LogLogic, LMI
  • Follow the onscreen prompts to create an S3 bucket. For more information, refer to Amazon Documentation on "How to create an S3 bucket".
  • Once the bucket is created, click on the bucket and select Upload option and choose Add Files to upload the VHD file.

Method 2: Using CLI to Upload VHD

To upload the VHD file to the AWS S3 bucket, users first have to configure the VHD file hosting system to be able to communicate with AWS. Users who have configured their system already can skip to "issue command" step of the following procedure.

  • Users need to download and install AWS CLI tools.
  • Once the tools are downloaded and installed, AWS CLI needs to be configured with user's Access Key ID and Secret Access Key. To do that, run the command aws configure and then follow the onscreen prompts to fill the necessary details.

    AWS Configure, LMI, LogLogic, AWS LMI



    Note: Every AWS user has a unique AWS Access Key ID and an AWS Secret Access Key. To know more about this, refer to AWS documentation on "Managing Access Keys"

     
  • Once the configuration is complete, users can then issue the command $ aws s3 cp "<location of the VHD file>" s3://<S3 Bucket Name>/<LMI VHD File name>.vhd 
    • Example: $ aws s3 cp "c:\lmi-eva-vhd-6.1.1.vhd" s3://loglogic-wiki-test/lmi-eva-vhd-6.1.1.vhd 
    • Output of this command will look as follows: Completed 107.5 MiB/5.2 GiB (850.8 KiB/s) with 1 file(s) remaining
  • Once the file is uploaded to the S3 bucket, it should be listed under the bucket as follows:

    VHD Uploaded

Creating the Role and the Trust Relationship

Once the Bucket is created and the VHD file is uploaded, the next step is to ensure the right Role and Trust relationship is configured in order to use the VHD file and deploy an EC2 instance. This article assumes that the users have this in place, as this is not a LogLogic specific step and is the same setup for all VM's that need to be deployed on AWS. For more information on how to set up, this refer to the AWS documentation on "Importing a VM as an Image Using VM Import/Export"

That article explains how to setup the Trust and Role relationship that's necessary for users to create Amazon Machine Images (AMI). 

Creating the AMI

Once the trust and role relationship are established, you can run the following command to create an AMI that can then be used to deploy an EC2 instance.

$aws ec2 import-image --cli-input-json "{ \"Description\":\"Description of the task\",\"DiskContainers\": [ { \"Description\":\"Test\", \"UserBucket\": { \"S3Bucket\": \"<Name of the VHD hosting S3 bucket>\",\"S3Key\":\"<Name of the file>.vhd\" } } ]}"

This above command as an example would look like this:

$aws ec2 import-image --cli-input-json "{ \"Description\":\"LMI EVA 6.1.1 2-8-17\",\"DiskContainers\": [ { \"Description\":\"Test\", \"UserBucket\": { \"S3Bucket\": \"loglogic-wiki-test\",\"S3Key\":\"lmi-eva-vhd-6.1.1.vhd\" } } ]}"

Once this command is executed, the conversion task begins, and a creation of AMI is started. The output of the above command would look like this:

{
     "Status": "active",
     "Description": "LMI EVA 6.1.1",
     "Progress": "2",
     "SnapshotDetails": [
         {
             "UserBucket": {
                 "S3Bucket": "loglogic-wiki-test",
                 "S3Key": "lmi-eva-vhd-6.1.1.vhd"
             },
             "DiskImageSize": 0.0
         }
     ],
     "StatusMessage": "pending",
     "ImportTaskId": "import-ami-ffqyiq1"
 }

 

To monitor and check the status of the conversion, use the ImportTaskId from the above output and run the command: $ aws ec2 describe-import-image-tasks --cli-input-json \ "{\"ImportTaskIds\":[\"<Your TaskId here>\"]}"

The output of this command would show you a status as follows:

Once the conversion is complete, an AMI is created and listed under Services->EC2->Images->AMIs page:

Note:  After the VHD is converted to an AMI (which is what the import-image subcommand will do) an automatic snapshot is created. That snapshot is listed under Services->Elastic Block Store->Snapshots. The snapshot size will be equivalent to the size of the EVA, which is 500GB.

Deploying an EC2 Instance

At this point, the AMI is available to be deployed as an EC2 instance. Go to Services > EC2 page and click on Launch Instance button. This should take users to a guided deployment page.

  1. Unde the choose AMI's step, select My AMI's pane from the list and select the AMI that was created with the LMI's 6.1.1 VHD file. 

  2. Under step 2, users can choose any Instance Type. The minimum requirement to be able to use Advanced Features is to have 16GB RAM and 8 cores CPU. 
  3. Under step 3, LMI doesn't require any changes to be made specifically.
  4. Under step 4, users can choose to add more storage to the instance if necessary. The default comes with 1 disk of 500GB size. 
  5. Step 5 requires no additional information for LMI's deployment.
  6. Step 6, is where users would add their Public IP's, as a Rule, to ensure they are able to reach that VM. To understand more about "Security Groups" refer to the following AWS documentation page.
  7. For Step 7, review the configuration and if everything is set correctly, click the Launch button to deploy the EC2 instance.

At this point user is prompted to create an SSH key pair as follows:

Users can choose the option Proceed without a key pair and continue on to Launch the instance. LMI EVA already has an SSH keypair generated for which the public key is added to the users authorized key list upon connecting the first time (just like any other LMI instance).

Once the deployment is finished, users should be able to see the EC2 instance listed under Services->EC2->Instances->Instances. Users should now be able to SSH to the Public IP of this server and should be able to use LMI's Web UI. 


Additional Resources

To learn more about how to use LogLogic LMI to manage your Logs and please refer to our documentation at https://docs.tibco.com/products/tibco-loglogic-log-management-intelligence and watch our tutorial videos on https://www.youtube.com/LogLogic

Refer to TIBCO KB Article 000030466 for S3 NoSuchBucket errors. Refer to TIBCO KB Article 000030465 for region issues. Refer to TIBCO KB Article 000030469 for vmimport issues.

If there are any general questions regarding the use of these LogLogic products please post your questions to https://legacycommunity.tibco.com/answers/product/701891 and for issues that require a support case please open a case with us at https://support.tibco.com