aws (Amazon Web Services Monitoring) Release Notes

Amazon Web Service (AWS) provides a decentralized IT infrastructure to multiple organizations. You can create an account on the AWS cloud and can use its services according to your IT infrastructure requirements. The various capabilities of AWS include storage, web-scale computing, database access, and messaging.
The Amazon Web Services Monitoring (aws) probe remotely monitors the health and performance of available services over an AWS cloud. The probe allows you to monitor your AWS user account and retrieves all the service data from AWS CloudWatch. The probe generates Quality of Service (QoS) data and issues status alarms.
The probe from version 2.01 and later is configured only through the Admin Console GUI.
Amazon Web Service (AWS)
provides a decentralized IT infrastructure to multiple organizations. You can create an account on the AWS cloud and can use its services according to your IT infrastructure requirements. The various capabilities of AWS include storage, web-scale computing, database access, and messaging.
Amazon charges the AWS account which the probe uses to monitor the AWS services. Consider this fact while configuring the probe to monitor various AWS services.
Revision History
This section describes the history of the revisions for the aws probe.
Support case(s) may not be viewable to all customers.
What’s New:
  • Updated the Log4j library to 2.17.1 to remediate the vulnerabilities - CVE-2021-44228, CVE 2021-45046, and CVE-2021-45105.
January 2022
What's New:
  • The probe has been updated to address the common vulnerabilities and exposures by updating the jackson-databind libraries. For more information and CVE numbers, see Addressing Jackson Vulnerabilities.
Fixed Defects:
  • Fixed an issue where the Health Services Status data is not updated.
    Support Case 01253021
  • Fixed an issue where the custom metrics for the CWAgent cannot be viewed in the Admin Console.
    Support case 01207005
July 2019
What's New:
  • Added support for the probe to use IAM roles set on the EC2 instances, where the probe is deployed, to access AWS resources without using Access Key and Secret Key for authentication. For more information, see the
    Create a Profile
    section in aws AC Configuration.
September 2018
What's New:
  • New MCS template with:
    • Enhanced profiles that enable you to configure metrics, baselines, alarm thresholds, alarms - including Time Over Threshold alarms - and custom alarm and close alarm messages, all within a single MCS profile. For more information, see Configuring Alarm Thresholds in MCS.
June 2018
What’s New:
  • Added
    Region and Services List
    to exclude or include AWS regions and services from discovery and monitoring to only collect data from selected services and optimize API usage. For more information, see the
    Create a Profile
    section in aws AC Configuration.
  • AWS probe can be configured to fetch, parse and send parsed Cloudtrail logs to AXA Kafka. For more information , see the
    Create a Profile
    section in aws AC Configuration.
  • Added following 2 new metrics for monitoring performance of EC2 and RDS T2 instances:
    • CPUCreditUsage:
      Monitors percentage credit used
    • CPUCreditBalance:
      Monitors available credit balance
For more information, see aws Metrics.
These metrics are not applicable to other instance types.
  • Added metric,
    to monitor the status of a Relational Database Service DB instance. For more information, see aws Metrics.
The QoS data collection for AWS services is not dependent on the status of
check box under
Service Configurations
in AC GUI. The QoS data is collected based on the individual QoS selection for specific AWS services. The Active check box will be removed from the Admin Console’s
Service Configuration
section in the future release of the probe.
Fixed Defects:
  • The probe did not collect all custom metrics for Linux systems.
    Support case number 00776420
  • The probe generated QoS values as 0 instead of NULL for free available space when a value wasn't retrieved from AWS CloudWatch.
    Support case number 00802202
  • The probe did not collect data for AWS Route53 and Lambda even after enabling QoS metrics in the template.
    Support case number 00840045
  • The probe version 5.26 stopped displaying EC2 instances after some time post probe installation.
    Support case number 00841187
The probe version 5.26 reported NULL values for Auto Scaling Factory Template.
Support case number 00913242
February 2018
Fixed Defect:
  • The probe retrieved monitoring information of services of only one cluster when the AWS account has multiple clusters.
    Support case number 623074
