AWS

Edit online

The AWS (Amazon Web Services) integration allows you to collect devices, metadata, and metrics from the AWS environment, without any additional modules. The integration uses AWS CloudWatch metric streams for time-series data and API calls for the metadata enrichment. The AWS integration allows you to monitor multiple AWS accounts and regions. It also allows you to collect AWS flow logs from the AWS environment. This is optional.

Important: NMS cluster must have a PAS appliance to host the AWS integration device.

For additional guidance, please refer to AWS Quick Start Guide.

Configuration

Edit online

From the left navigation bar, click Integrations. Under Filter, choose a datasource from the drop-down list. Select AWS under Public cloud.

awsIntegrationManager
Note: You will see a list of AWS integrations configured, count of All devices from integrations, AWS integration count, and the integration status. You may choose the chart to filter the data table by integration status; Succeeded, In progress, or Failed.

To manage existing AWS integrations, in the list of AWS integrations available, click 3dots icon next to the integration you want to manage. You can Edit or Delete the integration.

NOTE: Do not use SevOne NMS Device Manager to edit or delete AWS integrations. Using Device Manager for these actions can cause backend database inconsistencies.

To add a new integration, click Add new integration drop-down and select AWS option.

Execute the following steps.

  1. Setup AWS role - set up AWS role.
    • Select check box Infrastructure user setup.
    • Select check box Collector user setup.
    • Select check box Access key credentials.
    Note: You will see a list of supported devices types.

    Click Continue button to proceed to the next step.

  2. Infrastructure setup - set up AWS infrastructure.
    • Tab Terraform (recommended)
      • Select check box Infrastructure role setup.
      • Select check box Collector infrastructure.
    • Tab AWS management console
      • Select check box Create a metric stream.
      • Select check box Setup a S3 event notification.
      • Select check box Create a collector role.

    Click Continue button to proceed to the next step.

  3. AWS login - log in to AWS account using the AWS credentials to connect SevOne to AWS.

    integrationAWSLogin

    • Credentials
      • In the Account ID field, enter the ID of the AWS account you want to monitor and collect data from. The account ID must be a 12-digit number.
      • In the Access key ID field, enter the access key ID created for the collector user account. For additional details, please refer to https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html. The access key ID must be a 20-character string containing only uppercase letters (A-Z) and numbers (0-9).
      • In the Secret access key field, enter the secret access key created for the collector user account. For additional details, please refer to https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html. The secret acess key must be a 40-character string.
      • In the Collector Role ARN field, enter the ARN of the IAM role that the collector will assume. For additional details, please refer to section Required Infrastructure in AWS in AWS Quick Start Guide.
      • In the CloudWatch SQS Queue field, enter the SQS Queue name that the collector will listen to for metric stream events. For additional details, please refer to section Required Infrastructure in AWS in AWS Quick Start Guide. The CloudWatch SQS queue must have at least one character.
      • (optional) Enable Flow logs field. If enabled, enter the name of the SQS queue(s) in Flow logs SQS queue field that the collector will listen to for event notifications of VPC Flow logs.
      • From the Location drop-down list, select the AWS regions to monitor.
    • Polling Information
      • From Datasource drop-down list, select a configured connection that allows SevOne Data Insight to retrieve and visualize data from external systems.
      • From Polled by drop-down list, select which peer should poll this AWS integration. Devices will be added to the least loaded peer.

    Click Check Connection to check if the credentials and polling information have been configured correctly. If successful, you will get the message Connection successfully validated. Click Continue button to proceed to the next step.

  4. Basic information - enter the basic information.
    • Integration name - is an auto generated name based on the account ID's and integration type.
    • Alternative Name (optional) - enter the alternative name. This field is optional.
    • Description (optional) - enter the description. This field is optional.

Click Start integration to initiate the AWS integration.

To cancel the configuration, click the Cancel button.

To go to the previous step, click the Back button.

Important: Once the device is created, collection of AWS resources starts on SevOne NMS.

Manage AWS Integrations

Edit online
When you onboard an AWS integration, SevOne NMS automatically creates a corresponding entry in Device Manager. To manage AWS integrations, use Integration Manager in SevOne Data Insight.
  • To edit an AWS integration, click the overflow menu 3dots icon next to the integration and select Edit.
  • To delete an AWS integration, click the overflow menu 3dots icon next to the integration and select Delete.
Note:
  • Click the link in the Status column, for example, Succeeded to view the corresponding Device Notes.

    awsIntegrationManagerStatus

    awsIntegrationManagerDeviceNotes

AWS Services

Edit online
The AWS integration supports the following AWS services.
  • EBS Volumes
  • EC2 Instances
  • Direct Connects
  • NAT Gateways
  • Network Load Balancers
  • S3 Buckets
  • Site-to-Site VPN Connections
  • Transit Gateways
  • Lambda
  • Route 53 Health Checks
  • Route 53 Resolvers

