Skip to content
This repository was archived by the owner on Aug 7, 2025. It is now read-only.

Latest commit

 

History

History
290 lines (199 loc) · 9.62 KB

File metadata and controls

290 lines (199 loc) · 9.62 KB

|CL-ATTR| on Amazon Web Services*

This tutorial explains how to create and launch a |CL| :abbr:`AMI (Amazon Machine Image)` instance from the :abbr:`AWS\* (Amazon Web Services)` console and complete the following tasks:

  1. Locate and select the |CL| OS Basic AMI in the AWS Marketplace.
  2. Create a new public and private key pair to allow you to connect to your |CL| instance securely.
  3. Launch the new |CL| instance and connect to it.
  4. Update your instance of |CL| using the :command:`swupd` command.
  5. Stop the |CL| instance.

This tutorial assumes the following statements are true:

  • You are using a linux-based system to access AWS and can run :command:`SSH` to access the remote |CL| AWS image.
  • Your browser puts downloaded files in the :file:`$HOME/Downloads` directory.
  • You have already set up an AWS user account and logged into the AWS console.

Note

This tutorial uses a |CL| AMI t2.micro instance that is eligible for the AWS free tier. To learn more about AWS and setting up an account, visit the AWS website at http://aws.amazon.com.

  1. Start from your main AWS services console menu in your browser and select the :guilabel:`EC2` text as shown in Figure 1:

    This selection brings up your :guilabel:`EC2 Dashboard` menu.

  2. To create a new |CL| instance from the :guilabel:`EC2 Dashboard` menu, select the :guilabel:`Launch Instance` button as shown in Figure 2:

    This selection takes you to the :guilabel:`Step 1: Choose an Amazon Machine Image (AMI)` menu.

  3. To find the :guilabel:`Clear Linux OS Basic` AMI in the :guilabel:`Step 1: Choose an Amazon Machine Image (AMI)` menu, do the following:

    1. In the lefthand navigation window, select the :guilabel:`AWS Marketplace` menu item to bring up the search bar to :guilabel:`Search AWS Marketplace Products`.

    2. In the search bar, type "clear linux os" and press the Enter key to search for and locate the :guilabel:`Clear Linux OS Basic` AMI.

    3. Select the :guilabel:`Clear Linux OS Basic` AMI by clicking the :guilabel:`Select` button as shown in Figure 3:

    4. A pop-up dialog box appears showing you more information about the :guilabel:`Clear Linux OS Basic` AMI along with the pricing details for running |CL| on different platform configurations as shown in Figure 4. Select the :guilabel:`Continue` button.

  4. The :guilabel:`Choose Instance Type` menu appears as shown in Figure 5.

    Select the :guilabel:`t2.micro` type by clicking the box on the left side of the instance and then select the :guilabel:`Review and Launch` button to move to the :guilabel:`Step 7: Review the Instance Launch` menu.

    Note

    You can configure the instance details, add additional storage, add tags, and configure the security group before selecting the :guilabel:`Review and Launch` button if you want to further customize this |CL| instance.

  5. The :guilabel:`Step 7: Review the Instance Launch` menu, shown in Figure 6, allows you to :guilabel:`Cancel` the process, return to the :guilabel:`Previous` screen to change the configuration or :guilabel:`Launch` the instance defined.

    1. Select the :guilabel:`Launch` button. A dialog box appears, as shown in Figure 7, asking you to :guilabel:`Select an existing key pair or create a new pair`.

      1. Select the :guilabel:`Create a new key pair` option.

      2. For the :guilabel:`Key pair name` field, enter AWSClearTestKey.

      3. Select the :guilabel:`Download Key Pair` button to download the :file:`AWSClearTestKey.pem` to your browser's defined :file:`Downloads` directory.

      4. When the file finishes downloading, select the :guilabel:`Launch Instances` button to proceed to the :guilabel:`Launch Status` menu shown in Figure 8.

    2. Once the :guilabel:`Launch Status` page changes to what is shown in Figure 9, select the :guilabel:`View Instances` button to view your :guilabel:`Instances` dashboard.

Your :guilabel:`Instances` Dashboard is shown in Figure 10 with the new |CL| OS basic instance already selected and in the running state. If there are other instances available, they are also listed but not selected.

  1. To connect to your running instance, click the :guilabel:`Connect` button located at the top of your dashboard. AWS brings up the pop-up dialog box shown in Figure 11 describing how to connect to your running instance.
  1. Open a terminal on your system. You should be in your :file:`$HOME` directory.

  2. Copy the previously downloaded keyfile from the :file:`Downloads` directory to the current directory.

    cp Downloads/AWSClearTestKey.pem .
  3. Change the attributes of the :file:`AWSClearTestKey.pem` using the :command:`chmod` command as instructed in the dialog box shown in Figure 11.

    chmod 400 AWSClearTestKey.pem
  4. Copy the text highlighted in the :guilabel:`Example:` section that is shown in :ref:`figure 11<fig-aws-web-11>`. Paste the copied text into your terminal, change the text before the @ sign to the username clear, and press the Enter key to execute the command.

    ssh -i "AWSClearTestKey.pem" clear@ec2-34-209-39-184.us-west-2.compute.amazonaws.com
  5. A message appears on the terminal stating the authenticity of the host can't be established and prompts you with the message:

    The authenticity of host 'ec2-34-209-39-184.us-west-2.compute.amazonaws.com (34.209.39.184)' can't be established.
    ECDSA key fingerprint is SHA256:LrziT5Ar66iBTfia8qmiIsrfBUm/UGam76U8bDR6yJc.
    Are you sure you want to continue connecting (yes/no)?
  6. Type yes and press the Enter key. Another warning is printed to the terminal and you are now at the command prompt of your new |CL| instance.

    Warning: Permanently added 'ec2-34-209-39-184.us-west-2.compute.amazonaws.com,34.209.39.184' (ECDSA) to the list of known hosts.
    clear@clr-96a8565d0ca54b0c80364a1e5e7b0f88 ~ $

Run the :command:`sudo swupd update` command to update the operating system as shown in Figure 12:

In this example, we updated from version 18940 to 19100.

Stop the |CL| instance

When you are finished using your AWS |CL| instance, you must stop it using the :guilabel:`Instances` dashboard to stop accruing charges. Complete the following steps from the :guilabel:`Instances` dashboard to stop your AWS |CL| instance from running.

  1. Select the :guilabel:`Actions` button to bring up a pull-down menu.

  2. Select the :guilabel:`Instance State` menu item to expand the options.

  3. Select :guilabel:`Stop` menu item to shut down the running instance.

    Figure 13 illustrates these steps.

  4. A pop-up dialog box appears warning you that any ephemeral storage of your instance will be lost. Select the :guilabel:`Yes, Stop` button to stop your |CL| instance.

Congratulations! You are up and running with |CL| on AWS. To see what you can do with your |CL| instance, visit our :ref:`tutorials <tutorials>` section for examples on using your |CL| system.