Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell PowerProtect Cyber Recovery 19.13 AWS Deployment Guide

PDF

Installing the CloudWatch agent

To be able to monitor memory and disk use, first install the CloudWatch agent on your Cyber Recovery instance.

Prerequisites

Connectivity for the CloudWatch agent has been set up.

Steps

  1. Update IAM permissions:
    1. Log in to the AWS Management Console and then open the IAM console at https://console.aws.amazon.com/iam/.
    2. In the navigation pane, select Roles and then select <your prefix>_PPCRRole.
    3. Under the Permissions tab, select Attach policies.
    4. In the list of policies, select the check box next to CloudWatchAgentServerPolicy.
      If necessary, use the search box to find the policy.
    5. Click Attach policy.
  2. From a host that has access to the Internet, go to the Amazon Download and configure the CloudWatch agent using the command line web page at https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/download-cloudwatch-agent-commandline.html.
    1. Scroll to the table in the middle of the page.
    2. Download the latest CloudWatch agent for x86-64 for SUSE by using the first download link.
    The amazon-cloudwatch-agent.rpm agent package is downloaded.
  3. Log in to the Cyber Recovery jump host. Copy the amazon-cloudwatch-agent.rpm agent package onto the jump host.
    For information about enabling copy-paste functionality and copying files to the jump host, see the steps in Transferring files to the Cyber Recovery vault jump host.
  4. From the jump host, copy the amazon-cloudwatch-agent.rpm agent package to the \home\ec2-user\ directory on the Cyber Recovery host:
    scp -i <keypair> amazon-cloudwatch-agent.rpm  ec2-user@<cr_host_ip>:/home/ec2-user/
  5. Log in to the Cyber Recovery host and install the agent package:
    sudo rpm -U /home/ec2-user/amazon-cloudwatch-agent.rpm
  6. Configure the CloudWatch agent by running the following command on the Cyber Recovery host and responding to the queries with the recommended options as described in the following table:
    sudo /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-config-wizard
    Table 1. Recommended responses to the CloudWatch wizard queries
    Wizard query Value
    On which OS are planning to use the agent? 1. linux
    Are you using EC2 or On-Premises hosts? 1.EC2
    Which user are planning to run the agent? 1. root
    Do you want to turn on StartD daemon? 2. no
    Do you want to monitor metrics from CollectD? 2. no
    Do you want to monitor any host metrics? 1. yes
    Do you want to monitor any metrics per core? 2. no
    Do you want to add ec2 dimensions? 1. yes
    Would you like to collect your metrics at high resolution (sub-minute resolution)? 4. 60s
    Which default metrics config do you want? 2. Standard
    Are you satisfied with the above config? 1. yes
    Do you have an existing CloudWatch Log Agent configuration files to import for migration? 2. no
    Do you want to monitor any log files? 2. no
    Do you want to store the config in the SSM parameter store? 2. no
  7. Start the agent by running the following command:
     sudo /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a fetch-config -m ec2 -s -c file:/opt/aws/amazon-cloudwatch-agent/bin/config.json

    The agent uses the configuration file that the wizard created in the preceding step.

  8. Verify that the agent is running by using the following command:
    sudo service amazon-cloudwatch-agent status
  9. Wait several minutes for the CloudWatch Service to display the metrics.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\