{"id":571,"date":"2021-07-23T12:33:09","date_gmt":"2021-07-23T12:33:09","guid":{"rendered":"https:\/\/ssdsunucum.com\/blog\/amazon-aws-instance-management\/"},"modified":"2021-07-23T12:33:09","modified_gmt":"2021-07-23T12:33:09","slug":"amazon-aws-instance-management","status":"publish","type":"post","link":"https:\/\/ssdsunucum.com\/blog\/amazon-aws-instance-management\/","title":{"rendered":"Amazon AWS Instance Management"},"content":{"rendered":"<\/p>\n<div class=\"col-md-9\">\n<div class=\"flex-column flex-md-row article-header\"><\/div>\n<hr>\n<h2 id=\"overview\">Overview<\/h2>\n<p>After you create an instance with the cPanel &#038; WHM Amazon Machine Image\u2122 (AMI), you can manage that instance from within the Amazon Web Services\u2122 (AWS) Management Console. This document describes common instance-management tasks that your cPanel &#038; WHM instance may require.<\/p>\n<div class=\"callout callout-info\">\n<div class=\"callout-heading\">Note:<\/div>\n<div class=\"callout-content\">\n<ul>\n<li>For more information about AWS instance management, read Amazon\u2019s\u00ae Working with the AWS Management Console documentation.<\/li>\n<li>AWS systems may encounter package conflicts when the system attempts to update certain libraries (generally, <code>libstdc++<\/code> libraries). These errors occur due to the way in which AWS manages packages. To resolve this issue, use the <code>yum remove<\/code> or <code>rpm -e<\/code> commands to remove the conflicting package.<\/li>\n<li>For video tutorials about this process, view the cPanel and Amazon AWS playlist on our YouTube channel.<\/li>\n<\/ul><\/div>\n<\/div>\n<h2 id=\"access-your-instance-for-the-first-time\">Access your instance for the first time<\/h2>\n<div class=\"callout callout-info\">\n<div class=\"callout-heading\">Note:<\/div>\n<div class=\"callout-content\">\n<ul>\n<li>To improve security for your system, the cPanel &#038; WHM AMI automatically runs the <code>\/usr\/local\/cpanel\/upcp<\/code> script after the instance initializes. This script may alter the AMI\u2019s version number. Also, the WHM interface may display a license error if you click any update links while the update script runs as a background task.<\/li>\n<li>New instances may require several minutes to initialize. Until the initialization process finishes, the <em>Status Checks<\/em> column of the EC2\u2122 Management Console will display <em>Initializing<\/em> and an hourglass icon.<\/li>\n<\/ul><\/div>\n<\/div>\n<p>To access a new instance, perform the following steps:<\/p>\n<ol>\n<li>\n<p>Sign in to your AWS account.<\/p>\n<\/li>\n<li>\n<p>From the <em>Services<\/em> menu in the top-left corner, select <em>EC2 under Compute<\/em>. The <em>EC2 Management Console<\/em> will appear.<\/p>\n<\/li>\n<li>\n<p>In the left-side menu under <em>Instances<\/em>, click <em>Instances<\/em>. The list of instances will appear.<\/p>\n<\/li>\n<li>\n<p>In the list of instances, or at the bottom of the interface in the <em>Description<\/em> tab, locate the following values:<\/p>\n<ul>\n<li>\n<p><em>Public DNS (IPv4)<\/em> \u2014 The public DNS address for the instance.<\/p>\n<div class=\"callout callout-warning\">\n<div class=\"callout-heading\">Important:<\/div>\n<div class=\"callout-content\">\n<p>You <strong>must<\/strong> set the hostname correctly before you can license the server.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n<li>\n<p><em>Key Name (Key pair name in the Description tab)<\/em> \u2014 The name of the key pair that you used when you created the instance.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<li>\n<p>To connect to the instance via SSH, run the following command, where <code>example<\/code> represents the key pair name and <code>IPADDRESS<\/code> represents the public DNS address:\n<\/p>\n<div class=\"highlight\">\n<pre style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"><code class=\"language-bash\" data-lang=\"bash\">ssh -i <span style=\"color:#e6db74\">\"~\/.ssh\/example.pem\"<\/span> centos@IPADDRESS<\/code><\/pre>\n<\/div>\n<\/li>\n<li>\n<p>To escalate to the <code>root<\/code> account, run the <code>sudo su<\/code> command.<\/p>\n<\/li>\n<li>\n<p>To change the <code>root<\/code> user\u2019s password, run the <code>passwd<\/code> command. The system will prompt you to enter a new password.<\/p>\n<\/li>\n<li>\n<p>Enter the desired password and press <em>Enter<\/em>. The system will prompt you to confirm the password.<\/p>\n<\/li>\n<li>\n<p>Reenter the desired password and press <em>Enter<\/em>. A confirmation message will appear.<\/p>\n<\/li>\n<li>\n<p>If you wish to access WHM in your browser, perform the following additional steps:<\/p>\n<ol>\n<li>\n<p>Navigate to the following address, where <code>IPADDRESS<\/code> represents the public DNS address:\n<\/p>\n<div class=\"highlight\">\n<pre style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"><code class=\"language-bash\" data-lang=\"bash\">https:\/\/IPADDRESS:2087<\/code><\/pre>\n<\/div>\n<div class=\"callout callout-warning\">\n<div class=\"callout-heading\">Important:<\/div>\n<div class=\"callout-content\">\n<p>The cPanel &#038; WHM AMI\u2019s cPanel-provided security group <strong>only<\/strong> allows connections via HTTPS.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n<li>\n<p>Use the <code>root<\/code> password to log in to the WHM interface as the <code>root<\/code> user.<\/p>\n<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<div class=\"callout callout-cpanel\">\n<div class=\"callout-heading\">More:<\/div>\n<div class=\"callout-content\">\n<p>For more information, read our How to Access the Command Line and How to Log in to Your Server or Account documentation.<\/p>\n<\/p><\/div>\n<\/div>\n<h2 id=\"manage-instances\">Manage instances<\/h2>\n<div class=\"callout callout-warning\">\n<div class=\"callout-heading\">Important:<\/div>\n<div class=\"callout-content\">\n<ul>\n<li>We <strong>strongly<\/strong> recommend that you stop unused instances to avoid unnecessary costs.<\/li>\n<li>If you stop an instance, Amazon retains the instance\u2019s basic information, but removes some data. For example, when you restart the instance, AWS will generate a new DNS hostname and IP address.<\/li>\n<\/ul><\/div>\n<\/div>\n<p>To start, stop, reboot, or terminate an instance, perform the following steps:<\/p>\n<ol>\n<li>\n<p>Sign in to your AWS account.<\/p>\n<\/li>\n<li>\n<p>From the <em>Services<\/em> menu in the top-left corner, select <em>EC2 under Compute<\/em>. The <em>EC2 Management Console<\/em> will appear.<\/p>\n<\/li>\n<li>\n<p>In the left-side menu under <em>Instances<\/em>, click <em>Instances<\/em>. The list of instances will appear.<\/p>\n<\/li>\n<li>\n<p>Select the desired instance from the list.<\/p>\n<div class=\"callout callout-info\">\n<div class=\"callout-heading\">Note:<\/div>\n<div class=\"callout-content\">\n<p>To update multiple instances, select all of the desired instances.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n<li>\n<p>At the top of the list of instances, click <em>Actions<\/em>. The <em>Actions<\/em> menu will display.<\/p>\n<\/li>\n<li>\n<p>Select the desired setting from the <em>Instance State<\/em> menu:<\/p>\n<ul>\n<li>\n<p><em>Start<\/em> \u2014 Restart the instance, which you <strong>must<\/strong> have previously stopped.<\/p>\n<\/li>\n<li>\n<p><em>Stop<\/em> \u2014 Pause the instance and retain some, but not all, of its data.<\/p>\n<\/li>\n<li>\n<p><em>Reboot<\/em> \u2014 Reboot the instance.<\/p>\n<\/li>\n<li>\n<p><em>Terminate<\/em> \u2014 Permanently delete the instance.<\/p>\n<div class=\"callout callout-danger\">\n<div class=\"callout-heading\">Warning:<\/div>\n<div class=\"callout-content\">\n<p>When you terminate an instance, the system will delete the instance\u2019s data.<\/p>\n<ul>\n<li>Termination will <strong>not<\/strong> delete EBS volumes unless you enable the <em>Delete on Termination<\/em> setting.<\/li>\n<li>You <strong>cannot<\/strong> restore a terminated instance.<\/li>\n<\/ul><\/div>\n<\/div>\n<p> A confirmation message will appear. Confirm your action. The system may require several minutes in order to stop or terminate the instance.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<p>The <em>Instance State<\/em> column in the list of instances displays the instance\u2019s state and the following status icons:<\/p>\n<ul>\n<li>\n<p>A green icon \u2014 The system has successfully started the instance.<\/p>\n<\/li>\n<li>\n<p>A yellow icon \u2014 An action is in progress.<\/p>\n<\/li>\n<li>\n<p>A red icon \u2014 The system has successfully stopped or terminated the instance.<\/p>\n<div class=\"callout callout-warning\">\n<div class=\"callout-heading\">Important:<\/div>\n<div class=\"callout-content\">\n<p>After you terminate an instance, that instance will <strong>only<\/strong> remain in the list of instances until you refresh the list.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n<\/ul><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Overview After you create an instance with the cPanel &#038; WHM Amazon Machine Image\u2122 (AMI), you can manage that instance from within the Amazon Web Services\u2122 (AWS) Management Console. This document describes common instance-management tasks that your cPanel &#038; WHM instance may require. Note: For more information about AWS instance management, read Amazon\u2019s\u00ae Working with &hellip;<\/p>\n","protected":false},"author":1,"featured_media":572,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/571"}],"collection":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/comments?post=571"}],"version-history":[{"count":0,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/571\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media\/572"}],"wp:attachment":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media?parent=571"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/categories?post=571"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/tags?post=571"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}