Configuring and Monitoring Amazon EC2. eg Enterprise v5.6

Transcription

1 Configuring and Monitoring Amazon EC2 eg Enterprise v5.6

2 Restricted Rights Legend The information contained in this document is confidential and subject to change without notice. No part of this document may be reproduced or disclosed to others without the prior permission of eg Innovations, Inc. eg Innovations, Inc. makes no warranty of any kind with regard to the software and documentation, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Trademarks Microsoft Windows, Windows NT, Windows 2000, Windows 2003 and Windows 2008 are either registered trademarks or trademarks of Microsoft Corporation in United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. Copyright 2012 eg Innovations, Inc. All rights reserved.

3 Table of Contents CONFIGURING AND MONITORING AWS EC2 CLOUD PRE-REQUISITES FOR MONITORING THE AWS EC2 CLOUD Configuring the eg agent with the required software Pricing details of the Amazon EC2 Instances Amazon Cloudwatch is a Paid service Obtaining an Access key and Secret key ADMINISTERING THE EG MANAGER TO MONITOR THE AWS EC2 CLOUD MONITORING THE AWS EC2 CLOUD...5 CONFIGURING AND MONITORING AWS EC2 REGION ADMINISTERING THE EG MANAGER TO MONITOR THE AWS EC2 REGION MONITORING THE AWS EC2 REGION...8 CONCLUSION...10

4 Table of Figures Figure 1.1: Providing the credentials during discovery of the AWS EC2 Cloud component...3 Figure 1.2: Managing the discovered AWS EC2 Cloud components...3 Figure 1.3: The list of unconfigured tests for AWS EC2 Cloud...4 Figure 1.4: Configuring the AWS - EC2 Region Status test...4 Figure 2.1: Managing an AWS EC2 Region...7 Figure 2.2: The list of unconfigured tests for AWS EC2 Region...7 Figure 2.3: Configuring the EC2 Region Status test...8

5 Configuring and Monitoring AWS EC2 Cloud Chapter 1 Configuring and Monitoring AWS EC2 Cloud This chapter describes the steps involved in administering and monitoring the Amazon EC2 Cloud. 1.1 Pre-Requisites for Monitoring the AWS EC2 Cloud There are certain pre-requisites that are to be satisfied while you start monitoring the AWS EC2 Cloud. These pre-requisites are discussed in detail in the forthcoming sections Configuring the eg agent with the required software The main pre-requisite for an eg agent to be able to monitor the AWS EC2 models is to make sure that the eg agent monitoring the AWS EC2 models supports JRE 1.6. By default, JRE 1.5 is bundled with the eg agent on Linux and Windows(64-bit) platforms. The AWS EC2 modelss are monitored in an agentless manner. Therefore, ensure that the remote agent supports JRE 1.6 by doing the following: Login to the agent host. Download JRE 1.6 for 64-bit hosts (if not already available on the host) from the java.sun.com web site. Then, copy the contents of the jre directory of JRE 1.6 (i.e., the <JAVA_HOME>\jre directory) to the jre directory of the eg agent (i.e., <EG_AGENT_INSTALL_DIR>\jre). Restart the eg agent Pricing details of the Amazon EC2 Instances The Amazon instances are classified into six families namely Standard, Micro, High-Memory, High-CPU, Cluster Compute, and Cluster GPU. Basically, configuring an instance within an Amazon EC2 Region and monitoring that instance is a paid service i.e., you pay charges for both configuring an instance in the Amazon EC2 cloud based on your requirement and collecting metrics from that particular instance. The payment varies according to the instance types and the Region in which the instance is deployed. 1

