Importing into AWS

Note: By default, LogLogic EVA for AWS is configured for DHCP, which is the recommended configuration when running in AWS. However, settings such as NTP server and time can be configured as applicable.

Prerequisites

  • Download the LogLogic EVA TIB_logeva_<version>_vhd.zip archive that contains the lmi-eva-vhd-<version>.vhd file.
  • AWS Import/Export Tools: AWS Command Line Interface (AWS CLI). See
  • An AWS Identity and Access Management (IAM) role, with permissions in your IAM policy to use VM Import/Export for S3.

    See Required Permissions for IAM Users

    Note: For more information on creating a service role and setting the required permissions, see the article #000030469 on the TIBCO Support website.
  • AWS Security Group with at least the following ports allowed:
    • All ICMP | ALL
    • DNS | UDP | 53
    • HTTP | TCP | 80
    • HTTPS | TCP | 443
    • HTTPS | TCP | 4443
    • SSH | TCP | 22
      Note: Depending on the features used, additional ports might be required. See TIBCO LogLogic® Log Management Intelligence Administration Guide for a list of ports and assignments.

      To use LogLogic LMI Forwarding you must disable source and destination checking on your LogLogic EVA Network Interfaces. See Changing the Source/Destination Checking.

  • An Amazon Virtual Private Cloud (Amazon VPC) defined with a private IP range.

    See Private IPv4 Addresses and Internal DNS Hostnames

  • A static private IPv4 address from the VPC range of your subnet for the primary IP:

    See the Network Interfaces section under Launching an Instance.

Procedure

  1. Upload the lmi-eva-vhd-<version>.vhd file to an S3 bucket. This can be done either via the AWS Web Console or via the AWS CLI using the aws s3 command. For example: 
    aws s3 cp lmi-eva-vhd-<version>.vhd s3://<s3bucketname>/lmi-eva-vhd-<version>.vhd
  2. Using the AWS CLI, run the aws ec2 import-image command to import the vhd image to an AWS Amazon Machine Image (AMI). 
    aws ec2 import-image --cli-input-json "{  \"Description\": \"<DESCRIPTION>\", \"DiskContainers\": [ { \"Description\": \"First CLI task\", \"UserBucket\": { \"S3Bucket\": \"<S3BUCKETNAME>\", \"S3Key\" : \"<EVAIMAGENAME>\" } } ]}"

    For example, using the following command: 

    >aws ec2 import-image --cli-input-json "{  \"Description\": \" LMI EVA IMAGE \", \"DiskContainers\": [ { \"Description\": \"First CLI task\", \"User Bucket\": { \"S3Bucket\": \" my-eva-bucket \", \"S3Key\" : \" lmi-eva-vhd-6.1.0.vhd \" } } ]}"

    produces the following output: 

    {
    "Status": "active",
    "Description": "LMI EVA Image",
    "Progress": "2",
    "SnapshotDetails": [
        {
            "UserBucket": {
                "S3Bucket": "my-eva-bucket",
                "S3Key": "lmi-eva-vhd-6.1.0.vhd"
            },
            "DiskImageSize": 0.0
        }
    ],
    "StatusMessage": "pending",
    "ImportTaskId": "import-ami-fgs8pjvt"
}
  3. Note the value of ImportTaskId because it can be used with the aws ec2 describe-import-image-tasks command to check the process of the import. 
    aws ec2 describe-import-image-tasks --import-task-id <IMPORTTASKID>

    For example, using the following command: 

    > aws ec2 describe-import-image-tasks --import-task-id "import-ami-fgs8pjvt"

    produces the following output: 

    {
    "ImportImageTasks": [
        {
            "Status": "active",
            "Description": "LMI EVA IMAGE",
            "Progress": "28",
            "SnapshotDetails": [
                {
                    "UserBucket": {
                        "S3Bucket": "my-eva-bucket",
                        "S3Key": "lmi-eva-vhd-6.1.0.vhd"
                    },
                    "DiskImageSize": 5633254400.0,
                    "Description": "First CLI task",
                    "Format": "VHD"
                }
            ],
            "StatusMessage": "converting",
            "ImportTaskId": "import-ami-fg3kce60"
        }
    ]
}
  4. After the job completes, login to the AWS console and view the completed import under EC2 > IMAGES > AMI.

Result

You can identify your new LogLogic EVA AMI by the AMI name, which should be the same as the ImportTaskId.

What to do next

You can launch the LogLogic EVA AMI and configure it by using the CLI interface via ssh.