May 2017
What's New:
  • Added support to monitor the performance and billing information of the AWS Lambda service.
  • Added a factory template to configure monitoring parameters for the AWS Lambda service.
  • Added support to monitor the following instance statistics:
    • Active EC2 Instances
    • EBS Instances
    • VPC Instances
    • RDS Instances
    • Auto Scale Instances
    • DynamoDB Instances
    • ECS Instances
    • Route53 Instances
    • ElastiCache Instances
    • SNS Instances
    • SQS Instances
    • ELB Instances
    • S3 Instances
  • Added support to create groups using the following AWS advanced filters in USM. For more information, see
    Create AWS Groups in USM
    in aws AC Configuration.
    • AWSUserName
      : filters using AWS accounts
    • AWSComputerNameInTags
      : filters using the name tag of the EC2 instance.
    • ComputerName:
      filters AWS instances using the instance ID.
  • Added support to identify instances with a combination of Instance ID and computer name when two or more instances have the same name in different regions.
  • Added support to display detailed information about VPCs in USM.
Fixed Defect:
  • The probe did not retrieve monitoring information for empty clusters outside the
    US West (Oregon)
April 2017
Fixed Defect:
  • Fixed an issue where the probe configuration GUI did not show the device inventory if MCS templates were enabled.
March 2017
What's new:
  • Added support to collect only enabled monitoring information for selected services.
    The probe always collects billing information for supported services.
  • Optimized the monitoring information collection interval for the following services:
    • Amazon Simple Storage Service (S3) - 24 hour intervals
    • AWS Billing and Cost Management - 8 hour intervals
  • Removed additional user credential requirements to collect billing information.
  • Added support for metric configuration through Monitoring Configuration Service (MCS).
January 2017
What's new:
  • Added help text in the
    Template Editor
Fixed Defect:
  • The probe did not store the monitoring information correctly when Amazon Web Services encountered any issue.
September 2016
What's New:
  • Added support in templates to filter the EC2 instances using AWS availability regions.
  • Added support to monitor the AWS services and geographical health in the
    ap-south-1: Asia Pacific (Mumbai)
  • Improved the monitoring performance for the following services:
    • Auto Scaling
    • Relational Database Service (RDS)
    • Simple Notification Service (SNS)
  • Enhanced the factory templates to include monitors for the Amazon Web Services (AWS) CABI dashboard.
  • Enhanced the Auto Scaling Factory Template with monitors for Auto Scaling groups.
August 2016
What's New:
  • Added support for unified dashboards for individual AWS services.
  • Added factory templates for each unified dashboard for individual AWS services.
  • Added support to monitor the following AWS services:
    • Amazon EC2 Container Service (ECS)
    • Amazon DynamoDB
    • Amazon Route 53
  • Added support to monitor the AWS Billing and Cost Management console for the following services:
    • DynamoDB
    • Elastic Compute Cloud (EC2)
    • ElastiCache
    • Relational Database Service (RDS)
    • Route 53
    • Simple Notification Service (SNS)
    • Simple Queue Service (SQS)
    • Simple Storage Service (S3)
  • Added support to monitor the power state of an EC2 instance.
  • Added support to monitor the size and number of objects in an S3 bucket.
  • Added support to monitor the following parameters in Elasticache:
    • Host
      • Network usage
      • Swap memory usage
    • Redis
      • Cache hits and misses
      • Number of evictions, hyperloglog based commands, new connection, key expirations, and current items
      • Replication size and lag
  • Enhanced the factory template.
  • Updated monitors in the probe with default threshold values.
Fixed Defects:
  • The probe displayed the Bin Log monitor for non-SQL Server RDS instances.
  • The probe generated QoS values as 0 instead of NULL when a value wasn't retrieved from AWS Cloudwatch.
June 2016
What's New:
  • Added the following functionalities in service health:
    • Monitor health of additional services
    • Generate QoS data for service health
    • Ignore alarms for deprecated services
    • Configure a timeframe and ignore the status of service earlier than that.
  • Added the following functionalities in EC2:
    • Monitor the EC2 instances that use only private IP addresses. For more information, see EC2 Private IP Configuration.
    • Display the public or private DNS name of the EC2 instance in USM instead of instance ID.
    • Filter the EC2 instances to monitor using templates by user specified AWS tags.
    • Monitor the EC2 instance status
  • Alarm messages have the following updates:
    • Enriched content in alarm messages
    • Complete service health name in alarm source
  • Removed alarm generation when service monitoring is initialized.
  • Enhanced the factory template.
March 2016
Fixed Defects:
  • The probe displayed a profile in Failure state despite of a successful credential verification.
    Salesforce cases 00169402, 70000878.
  • Updated the documentation to describe that Namespace and Dimension are required in the scripts to display the custom metrics on the probe GUI.
    Salesforce case 00167924
    For more information, see the
    Custom Metrics
    section in the aws AC GUI Reference
September 2015
  • Fixed an issue where NULL QoS value were generated for S3 service.