The AWS integration uses:

  • Metric streams to stream basic metrics and S3 request metrics.
  • Kinesis Data Firehose to ingest the metric stream data into S3.
  • S3 Standard Storage to store the ingested data as objects.
  • SQS Standard Queues to send notification messages to SevOne NMS.

The AWS integration also calls CloudWatch and S3 APIs to fetch the object data from S3 and obtain certain metrics that are unavailable through metric stream.

For additional details on how to setup the resources, please refer to section Required Infrastructure in AWS in AWS Quick Start Guide.

AWS Device Groups

Edit online

Device groups are automatically created on SevOne NMS to group AWS devices by device description and metadata values. The AWS integration regularly applies the rules for these groups to ensure that devices are added to the appropriate groups.

Device Groups Hierarchy

Edit online
  1. All Device Groups - the default device group that contains all devices on SevOne NMS. This exists by default.
    1. AWS - device group that contains all automatically created AWS devices. A device is a member of this group if any of the rules below apply.
      1. Account - device group is the parent to other device groups for each AWS account that is being monitored. The child device groups will be named with the account ID of the corresponding account and contain only the AWS-related devices from that account. A device is a member if its AWS::Account ID metadata attribute matches the group name.

        Examples

        • 123456789012 - device group contains all devices with metadata AWS::Account ID::123456789012.
        • 234567890123 - device group contains all devices with metadata AWS::Account ID::234567890123.
        • 358567890246 - device group contains all devices with metadata AWS::Account ID::358567890246.
        • ...
        • ...
      2. Direct Connects - device group contains all AWS Direct Connects. A device is a member if it contains AWS Direct Connect in the device description.
      3. EBS Volumes: This device group contains all AWS EBS Volumes. A device is a member if it contains AWS EBS Volume in the device description.
      4. EC2 - device group contains all AWS EC2 instances. A device is a member if it contains AWS EC2 Instance in the device description.
      5. Elastic Load Balancers: This device group contains all AWS Elastic Load Balancers. A device is a member if it contains AWS Elastic Load Balancer in the device description.
        1. Network Load Balancers: This device group contains all AWS Network Load Balancers. A device is a member if it contains AWS Elastic Load Balancer, Network in the device description.
      6. NAT Gateways - device group contains all AWS NAT gateways. A device is a member if it contains AWS NAT Gateway in the device description.
      7. Region - device group is the parent to other device groups for each AWS region that is being collected. The child device groups will be named with the region code of the corresponding region and contain only the AWS-related devices from that region. A device is a member if its AWS::Region metadata attribute matches the group name.

        Examples

        • us-east-1 - device group contains all devices with metadata AWS::Region::us-east-1.
        • eu-west-1 - device group contains all devices with metadata AWS::Region::eu-west-1.
        • ap-north-1 - device group contains all devices with metadata AWS::Region::ap-north-1.
        • ...
        • ...
      8. S3 - device group contains all AWS S3 buckets. A device is a member if it contains AWS S3 Bucket in the device description.
      9. Site-to-Site VPN Connections: This device group contains all AWS Site-to-Site VPN connections. A device is a member if it contains AWS Site-to-Site VPN Connection in the device description.
      10. Transit Gateways - device group contains all AWS transit gateways. A device is a member if it contains AWS Transit Gateway in the device description.
      11. Lambda - device group contains all AWS lambda functions. A device is a member if it contains AWS Lambda in the device description.
      12. Route 53 - device group contains all AWS route 53 devices. A device is a member if it contains AWS Route 53 in the device description.
        • Health Checks - this device group contains all AWS route 53 health checks. A device is a member if it contains AWS Route 53 Health Check in the device description.
        • Resolvers - this device group contains all AWS route 53 resolvers. A device is a member if it contains AWS Route 53 Resolver in the device description.

AWS Flow Logs

Edit online
AWS integration supports the following AWS flow logs.
  • VPC Flow logs
  • TGW Flow logs

It uses S3 Standard Storage to store the flow logs and SQS Standard Queues to send notification messages to SevOne NMS. For additional details on how to setup the resources, please refer to section Required Infrastructure in AWS in AWS Quick Start Guide.

AWS Flow Log Format

Edit online

Currently, the collector supports flow logs from VPCs and Transit Gateways (TGWs), in their default and custom extended formats.

The following fields are supported for VPC Flow logs.

Table 1. Fileds supported by VPC Flow logs
Fields supported by VPC Flow logs
  • awsAccountId
  • awsAction
  • awsAvailabilityZoneID
  • awsDestinationAddress
  • awsInstanceId
  • awsInterfaceId
  • awsPacketDestinationAddress
  • awsPacketDestinationService
  • awsPacketSourceAddress
  • awsPacketSourceService
  • awsRegion
  • awsSourceAddress
  • awsSublocationId
  • awsSublocationType
  • awsSubnetId
  • awsTrafficType
  • awsTrafficPath
  • awsVPCId
  • awsAction
  • awsTrafficType
  • awsECSClusterARN
  • awsECSClusterName
  • awsECSContainerID
  • awsECSContainerID2
  • awsECSContainerInstanceARN
  • awsECSContainerInstanceId
  • awsECSServiceName
  • awsECSTaskARN
  • awsECSTaskDefininitionARN
  • awsECSTaskId

