Amazon Elastic Compute Cloud

Posted on by harishrao2835

Amazon Elastic Compute Cloud (Amazon EC2) is a web service that provides resizeable computing capacity (i.e.: virtual servers) in Amazon’s data centers. These virtual severs are known as Amazon EC2 instances. You will create and launch the EC2 instances required to host the WebCenter system.

EC2 is a pay-as-you-go cloud platform that includes compute power, storage and database services as its core components. Users select the CPU, memory, storage, networking capacity and access controls, OS, security, and additional software needed to run a virtual computing environment, or instance.

Amazon offers preconfigured, templated Amazon Machine Images (AMIs), or users can create their own images. Administrators determine when to start, terminate and monitor as many instances as they need, depending on workloads. They can also run instances in multiple locations, use static IP endpoints or attach persistent block storage.

Using AWS EC2 can reduce the time needed to obtain and boot new server instances to minutes, allowing you to quickly scale capacity — both up and down — as computing requirements change. Amazon EC2 allows companies to pay only for the computing resources and capacity they use. It provides developers the tools to build failure-resilient applications and isolate them from common failure scenarios.

Create an Amazon Linux Instance From an Amazon Machine Image

First we need to open EC2 service in the Amazon Web Services and launch instance to create Amazon Linux Instance from an Amazon Machine Image. Here, we are creating Linux machine which configures automatically we need to select basic options like processors, hard disk memory.

2016-01-12

This interface attaches public DNS automatically, we need to copy that public DNS and the name of public DNS is like “ec2-54-201-40-206.us-west-2.compute.amazonaws.com”. We need to connect to this DNS server with the given user name using Putty.exe through SSH connection. For authentication it needs private key, this EC2 key pair private key was provided by the Amazon only (we can get this in the LAB site only from “Download PPK/PEM”).

Connect to Your Instance

There are several ways to connect to a Linux instance. We will connect using your browser. Alternatively, you can connect using PuTTY or an SSH client. For more information, seeConnecting to Your Linux Instance from Windows Using PuTTY or Connecting to Your Linux Instance Using SSH.

To connect to your Linux instance using a web browser

  1. You must have Java installed and enabled in the browser. If you don’t have Java already, you can contact your system administrator to get it installed.
  2. From the Amazon EC2 console, click Instances in the navigation pane.
  3. Select the instance, and then choose Connect.
  4. Choose A Java SSH client directly from my browser (Java required).
  5. Amazon EC2 automatically detects the public DNS name of your instance and populates Public DNS for you. It also detects the key pair that you specified when you launched the instance. Complete the following, and then click Launch SSH Client.
    1. In User name, enter ec2-user.
    2. In Private key path, enter the fully qualified path to your private key (.pem) file, including the key pair name.
    3. (Optional) Choose Store in browser cache to store the location of the private key in your browser cache. This enables Amazon EC2 to detect the location of the private key in subsequent browser sessions, until you clear your browser’s cache.
  6. If necessary, choose Yes to trust the certificate, and choose Run to run the MindTerm client.
  7. If this is your first time running MindTerm, a series of dialog boxes asks you to accept the license agreement, confirm setup for your home directory, and confirm setup of the known hosts directory. Confirm these settings.
  8. A dialog prompts you to add the host to your set of known hosts. If you do not want to store the host key information on your local computer, choose No.
  9. A window opens and you are connected to your instance.

    Note

    If you chose No in the previous step, you’ll see the following message, which is expected:

    Verification of server key disabled in this session.

If you can’t connect to your instance, see Troubleshooting Connecting to Your Instance for assistance.

Thanks for viewing the Blog.

Leave a comment