6 Configuring and Monitoring AWS EC2 Cloud For more detailed information regarding the Amazon EC2 purchasing options refer For more details regarding the pricing of the Amazon EC2 instances based on the Regions where they are deployed, refer Amazon Cloudwatch is a Paid service Amazon CloudWatch is a web service that enables you to monitor your Amazon EC2 instances, in real-time. Metrics such as CPU utilization, latency, and request counts are provided automatically for these AWS resources. You can also supply your own custom application and system metrics, such as memory usage, transaction volumes, or error rates, and Amazon CloudWatch will monitor these metrics too at a nominal charge. With Amazon CloudWatch, you can access up-to-the-minute statistics, view graphs, and set alarms for your metric data. Amazon CloudWatch functionality is accessible via API, command-line tools, the AWS SDK, and the AWS Management Console. Therefore, while configuring the tests for the AWS EC2 Component types, set the CLOUDWATCH ENABLED flag to true. By default, this flag is set to true Obtaining an Access key and Secret key To monitor an Amazon EC2 instance, the eg agent has to be configured with the access key of a user with a valid AWS account. To obtain the access key, follow the steps given below: Sign up for a new AWS account from the page. Provide the details of the user for whom you wish to create the AWS account. Based on the AWS EC2 Regions, you will be requested to choose the pricing for an instance to be deployed in the AWS EC2. Once the payment is made, the user will automatically be signed in to the AWS account. From the newly created AWS account, you can request for an access key. You will be provided with an access key and a corresponding secret key. While discovering an AWS EC2 Cloud component, provide the access key and secret key credentials that you have obtained in the corresponding text boxes. Once the AWS EC2 Cloud is discovered, the Regions that are available within the Cloud will be discovered automatically. 1.2 Administering the eg Manager to Monitor the AWS EC2 Cloud To achieve this, follow the steps given below: 1. Log into the eg administrative interface. 2. eg Enterprise automatically discovers the AWS EC2 Cloud component. If the AWS EC2 Cloud component is already discovered, use the Infrastructure -> Components - >Manage/Unmanage menu to manage it. Otherwise run discovery process as shown in Figure 1.1 from the menu sequence: Infrastructure ->Components -> Discover. Provide the credentials that you had obtained while creating the AWS account. To know more about the AWS account, refer to Section of this document. 2

7 Configuring and Monitoring AWS EC2 Cloud Figure 1.1: Providing the credentials during discovery of the AWS EC2 Cloud component 3. To manage the discovered components, go to the Infrastructure -> Components -> Manage/Unmanage page. The process of managing a component is clearly depicted by Figure 1.2 below. Figure 1.2: Managing the discovered AWS EC2 Cloud components For a more detailed procedure for managing components, refer to Configuring and Monitoring Web Servers document. 3

8 Configuring and Monitoring AWS EC2 Cloud 4. You can also manually add the AWS EC2 Cloud component using Infrastructure -> Components -> Add/Modify. Remember that components manually added are managed automatically. While manually adding the AWS EC2 Cloud component, make sure that you provide a valid name in the HOST text box instead of an IP address. In order to provide a valid name, ensure that the AllowQualifiedHostnames flag is set to Yes in the eg_services.ini file of the <EG_INSTALL_DIR>\manager\config directory. 5. Now, when you attempt to sign out of the eg administrative interface, Figure 1.3 appears, listing the tests that require manual configuration. Figure 1.3: The list of unconfigured tests for AWS EC2 Cloud 6. Click on the AWS EC2 Region Status test to configure it. This test reports the availability of the default Region and enables the administrators to figure out the time taken by the default Region to respond to responses. Upon clicking the test, Figure 1.4 appears. Figure 1.4: Configuring the AWS - EC2 Region Status test 7. In Figure 1.4, specify the following: TEST PERIOD How often this test needs to be executed HOST The host for which the test is to be configured AWS ACCESS KEY and CONFIRM PASSWORD As you provide these credentials during discovery of the AWS EC2 Cloud component, these fields will be auto-populated. For more details on these parameters refer Section AWS SECRET KEY and CONFIRM PASSWORD These credentials will also be autopopulated while discovery. For more details regarding these parameters refer to 4

9 Configuring and Monitoring AWS EC2 Cloud Section of this document. CLOUDWATCH ENABLED Amazon CloudWatch is a web service that enables you to monitor, manage, and publish various metrics, as well as configure alarm actions based on data from metrics. You can use Amazon CloudWatch to collect metrics about your Amazon Web Services (AWS) resources such as the performance of your Amazon EC2 instances i.e., VMs. To obtain the performance metrics of the AWS EC2 instances, set this flag to true. By default, this flag is set to true. For more details on the Amazon Cloudwatch, refer to Section of this document. EXCLUDE INSTANCE - Provide a comma-separated list of instance names or instance name patterns that you do not wish to monitor. By default, this parameter is set to none. REPORT INSTANCE REGION To monitor only the Regions that contain instances, set this flag to Yes. If this flag is set to No, the Regions will be monitored irrespective of whether the instances are present or not in each Region. By default, this flag is set to Yes. 8. Then, click the Update button in Figure Finally, sign out of the eg administrative interface. 1.3 Monitoring the AWS EC2 Cloud To monitor the AWS EC2 Cloud, do the following: 1. Login as a monitor / supermonitor user. 2. Click on the Components option in the menu bar, and select the Servers option from the Components menu. 3. In the COMPONENT LIST page, click on the AWS EC2 Cloud component for which you wish to view measurements. 5