The following fields are supported for TGW Flow logs.

Table 2. Fields supported by TWG Flow Logs
Fields supported by TGW Flow logs
  • awsDestinationAddress
  • awsResourceType
  • awsSourceAddress
  • awsTGWId
  • awsTGWAttachmentId
  • awsTGWDestinationVPCId
  • awsTGWPairAttachmentId
  • awsTGWSourceVPCId
  • awsTGWDestinationAZ
  • awsTGWDestinationENI
  • awsTGWDestinationSubnetId
  • awsTGWDestinationVPCAccountId
  • awsTGWSourceAZ
  • awsTGWSourceENI
  • awsTGWSourceSubnetId
  • awsTGWSourceVPCAccountId
  • awsTrafficType
  • awsAccountId
  • awsRegion
  • awsPacketSourceService
  • awsPacketDestinationService
  • awsPacketsLostBlackHole
  • awsPacketsLostMTUExceeded
  • awsPacketsLostNoRoute
  • awsPacketsLostTTLExpired
Table 3. Fiields supported by TGW Flow logs
Fields supported by TGW Flow logs
  • awsDestinationAddress
  • awsResourceType
  • awsSourceAddress
  • awsTGWId
  • awsTGWAttachmentId
  • awsTGWDestinationVPCId
  • awsTGWPairAttachmentId
  • awsTGWSourceVPCId
  • awsTGWDestinationAZ
  • awsTGWDestinationENI
  • awsTGWDestinationSubnetId
  • awsTGWDestinationVPCAccountId
  • awsTGWSourceAZ
  • awsTGWSourceENI
  • awsTGWSourceSubnetId
  • awsTGWSourceVPCAccountId
  • awsTrafficType
  • awsAccountId
  • awsRegion
  • awsPacketSourceService
  • awsPacketDestinationService
  • awsPacketsLostBlackHole
  • awsPacketsLostMTUExceeded
  • awsPacketsLostNoRoute
  • awsPacketsLostTTLExpired
In addition to all aws Flow fields, some IPFIX fields are also supported and can be included in views for flow logs. The supported fields are,
  • Source Port
  • Destination Port
  • Protocol
  • Flow Direction
  • TCP Control Bits
  • Start Seconds
  • End Seconds
  • Bandwidth
  • Flows
  • Packets

For more information about the default and custom formats for flow records, please refer to VPC Flow records and TGW Flow records.

AWS Metadata

Edit online

New devices have metadata attributes added to them automatically in Device, Location, AWS, and AWS <service name> namespaces. For example, an EC2 instance will have metadata attributes populated in Device, Location, AWS, and AWS EC2 namespaces.

The tables below contain all AWS metadata namespaces and attributes in SevOne NMS.

Device

Edit online

Contains all attribute names and types that are created within the Device metadata namespace. All AWS devices will have these attributes populated.

Table 4. Attrubutes created within Device metadata
Attribute Name Attribute Type Description
Class Accepted Values The category or type of device.
Description Text The description of the device.
Function Text The primary role or operation performed by the device.
Identifier Text The unique identity of the device.
License Type Accepted Values The license type of the device.
Main Website URL The official website of the vendor that provides general information and documentation about the device.
Model Text The specific model, version, or configuration of the device.
Operational Status Accepted Values The current lifecycle or activity state of the device.
OS Family Text The operating system platform of the device.
OS Version Text The operating system version of the device.
Support Website URL The official website for technical support, troubleshooting, and updates for the device.
System Description Text The system description of the device.
Tenant Text The tenant of the device.
Vendor Text The organization that is associated with the device.
Wikipedia Entry URL A public Wikipedia URL that provides information about the device.

Location

Edit online

Contains all attribute names and types that are created within the Location metadata namespace. All AWS devices will have the following attributes populated.

Table 5. Attrubutes created within Locationmetadata
Attribute Name Attribute Type Description
Lat / Lon Latitude / Longitude The coordinates of the device.
Site Name Text The site of the device.
Site Type Accepted Values The type of the site.

AWS

Edit online

Contains all attribute names and types that are created within the AWS metadata namespace. All AWS devices will have these attributes populated.

Table 6. Attrubutes created within AWS metadata
Attribute Name Attribute Type Description
Account ID Text The 12-digit account number of the account that the device is within.
Region Text The AWS region code that the corresponding AWS device is within.
Coordinates Latitude / Longitude The coordinates of the device.

AWS Tags

Edit online

Contains all attribute names and types that are created within the AWS Tags metadata namespace. All AWS devices will have the attributes in the metadata for all the configured tag attributes in /config/aws/config.yaml.

AWS Direct Connect

Edit online