June 2015
What's New:
  • Added the ability to create monitoring configuration templates. The templates allow you to apply consistent monitoring configurations across multiple profiles using filters. The monitoring configurations apply across multiple instances of a service and multiple profiles of the aws probe.
    Template Editor is available from probe version 4.0 or later on UIM 8.3 and above. Health and Custom Metrics are not supported on Template Editor.
  • Factory templates for all monitors are available for Unified Dashboard.
    Factory Templates do not support Simple Storage Service (S3).
  • Added the ability to create AutoScale Groups on USM groups.
May 2015
  • Removed the ReplicaLag monitor for the RDS service from the GUI from version 3.51 onwards, for all databases except MySQL.
    When upgrading the probe from version 3.00 ~ 3.50 to version 3.51, you must delete the ReplicaLag key from the Raw Configure option to stop unwanted alarms for databases other than MySQL.
December 2014
  • Addition of ELB, SNS, SQS, and AutoScaling services.
December 2014
  • Changed default value of
    field from
    for EBS, RDS, ElastiCache services, and Custom Metrics monitoring.
September 2014
  • Addition of EBS, RDS, ElastiCache services, and Custom Metrics monitoring.
September 2014
  • First release of the probe for Admin Console GUI.
  • The probe is now available only through the web-based GUI and not through the Infrastructure Manager (IM) GUI.
  • Upgrade from previous versions to version 2.0x and later is not supported.
  • Removed the QOS_MACHINE_DEPLOYMENT_TIME metric.
  • The probe requires PPM probe version 2.34 for execution.
Probe is supported from CA UIM 7.6 and later only.
June 2014
  • Added Regional support for gathering metrics for QoS and Alarm.
  • Added configuration capabilities for Message Alarms for 7 Cloud watch Metrics.
  • Re-structuring of QoS Names.
  • Added option to configure the Log level.
  • Added the t1.micro instance option for Deployment sampler.
June 2013
  • First version of the Amazon AWS probe.
December 2009
Probe Specific Hardware Requirements
The aws probe is installed on systems with the following minimum resources:
  • Memory: 4 GB of RAM. The OOB configuration of the probe requires 256 MB of RAM.
  • CPU: 3-GHz dual-core processor; 32-bit or 64-bit
Probe Specific Software Requirements
The aws probe version 2.01 and later require the following software environment:
  • CA Unified Infrastructure Management 8.0 or later
    • (From aws version 5.00)
      CA UIM 8.4 SP1 or later for EC2 dynamic tags and USM groups
    • (From aws version 5.10)
      CA UIM 8.47 or later for Amazon Web Services (AWS) CABI dashboard
    Monitoring Configuration Service (MCS) requires CA Unified Infrastructure Management 8.51 or later.
  • Robot 7.62 or later (recommended)
  • Java JRE version 7 or later
  • Unified Dashboard 3.0.5 (for AWS 5.00 and later)
    For more information about upgrading Unified Dashboard, see Unified Dashboards.
(aws 4.10 and later) EC2 Private IP Configuration
The EC2 instances that use only private IPs require additional configuration to be monitored by the probe. The probe then publishes the private DNS name to USM.
Follow these steps:
  1. Open the
    Raw Configuration
    interface of the probe.
  2. Navigate to the
  3. Change the value of the
    key to
    Default: false
    EC2 instances can also use both public and private IPs. In such cases, the probe uses the private IP after you modify the key.
  4. Click
(aws 5.00 and later) Optimize Publishing for the Discovery Server Version
(CA UIM version 8.2 or later)
You can optimize the efficiency of the probe publishing process. Configure the probe to publish your QoS data to your specific version of Discovery Server.
Follow these steps:
  1. Verify your Discovery Server version. In the navigation tree for Admin Console, click on the machine that hosts Discovery Server. A table of probes appears where you can verify the version.
  2. Locate the machine that hosts the aws probe.
  3. Open Raw Configure for the probe.
  4. Select
  5. Select the key
    . It might be necessary to add this key if it does not exist.
  6. Enter the version for your Discovery Server as the key value.
    For example: 8.2
  7. Apply your changes.
  8. Restart the probe.
    Optimized publishing is enabled. The probe publishes only the delta values for the data it sends to the Discovery Server.