10 Configuring and Monitoring AWS EC2 Region Chapter 2 Configuring and Monitoring AWS EC2 Region This chapter describes the steps involved in administering and monitoring the Amazon EC2 Region. 2.1 Administering the eg Manager to Monitor the AWS EC2 Region To achieve this, follow the steps given below: 1. Log into the eg administrative interface. 2. eg Enterprise automatically discovers the AWS EC2 Regions once you set the Discover AWS EC2 cloud regions parameter to Yes while discovering the AWS EC2 Cloud. If the AWS EC2 Region is already discovered, use the Infrastructure -> Components ->Manage/Unmanage menu to manage it. 3. To manage the discovered components, go to the Infrastructure -> Components -> Manage/Unmanage page. The process of managing a component is clearly depicted by Figure 2.1 below For a more detailed procedure for managing components, refer to Configuring and Monitoring Web Servers document. 6

11 Configuring and Monitoring AWS EC2 Region Figure 2.1: Managing an AWS EC2 Region 4. If you wish to manually add the Amazon EC2 Region component using the menu sequence: Infrastructure -> Components -> Add/Modify, ensure that you provide a valid name in the HOST text box instead of an IP address. In order to provide a valid name, ensure that the AllowQualifiedHostnames flag is set to yes in the eg_services.ini file of the <EG_INSTALL_DIR>\manager\config directory. Remember that components manually added are managed automatically Note: The HOST name must be provided in the following format: AWS EC2 Cloud/Region name. In this case, the HOST name must be given as awsec2cld/ap-southeast-1 5. Now, when you attempt to sign out of the eg administrative interface, Figure 2.2 appears, listing the tests requiring manual configuration. Figure 2.2: The list of unconfigured tests for AWS EC2 Region 6. Click on the EC2 Region Status test to configure it. This test reports the availability of the Region and enables the administrator to figure out the time taken by the Region to 7

12 Configuring and Monitoring AWS EC2 Region respond to responses. Upon clicking the test, Figure 2.3 appears. Figure 2.3: Configuring the EC2 Region Status test 7. In Figure 2.3, specify the following: TEST PERIOD How often this test needs to be executed HOST The host for which the test is to be configured AWS ACCESS KEY and CONFIRM PASSWORD As you provide these credentials during discovery of the AWS EC2 Region component, these fields will be auto-populated. For more details on these parameters refer to Section of this document. AWS SECRET KEY and CONFIRM PASSWORD These credentials will also be autopopulated while discovery. For more details regarding these parameters refer Section CLOUDWATCH ENABLED Amazon CloudWatch is a web service that enables you to monitor, manage, and publish various metrics, as well as configure alarm actions based on data from metrics. You can use Amazon CloudWatch to collect metrics about your Amazon Web Services (AWS) resources such as the performance of your Amazon EC2 instances i.e., VMs. To obtain the performance metrics of the AWS EC2 instances, set this flag to true. By default, this flag is set to true. For more details on the Amazon Cloudwatch, refer to Section of this document. EXCLUDE INSTANCE - Provide a comma-separated list of instance names or instance name patterns that you do not wish to monitor. By default, this parameter is set to none. 8. Then, click the Update button in Figure Finally, sign out of the eg administrative interface. 2.2 Monitoring the AWS EC2 Region To monitor the AWS EC2 Region, do the following: 8

13 Configuring and Monitoring AWS EC2 Region 1. Login as a monitor / supermonitor user. 2. Click on the Components option in the menu bar, and select the Servers option from the Components menu. 3. In the COMPONENT LIST page, click on the AWS EC2 Region component for which you wish to view measurements. 9

14 Conclusion Chapter 3 Conclusion This document has described in detail the steps for configuring and monitoring the Amazon EC2 component types. For details of how to administer and use the eg Enterprise suite of products, refer to the user manuals. We will be adding new measurement capabilities into the future versions of the eg Enterprise suite. If you can identify new capabilities that you would like us to incorporate in the eg Enterprise suite of products, please contact support@eginnovations.com. We look forward to your support and cooperation. Any feedback regarding this manual or any other aspects of the eg Enterprise suite can be forwarded to feedback@eginnovations.com. 10