Contains all attribute names and types that are created within the AWS Direct Connect metadata namespace. Only Direct Connect devices will have these attributes populated.

Table 7. Attrubutes created within AWS Device Connect metadata
Attribute Name Attribute Type Description
Account ID Text The 12-digit account number of the account that the connection is within.
Bandwidth Text The bandwidth of the connection.
Connection Name Text The name of the connection.
Connection State Text

The state of the connection.

Please refer to https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/directconnect%40v1.18.10/types#ConnectionState for additional details.
Location Text The name of the location where the direct connect is located.
Region Text The code of the AWS region that the connection is within.

AWS EC2

Edit online

Contains all attribute names and types that are created within the AWS EC2 metadata namespace. Only EC2 instance devices will have these attributes populated.

Table 8. Attrubutes created within AWS EC2 metadata
Attribute Name Attribute Type Description
Account ID Text The 12-digit account number of the account that the instance is within.
Availability Zone Text The code of the AWS availability zone that the instance is within.
Instance State Text

The current state of the instance.

Please refer to https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/ec2%40v1.93.2/types#InstanceState for additional details.
Instance Type Text

The type of the instance.

Please refer to https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/ec2%40v1.93.2/types#InstanceType for additional details.
Launch Time Date/Time The time the instance was launched.
Public IPv4 Address IP Address

The public IPv4 or the Carrier IP address assigned to the instance.

Please refer to https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/ec2%40v1.93.2/types#Instance under PublicIPAddress for additional details.
Region Text The code of the AWS region that the instance is within.
VPC ID Text The ID of the VPC in which the instance is running.
Platform Text The operating system details of the instance.
IPv6 Address IP The IPv6 address assigned to the instance.

AWS Elastic Block Store

Edit online

The following table contains all of the attribute names and types that are created within the AWS Elastic Block Store metadata namespace. Only EBS Volume devices will have these attributes populated.

Table 9. Attrubutes created within AWS Elastic Block Store metadata
Attribute Name Attribute Type Description
Attached Instance Text The ID of the EC2 instance attached to the volume.
Created Date/Time The time stamp when volume creation was initiated.
Encryption Text Indicates whether the volume is encrypted.
IOPS Integer The number of I/O operations per second (IOPS).
Size Integer The size of the volume, in GiBs.
Type Text The volume type.
Volume State Text The volume state. For additional details, please refer to sectionReferences forAWS Type > VolumeState.
Volume Status Text The status of the volume. For additional details, please refer to sectionReferences forAWS Type > VolumeStatusInfoStatus.

AWS Elastic Load Balancer

Edit online

The following table contains all of the attribute names and types that are created within the AWS Elastic Load Balancer metadata namespace. Only Elastic Load Balancer devices will have these attributes populated.

Table 10. Attrubutes created within AWS Elastic Load Balance metadata
Attribute Name Attribute Type Description
Availability Zones Text The subnets for the load balancer.
Creation Time Date/Time The date and time the load balancer was created.
Load Balancer Type Text The type of load balancer. For additional details, please refer to sectionReferences forAWS Type > LoadBalancerTypeEnum.
State Text The state of the load balancer. For additional details, please refer to sectionReferences forAWS Type > LoadBalancerStateEnum.
VPC ID Text The ID of the VPC for the load balancer.

AWS NAT Gateway

Edit online

Contains all attribute names and types that are created within the AWS NAT Gateway metadata namespace. Only NAT gateway devices will have these attributes populated.

Table 11. Attrubutes created within AWS NAT Gateway metadata
Attribute Name Attribute Type Description
Connectivity Type Text

The type of the NAT gateway, either public or private.

Please refer to https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/ec2%40v1.93.2/types#ConnectivityType for additional details.
Creation Date Date/Time The time that the NAT gateway was created.
NAT Gateway State Text

The state of the NAT gateway.

Please refer to https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/ec2%40v1.93.2/types#NatGatewayState for additional details.
Primary Elastic IP Address IP Address The primary elastic IP address associated with the NAT gateway.
Primary Private IP Address IP Address The primary private IP address associated with the NAT gateway.
Subnet ID Text The ID of the subnet in which the NAT gateway is located.
VPC ID Text The ID of the VPC in which the NAT gateway is located.

AWS S3

Edit online

Contains all attribute names and types that are created within the AWS S3 metadata namespace. Only S3 bucket devices will have these attributes populated.

Table 12. Attrubutes created within AWS S3 metadata
Attribute Name Attribute Type Description
Creation Date Text

The time that the S3 bucket was created.

Please refer to https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/s3%40v1.31.3/types#Bucket for additional details.
Region Text The code of the AWS region that the bucket is within.

AWS Site-to-Site VPN

Edit online

The following table contains all of the attribute names and types that are created within the AWS Site-to-Site VPN metadata namespace. Only Site-to-Site VPN Connection devices will have these attributes populated.

