Skip to content

Getting Started

The Sunlight Infrastructure Dashboard can be used to manage sunlight cluster instances. It provides a single pane of glass to manage and monitor resources, and even deploy clusters on demand for the right infrastructure plugin such as on AWS baremetal nodes. It can be deployed instantly on-demand in AWS and be up and running within minutes.

Sunlight on AWS Dashboard Deployment

The Sunlight on AWS Dashboard is a Sunlight-prepared AMI image.

It is fully prepared as an AMI and includes all the necessary tools to run the Sunlight Infrastructure Manager. These tools include:

  • Nginx (in order to serve the UI part of the SIM)
  • Mysql (stores user data)
  • Nodejs (is is used to run the server/client side of the UI)
  • Pm2 (it is used to manage the server side of the UI)
  • Python (it is used to run the API of the SIM)
  • Letsencrypt (it is used in the case of securing a domain name)

The Sunlight on AWS Dashboard AMI is available through the AWS marketplace as a free AMI.

Creating a Sunlight on AWS Dashboard VM

To deploy a Dashboard VM the user just has to select the AMI from the AWS marketplace images (using either the AWS Console, or AWS cli/api).

The user must make sure that the http, https and ssh services are allowed in the Network Security Group configuration.

The following steps will help in running your first Sunlight Infrastructure Manager:

STEP 1

As soon as the VM is built, the user will have to assign an elastic IP to that VM. At this stage we can see the Infrastructure Manager UI via this IP but we will be logging in via a non https (secure) connection. The objective in this step is to assign/create a domain or a subdomain pointing to the elastic IP of this new VM, so that it will allow us to create an SSL certificate pair (issued by let’s encrypt). This way we will have a secured (https) connection to the UI of the Infrastructure Manager UI, thus encrypting the communication between a web client and the UI.

To generate an SSL cert you must create a domain/subdomain entry via your DNS service. If you are unfamiliar with DNS record assingment, please contact the Sunlight support team for assistance.

It is suggested that you wait for full DNS propagation before attempting to run step 2, to avoid ssl issue problems, otherwise you can continue using the IP address assigned.

So for step 1:

  • Go into your AWS ec2 dashboard and allocate a new (or use an existing) Elastic IP
  • Through the AWS ec2 dashboard associate the Elastic IP address to the Sunlight_on_AWS_dashboard instance
  • Make a note of the AWS INSTANCE ID given to the new Sunlight_on_AWS_dashboard instance

Once the DNS change has concluded and the records have propagated, then by visiting the domain/subdomain used and assigned to the elastic IP, should resolve and display on your web browser a sunlight.io default UI login web page via the HTTP protocol.

The following screen should appear

aws infrastructure manager login

Using the default username is required. The default username is sunlight

The password for your first time login is the randomised AWS INSTANCE ID of the new instance that you copied above from your aws manager.

The system immediatey redirects the user to change his/her default password:

aws infrastructure manager password change

After a succesful password change the system redirects the user to login again.

With a changed password, the user should now be able to login and view the main dashboard.

STEP 2

At this step the user should proceed to settings in order to input the domain/subdomain assigned to the elastic IP and configure the manager to respond under https to that domain/subdomain url request.

So clicking on settings:

aws infrastructure manager settings

The important configuration step here is to insert the domain/subdomain chosen in step 1

aws infrastructure manager secure domain

If this step concludes succesfully then your web browser URL will be changed to the one just secured and the Sunlight Infrastructure Manager will be available under a https connection.

At this point there are two types of Sunlight infrastructure clusters that you can now manage via the SIM:

(1.) On-premise clusters that can be accessed from the SIM via a secure tunnel.

You are not required to input AWS access credentials

(2.) Deploy Sunlight clusters on-demand in AWS. You will need to setup IAM role permissions for your SIM instance in order to enable this as described below:

Following is a sample policy to be applied to the IAM role. You must enter this into the IAM wizard for the SIM instance that you have deployed:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "s3:*",
                "ec2:*"
            ],
            "Resource": "*"
        }
    ]
}

BE ADVISED, that providing secret access keys is not a suggested option

You can find more information regarding IAM roles and how to configure them from the following AWS link: IAM Roles for Amazon EC2 - Amazon Elastic Compute Cloud


Sunlight Platform Deployment

Now you are ready to start deploying and managing Sunlight hypervisor resources. Please review individual userguides for information on how to achieve this in each environment found here.

The Sunlight support team is on stand by to assist with any installation and configuration issues you may encounter. Link : support portal