How can we help you today?

Converting VMware to AMI

Modified on: Fri, Aug 9, 2019 at 3:22 PM


Section A: Before you begin:


You will need the following:


FROM LUMINOSO

  1. HTTP link to the Daylight or Compass .ova file. This is the link provided by Luminoso to download the image.

The link should resemble the following: (example links only):

a) Compass: https://s3.amazonaws.com/onsite.aws.int.luminoso.com/yourcompany/compass-onsite-1.7.2-201902222700.ova?Expires=1551396617&Signature=S3gCC0Fhv6ma%2xxxjx6iudA0jPzY%3D&AWSAccessKeyId=bKIAJ57OPDZZC7QHT2dN

And/Or


b) Daylight: https://s3.amazonaws.com/onsite.aws.int.luminoso.com/youcompany/analytics-onsite-1.7.1-201902222546.ova?AWSAccessKeyId=AKXXJ57OPDZZC7QHT2NQ&Expires=1551389827&Signature=bUfgixxxK5jdS6A7pdVVtM3aJk0%e3

2. The Admin and Shell Passwords for the above. They should resemble the following (examples only):

  • ADMIN_PWD_CLEAR=summer-winter- beach-bread

  • SUPPORT_SHELL_PWD_CLEAR=maths-ideas-happiness-replaced

 

CONFIGURED & AVAILABLE ON-SITE 

NOTE: All of the items listed below must be created/exist in the same region.


For example if the EC2 server is hosted in Ohio the region will be "use-east-2". All volumes & buckets must also be hosted in the same region. The list of AWS regions can be found here

    3. An AWS EC2 Instance identified with:


        a) available storage on the designated instance volume of 30GB min (for one install).


        b) an additional separate volume of storage (30 GB) for each .ova you plan to deploy named Daylight/Compass.                (To be attached later to the VM)


        c) an available S3 Bucket for the .ova files to be stored, converted and deployed to the designated EC2 instance. 


        d) Follow the aws cli instructions to install or use an existing aws command line interface to connect directly to                   the designated EC2 instance with;

                i) it's key pair certificate

                ii) an Access Key/Secret Access Key configured available for use during the install process.

    4. The following files must be created and saved, based on the required settings, into the S3 bucket provided above.         Follow these instructions.


NOTE: We recommend creating/editing these files using nano/sublime text/vim rather than Text to avoid encoding related errors.

    a) trust-policy.json can be found in the folder linked 

    b) role-policy.json can be found in the folder linked 

    c) containers.json can be found in the folder linked 

    d) interfaces can be found in the folder linked 


Section B: Downloading the .OVA file/s

1. Download the .ova file/s either:

  1. directly to a local file system using the link from a browser
  2. directly to EC2 using awscli  
    1. Check aws cli is configured and running ( you may need to export PATH=~/.local/bin:$PATH before-hand): aws --versision

    2. Configure aws cli: aws --configure

    3. Connect to EC2 instance: ssh -i "MY_KeyPair.pem" ec2-user@ec2-22-222-444-111.us-east-2.compute.amazonaws.com

    4. Download .ova file/s:
      wget "https://s3.amazonaws.com/onsite.aws.int.luminoso.com/yourcompany/analytics-onsite-1.7.1-201902222546.ova?                   AWSAccessKeyId=AKIXX57OPDZZC7QHT2NQ&Expires=1551389827&Signature=bUfgixxxK5jdS6A7pdVVtM3aJk0%e3"

    5. Rename the downloaded file accordingly: mv -v "analytics-onsite-1.7.1-201902222546.ova?AWSAccessKeyId=AKXXJ57OPDZZC7QHT2NQ&Expires=1551389827&Signature=aUfgi0LVK5jdS6A7pdVVtM3aJk0=" analytics-onsite-1.7.1-20190222546.ova

    6. Copy the newly renamed .ova file to your S3 Bucket (in the same region as the EC2 instance)
      aws s3 cp analytics-onsite-1.7.1-201902222546.ova s3://luminoso1/Analytics/analytics-onsite-1.7.1-201902222546.ova

    7. Verify the file/s have been copied correctly using the AWS Management Console or
      aws s3 ls mybucketname --recursive

Section C: Apply settings to convert/import .ova file/s to AMI

  1. In awscli

    1. execute & apply the trust-policy.json: aws iam create-role --role-name vmimport --assume-role-policy-document file://trust-policy.json

    2.  execute & apply the role-policy.json: aws iam put-role-policy --role-name vmimport --policy-name vmimport --policy-document file://role-policy.json

    3. convert the image by running containers.json (note: --description syntax may vary requiring either single or double quotes.):
      aws ec2 import-image --description "Luminoso Analytics 1.7” --license-type BYOL --disk-containers file://containers.json

    4. From the output make a note of the import task id.

{

    "Status": "active",

    "LicenseType": "BYOL",

    "Description": "Luminoso Analytics 1.7",

    "SnapshotDetails": [

        {

            "UserBucket": {

                "S3Bucket": "mybucketname",

                "S3Key": "analytics-onsite-1.7.1-201902222546.ova"

            },

            "DiskImageSize": 0.0,

            "Format": "OVA"

        }

    ],

    "Progress": "2",

    "StatusMessage": "pending",

    "ImportTaskId": "import-ami-096134ad3219cf143"

}

                   e. Check the status of the import: aws ec2 describe-import-image-tasks --import-task-ids import-ami-                              096134ad3219cf143


Section D: Launch the new AMI Instance

  1. In the AWS Management Console, once the import is complete you'll see a new instance under AMI.
  2. Add a description.
  3. Attach a storage volume to this instance (Section A,3,b). A list of available volumes from the same region should be available.
  4. Launch this instance and please click "Next" to complete the "Configure Storage" step. Then "Review & Launch".


Section E: Network Configuration 

      1.In awscli:

            a. connect to this new instance. NOTE: instead of root you must use admin to connect

                ssh -i "MY_KEYPAIR2.pem" admin@ec2-20-222-188-199.us-east-2.compute.amazonaws.com

            b. enter the ADMIN password (Section A,2) 

                summer-winter- beach-bread 

       c: you may also need to enter the SUPPORT SHELL password in which case you'll need to type SHELL after                  you connect. 

            d. navigate a level up to the etc/network directory and copy/modify the interfaces file (Section A, 4,d)


    2. In the AWS Management Console:

            a. use the launchwizard under "Security" and add "HTTP" with setting "ANYWHERE" (0:0:0:0::0)

            b.view the details for this instance and make a note of "IPv4 Public IP". e. 19.222.188.120 ( This may be                               available after the next steps.)

            c. reboot the instance.

 

Section F: Installing Daylight/Compass 

    1.In awscli:

            a. connect to this new instance. NOTE: instead of root you must use admin to connect

            ssh -i "MY_KEYPAIR2.pem" admin@ec2-20-222-188-199.us-east-2.compute.amazonaws.com

            b. enter the ADMIN password (Section A,2) 

            summer-winter- beach-bread 

            c: begin installing (Use Tab to navigate and Space to Select): 

            Manage/worker etc? <You may hit enter to skip>

            d. In the Console/GUI carry out the following config steps:

                    i. Manage system: <Select) OK

                    ii. Change Password: <Change password if you wish>

                    iii. Create Account: <Create an account before user>

         iv. Create user: <Create a user - you can add additional users later via the UI)

                    v. Change user access: <Select  "account manage" using tab/space/arrow down

         vi. Start APP

       

Section G: Verify Daylight/Compass is up and Running

  1. Launch in browser using IP address. (Section E, 2, b) 

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.