Table 13. Attrubutes created within AWS Site-to-Site VPN metadata
Attribute Name Attribute Type Description
Customer Gateway Text The ID of the customer gateway at your end of the VPN connection.
Customer Gateway Address Text The IP address of the customer gateway at your end of the VPN connection.
Transit Gateway Text The ID of the transit gateway associated with the VPN connection.
Virtual Private Gateway Text The ID of the virtual private gateway at the Amazon Web Services side of the VPN connection.
VPN Connection State Text The current state of the VPN connection. For additional details, please refer to sectionReferences forAWS Type > VpnState.
VPN Connection Type Text The type of VPN connection. For additional details, please refer to sectionReferences forAWS Type > GatewayType.

AWS Transit Gateway

Edit online

The following table contains all of the attribute names and types that are created within the AWS Transit Gateway metadata namespace. Only transit gateway devices will have these attributes populated.

Table 14. Attrubutes created within AWS Transit Gateway metadata
Attribute Name Attribute Type Description
Account ID Text The 12-digit account number of the account that the transit gateway was collected from.
Amazon ASN Integer

A private Autonomous System Number (ASN) for the Amazon side of a BGP session.

Please refer to https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/ec2%40v1.93.2/types#TransitGatewayOptions under AmazonSideAsn for additional details.
Description Text The description of the transit gateway.
DNS Support Text

Indicates whether DNS support is enabled.

Please refer to https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/ec2%40v1.93.2/types#DnsSupportValue for additional details.
Region Text The code of the AWS region that the transit gateway is within.
State Text

The state of the transit gateway.

Please refer to https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/ec2%40v1.93.2/types#TransitGatewayState for additional details.

AWS Lambda Functions

Edit online
The following table contains all of the attribute names and types that are created within the AWS Lambda functions metadata namespace. Only lambda function devices will have these attributes populated.
Table 15. Attrubutes created within AWS Lambda Functions metadata
Attribute Name Attribute Type Description
Architecture Text The type of processor lambda uses to run function.
Handler Text The method of the function code that processes events.
Memory (MB) Integer The memory allocated to the function in megabytes.
Package Type Text The type of package for the function.
Runtime Text The program that runs function’s handler method.

AWS Route 53 Health Check

Edit online
The following table contains all of the attribute names and types that are created within the AWS Route 53 Health Check metadata namespace. Only Route 53 health check devices will have these attributes populated.
Table 16. Attrubutes created within AWS Route 53 Health Check metadata
Attribute Name Attribute Type Description
IP Address IP Address The IP Address of the health check device.
Port Integer The port number associated with the device.
Protocol Text The protocol of the health check device.
URL URL The URL associated with the health check device.

AWS Route 53 Resolver

Edit online
The following table contains all of the attribute names and types that are created within the AWS Route 53 Resolver metadata namespace. Only Route 53 resolver devices will have these attributes populated.
Table 17. Attrubutes created within AWS Route 53 Resolver metadata
Attribute Name Attribute Type Description
Creation Date Date/Time The creation date of AWS Route 53 Resolver endpoint.
Endpoint Type Integer The type of the endpoint of AWS Route 53 Resolver.
Service Name Text The service that provides DNS resolution for resources in VPC to reach resources on network.
Status Text The status of AWS Route 53 Resolver endpoint.
VPC ID Text The ID of the VPC associated with AWS Route 53 Resolver endpoint.

AWS Metrics

Edit online

After a device is configured to monitor an AWS account, object and indicator types are created on the configured SevOne NMS. When metric data is obtained from S3, objects and indicators of the appropriate types are added to the corresponding SevOne NMS device.

The tables below contain all metrics collected by SevOne NMS and the associated object and indicator types created on SevOne NMS.

Direct Connect

Edit online

This section explains the object types and indicator types that are created for AWS Direct Connects.

Object Types

Edit online

Under All Object Types object type, the AWS integration creates an object type, AWS Direct Connect. Within AWS Direct Connect, the following object types are created.

  • AWS DX Physical Operations
  • AWS DX Virtual Operations

Indicator Types

Edit online

The following table contains all the indicator types for Direct Connects, their parent object type, and which unit is used on the NMS. For additional details, please refer to https://docs.aws.amazon.com/directconnect/latest/UserGuide/monitoring-cloudwatch.html.

Table 18. Indicator types for Direct Connects, their parent object type, and which unit is used on the NMS
Parent Object Type Name Description Unit
AWS DX Physical Operations ConnectionBpsEgress Connection Bps Egress Number
ConnectionBpsIngress Connection Bps Ingress Number
ConnectionEncryptionState Connection Encryption State Number
ConnectionErrorCount Connection Error Count Number
ConnectionLightLevelRx Connection Light Level Rx (dBm) Number
ConnectionLightLevelTx Connection Light Level Tx (dBm) Number
ConnectionPpsEgress Connection Pps Egress Number
ConnectionPpsIngress Connection Pps Ingress Number
ConnectionState Connection State Number
AWS DX Virtual Operations VirtualInterfaceBpsEgress Virtual Interface Bps Egress Number
VirtualInterfaceBpsIngress Virtual Interface Bps Ingress Number
VirtualInterfacePpsEgress Virtual Interface Pps Egress Number
VirtualInterfacePpsIngress Virtual Interface Pps Ingress Number