Installation Considerations
This section contains the installation prerequisites for the aws probe.
  • Ensure the following user access details:
    • An
      AWS user account
      with valid user-credentials, such as, Access Key and Secret Access Key.
    • The probe requires access to at least the following policies on AWS:
      • ReadOnlyAccess
      • AmazonS3ReadOnlyAccess
        The probe requires the
        policy to monitor
        S3 Write
    • The probe requires the following policies to monitor account billing details, in addition to
      access for
      • AWSAccountUsageReportAccess
      • AWSAccountActivityAccess
  • (aws 5.00 and later - Groups in USM)
    Follow these steps to use auto groups in USM:
    1. Deploy the CA UIM 8.4 SP2 package.
    2. Enable the trellis and das probes, if disabled.
  • (aws 5.00 and later)
    Add the following keys to the probe
    Raw Configuration
    interface >
    • thread_count
      : maximum number of threads that the probe can execute simultaneously. CA recommends you to use the maximum number as 50, but you can also increase this count if the probe is running on a system with high CPU memory.
    • max_api_requests
      : maximum number of API requests that the probe sends to the AWS CloudWatch in each second. Amazon supports a maximum of 400 requests in each second.
    Specify an integer value for both the keys.
  • (aws 5.40 and later)
    If you want to use IAM role-based authentication, then create a role and policies that provide required access to the AWS resources (ReadOnlyAccess and AmazonS3FullAccess) and assign that role to the EC2 instance. For more information about IAM role-based authentication, see
Upgrade Considerations
This section lists the upgrade considerations for the aws probe.
  • (aws 5.00 and later)
    Upgrade to Unified Dashboard version 3.05 to view the latest dashboards for the probe. The probe displays the earlier dashboard, however, CA recommends you to use the latest dashboards. For more information, see the
    View Probe Data
    section in aws AC Configuration.
  • On upgrade from 4.02 or earlier to a later version, the monitoring applied using the factory template is deactivated and all configuration is lost. The probe also does not upgrade custom templates to include new monitors. However, configuration using custom templates is retained.
  • When migrating to version 4.0 or later of the probe, you must manually clear the AutoScale alarms in USM. The new alarms generated by the probe are displayed in the created AutoScale group in USM.
  • For viewing the new metrics that are introduced in the aws probe version 3.0, on the USM portal, you can perform any one of the following actions:
    • Upgrade NMS 7.6 (or earlier) to CA UIM 8.0 and later.
    • Install the ci_defn_pack version 1.01 probe. You are required to restart the
      when you deploy the
      You can install the
      probe from
  • The aws probe version 2.0x and later is available through Admin Console GUI only and not through the Infrastructure Manager (IM) GUI. Upgrade from previous versions to version 2.0x and later is not supported.
  • QoS names of the following AWS metrics have changed in version 2.0x:
    Old QoS Name
    New QoS Name
  • Removed the QOS_MACHINE_DEPLOYMENT_TIME metric in version 2.0.
  • You must deploy Probe Provisioning Manager (PPM) probe version 2.34 or later for configuring the aws probe version 2.0x or later.
  • When you install the probe version 2.01 then manually move the existing configurations, in case you are using the probe of version earlier than version 2.01.
  • Delete all the versions of the probe that are earlier than version 2.01 as upgrade from a previous version to version 2.01 is not supported.
Alarm Threshold Requirements
The PPM probe maintains a table of subsystem IDs that are mapped to the probes. As of the current release, the subsystem IDs for this probe will default to 1.1.19. The aws probe supports the following types of alarms:
  • Dynamic Alarms Thresholds
  • Static Alarm Thresholds
  • Time Over Threshold
  • Time To Threshold
If you are using either dynamic or static alarm thresholds, you can change the default entry to the appropriate subsystem ID.
If you have upgraded NMS 7.6 to CA UIM 8.0 then you do not have to perform the following procedures.
Follow these steps:
  1. In the Admin Console, click the black arrow next to the probe, select
  2. Select the monitor that you want to modify from the available list.
  3. Change the Static and Dynamic
    Subsystem (override) fields
  4. Save your settings.
Update Subsystem ID
Alarms are classified by their subsystem ID, identifying which part of the system the alarm relates to. These subsystem IDs are kept in a table maintained by the NAS probe. If you are working with NMS 7.6 or earlier, you must add the following subsystem IDs manually using the NAS Raw Configuration menu. However, if you have upgraded to CA UIM 8.0 then you do not have to manually add the following subsystem IDs:
Key Name
Auto Scaling
Route 53
Follow these steps:
  1. Open the
    Raw Configuration
    interface of the
  2. Navigate to the
  3. Create a new key and specify values in the
    Key Name
  4. Repeat this process for all the required subsystem IDs for your probe.
  5. Click