EBS Volume

Edit online

This section explains the object types and indicator types that are created for AWS EBS volumes.

Object Types

Edit online

Beneath the All Object Types object type, the AWS integration creates an object type, AWS EBS Volume. Within AWS EBS Volume, the following object types are created:

  • AWS EBS Volume Operations

Indicator Types

Edit online

The following table contains all the indicator types for EBS volumes, their parent object type, and which unit is used on the NMS. For additional details, please refer to https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using_cloudwatch_ebs.html.

Table 19. Indicator types for EBS volumes, their parent object type, and which unit is used on the NMS
Parent Object Type Name Description Unit
AWS EBS Volume Operations BurstBalance Burst Balance Percent
VolumeConsumedReadWriteOps Volume Consumed Read Write Ops Number
VolumeIdleTime Volume Idle Time Seconds
VolumeQueueLength Volume Queue Length Number
VolumeReadBytes Volume Read Bytes Bytes
VolumeReadOps Volume Read Ops Number
VolumeThroughputPercentage Volume Throughput Percentage Percent
VolumeTotalReadTime Volume Total Read Time Seconds
VolumeTotalWriteTime Volume Total Write Time Seconds
VolumeWriteBytes Volume Write Bytes Bytes
VolumeWriteOps Volume Write Ops Number

EC2

Edit online

This section explains the object types and indicator types that are created for AWS EC2 instances.

Object Types

Edit online

Under All Object Types object type, the AWS integration creates an object type, AWS EC2. Within AWS EC2, the following object types are created.

  • AWS EC2 Instance
  • AWS EC2 Instance CPU
  • AWS EC2 Instance CPU Credit
  • AWS EC2 Instance Disk
  • AWS EC2 Instance Network

Indicator Types

Edit online

The following table contains all indicator types for EC2 instances, their parent object type, and the unit used on SevOne NMS. For additional details, please refer to https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/viewing_metrics_with_cloudwatch.html.

Table 20. Indicator types for EC2 instances, their parent object type, and the unit used on SevOne NMS
Parent Object Type Name Description Unit
AWS EC2 Instance StatusCheckFailed Status Check Failed Number
StatusCheckFailed_Instance Instance Status Check Failed Number
StatusCheckFailed_System System Status Check Failed Number
AWS EC2 Instance CPU CPUUtilization CPU Utilization Percent
AWS EC2 Instance CPU Credit CPUCreditBalance CPU Credit Balance Minutes
CPUCreditUsage CPU Credit Usage Minutes
AWS EC2 Instance Disk DiskReadBytes DiskReadBytes Bytes
DiskReadOps DiskReadOps Number
DiskWriteBytes DiskWriteBytes Bytes
DiskWriteOps DiskWriteOps Number
AWS EC2 Instance Network NetworkIn Network In Bytes
NetworkOut Network Out Bytes

NAT Gateway

Edit online

This section explains the object types and indicator types that are created for AWS NAT gateways.

Object Types

Edit online

Under All Object Types object type, the AWS integration creates an object type, AWS NAT Gateway. Within AWS NAT Gateway, the following object type is created.

  • AWS NAT Gateway Operations

Indicator Types

Edit online

The following table contains all the indicator types for NAT gateways, their parent object type, and the unit used on SevOne NMS. For additional details, please refer to https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway-cloudwatch.html.

Table 21. Indicator types for NAT gateways, their parent object type, and the unit used on SevOne NMS
Parent Object Type Name Description Unit
AWS NAT Gateway Operations ActiveConnectionCount Active Connection Count Number
BytesInFromDestination Bytes In From Destination Bytes
BytesInFromSource Bytes In From Source Bytes
BytesOutToDestination Bytes Out To Destination Bytes
BytesOutToSource Bytes Out To Source Bytes
ConnectionAttemptCount Connection Attempt Count Number
ConnectionEstablishedCount Connection Established Count Number
ErrorPortAllocation Error Port Allocation Number
IdleTimeoutCount Idle Timeout Count Number
PacketsDropCount Packets Drop Count Number
PacketsInFromDestination Packets In From Destination Number
PacketsInFromSource Packets In From Source Number
PacketsOutToDestination Packets Out To Destination Number
PacketsOutToSource Packets Out To Source Number

Network Load Balancer

Edit online

This section explains the object types and indicator types that are created for AWS Network Load Balancers.

Object Types

Edit online

Beneath the All Object Types object type, the AWS integration creates an object type, AWS Network Load Balancer. Within AWS Network Load Balancer, the following object types are created:

  • AWS NLB Operations
  • AWS NLB Operations TCP
  • AWS NLB Operations TLS
  • AWS NLB Operations UDP
  • AWS NLB TCP Resets
  • AWS NLB TLS Negotiation Errors
  • AWS NLB Target Group Stats

Indicator Types

Edit online

The following table contains all the indicator types for network load balancers, their parent object type, and which unit is used on the NMS. For additional details, please refer to https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-cloudwatch-metrics.html.

Table 22. Indicator types for network load balancers, their parent object type, and which unit is used on the NMS
Parent Object Type Name Description Unit
AWS NLB Operations ActiveFlowCount Active Flow Count Number
ConsumedLCUs Consumed LCUs Number
NewFlowCount New Flow Count Number
PeakPacketsPerSecond Peak Packets per Second Number
PortAllocationErrorCount Port Allocation Error Count Number
ProcessedBytes Processed Bytes Bytes
ProcessedPackets Processed Packets Number
AWS NLB Operations TCP ActiveFlowCount_TCP Active Flow Count TCP Number
ConsumedLCUs_TCP Consumed LCUs TCP Number
NewFlowCount_TCP New Flow Count TCP Number
ProcessedBytes_TCP Processed Bytes TCP Bytes
AWS NLB Operations TLS ActiveFlowCount_TLS Active Flow Count TLS Number
ConsumedLCUs_TLS Consumed LCUs TLS Number
NewFlowCount_TLS New Flow Count TLS Number
ProcessedBytes_TLS Processed Bytes TLS Bytes
AWS NLB Operations UDP ActiveFlowCount_UDP Active Flow Count UDP Number
ConsumedLCUs_UDP Consumed LCUs UDP Number
NewFlowCount_UDP New Flow Count UDP Number
ProcessedBytes_UDP Processed Bytes UDP Bytes
AWS NLB TCP Resets TCP_Client_Reset_Count TCP Client Reset Count Number
TCP_ELB_Reset_Count TCP ELB Reset Count Number
TCP_Target_Reset_Count TCP Target Reset Count Number
AWS NLB TLS Negotiation Errors ClientTLSNegotiationErrorCount Client TLS Negotiation Error Count Number
TargetTLSNegotiationErrorCount Target TLS Negotiation Error Count Number
AWS NLB Target Group Stats HealthyHostCount Healthy Host Count Number
UnHealthyHostCount UnHealthy Host Count Number

S3

Edit online

This section explains the object types and indicator types that are created for AWS S3 buckets.

Object Types

Edit online

Under All Object Types object type, the AWS integration creates an object type, AWS S3. Within AWS S3, the following object types are created.

  • AWS S3 Bucket Statistics
  • AWS S3 Request Statistics

Indicator Types

Edit online

The following table contains all the indicator types for S3 buckets, their parent object type, and the unit used on SevOne NMS. For additional details please refer to https://docs.aws.amazon.com/AmazonS3/latest/userguide/metrics-dimensions.html.

Table 23. Indicator types for S3 buckets, their parent object type, and the unit used on SevOne NMS
Parent Object Type Name Description Unit
AWS S3 Bucket Statistics BucketSizeBytes Bucket Size Bytes Bytes
NumberOfObjects Number Of Objects Number
AWS S3 Request Statistics 4xxErrors 4xx Errors Number
5xxErrors 5xx Errors Number
AllRequests All Requests Number
BytesDownloaded Bytes Downloaded Bytes
BytesUploaded Bytes Uploaded Bytes
FirstByteLatency First Byte Latency Milliseconds
GetRequests Get Requests Number
PostRequests Post Requests Number
PutRequests Put Requests Number
TotalRequestLatency Total Request Latency Milliseconds

Site-to-Site VPN Connection

Edit online

This section explains the object types and indicator types that are created for AWS Site-to-Site VPN Connections.

Object Types

Edit online

Beneath the All Object Types object type, the AWS integration creates an object type, AWS Site-to-Site VPN Connection. Within AWS Site-to-Site VPN Connection, the following object types are created:

  • AWS VPN Operations

Indicator Types

Edit online

The following table contains all the indicator types for Site-to-Site VPN connections, their parent object type, and which unit is used on the NMS. For additional details please refer to https://docs.aws.amazon.com/vpn/latest/s2svpn/monitoring-cloudwatch-vpn.html.

Table 24. Indicator types for Site-to-Site VPN connections, their parent object type, and which unit is used on the NMS
Parent Object Type Name Description Unit
AWS VPN Operations TunnelDataIn Tunnel Data In Bytes
TunnelDataOut Tunnel Data Out Bytes
TunnelState Tunnel State Number

Transit Gateway

Edit online

This section explains the object types and indicator types that are created for AWS transit gateways.

Object Types

Edit online

Under All Object Types object type, the AWS integration creates an object type, AWS Transit Gateway. Within AWS Transit Gateway, the following object type is created.

  • AWS Transit Gateway Operations

Indicator Types

Edit online

The following table contains all the indicator types for transit gateways, their parent object type, and the unit used on SevOne NMS. For additional details please refer to https://docs.aws.amazon.com/vpc/latest/tgw/transit-gateway-cloudwatch-metrics.html.

Table 25. Indicator types for transit gateways, their parent object type, and the unit used on SevOne NMS
Parent Object Type Name Description Unit
AWS Transit Gateway Operations BytesDropCountBlackhole Bytes Drop Count Blackhole Bytes
BytesDropCountNoRoute Bytes Drop Count No Route Bytes
BytesIn Bytes In Bytes
BytesOut Bytes Out Bytes
PacketDropCountBlackhole Packet Drop Count Blackhole Number
PacketDropCountNoRoute Packet Drop Count No Route Number
PacketsIn Packets In Number
PacketsOut Packets Out Number

Lambda Function

Edit online

This section explains the object types and indicator types that are created for AWS lambda functions.

Object Types

Edit online

Under All Object Types object type, the AWS integration creates an object type, AWS Lambda Functions. Within AWS Lambda Functions, the following object type is created.

  • AWS Lambda Invocations
  • AWS Lambda Performance
  • AWS Lambda Concurrency
  • AWS Lambda Asynchronous Invocation

Indicator Types

Edit online

The following table contains all the indicator types for lambda functions, their parent object type, and the unit used on SevOne NMS. For additional details please refer to https://docs.aws.amazon.com/lambda/latest/dg/monitoring-metrics.html.

Table 26. Indicator types for lambda functions, their parent object type, and the unit used on SevOne NMS
Parent Object Type Name Description Unit
AWS Lambda Invocation Invocations Invocations Number
Errors Errors Number
DeadLetterErrors Dead Letter Errors Number
DestinationDeliveryFailures Destination Delivery Failures Number
Throttles Throttles Number
OversizedRecordCount Oversized Record Count Number
ProvisionedConcurrencyInvocations Provisioned Concurrency Invocations Number
ProvisionedConcurrencySpilloverInvocations Provisioned Concurrency Spillover Invocations Number
RecursiveInvocationsDropped Recursive Invocations Dropped Number
AWS Lambda Performance Duration Duration Milliseconds
PostRuntimeExtensionsDuration PostRuntime Extensions Duration Milliseconds
IteratorAge Iterator Age Milliseconds
OffsetLag Ofset Lag Milliseconds
AWS Lambda Concurrency ConcurrentExecutions Concurrent Executions Number
ProvisionedConcurrentExecutions Provisioned Concurrent Executions Number
UnreservedConcurrentExecutions Unreserved Concurrent Executions Number
ClaimedAccountConcurrency Claimed Account Concurrency Number
AWS Lambda Asynchronous Invocation AsyncEventsReceived Async Events Received Number
AsyncEventAge Async Event Age Milliseconds
AsyncEventsDropped Async Events Dropped Number

Route 53

Edit online

This section explains the object types and indicator types that are created for AWS Route 53.

Object Types

Edit online

Under All Object Types object type, the AWS integration creates an object type, AWS Route 53. Within AWS Route 53, the following object type is created.

  • AWS Route 53 Health Check
  • AWS Route 53 Resolver

Indicator Types

Edit online

The following table contains all the indicator types for Route 53, their parent object type, and the unit used on SevOne NMS. For additional details please refer to https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/monitoring-cloudwatch.html and https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/monitoring-resolver-with-cloudwatch.html

Table 27. Indicator types for Route 53, their parent object type, and the unit used on SevOne NMS
Parent Object Type Name Description Unit
AWS Route 53 Health Check ChildHealthCheckHealthyCount Child Health Check Healthy Count Number
ConnectionTime Connection Time Milliseconds
HealthCheckPercentageHealthy Health Check Percentage Healthy Percent
HealthCheckStatus Health Check Status Number
SSLHandshakeTime SSL Handshake Time Milliseconds
TimeToFirstByte Time To First Byte Number
AWS Route 53 Resolver EndpointHealthyENICount Endpoint Healthy ENI Count Number
EndpointUnhealthyENICount Endpoint Unhealthy ENI Count Number
InboundQueryVolume Inbound Query Volume Number
OutboundQueryVolume Outbound Query Volume Number
OutboundQueryAggregateVolume Outbound Query Aggregate Volume Number

References

Edit online
Table 28. AWS Types and URLs
AWS Type URL
GatewayType https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/ec2%40v1.93.2/types#GatewayType
LoadBalancerStateEnum https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/elasticloadbalancingv2%40v1.19.13/types#LoadBalancerStateEnum
LoadBalancerTypeEnum https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/elasticloadbalancingv2%40v1.19.13/types#LoadBalancerTypeEnum
VolumeState https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/ec2%40v1.93.2/types#VolumeState
VolumeStatusInfoStatus https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/ec2%40v1.93.2/types#VolumeStatusInfoStatus
VPCFlowLogs https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html
VPCTransitGatewayFlowLogs https://docs.aws.amazon.com/vpc/latest/tgw/tgw-flow-logs.html
VpnState https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/ec2%40v1.93.2/types#VpnState