Amazon CloudWatch
Learn how to connect Amazon CloudWatch to ZigiOps. Supported versions, IAM access keys, prerequisites, and connected system configuration.
What is Amazon CloudWatch integration in ZigiOps?
Amazon CloudWatch is a cloud-based monitoring and observability service that provides metrics, logs, and events for AWS resources and applications.
ZigiOps enables secure, agentless integration between Amazon CloudWatch and ITSM, DevOps, and enterprise systems. Using ZigiOps, CloudWatch metrics, alarms, and events can be forwarded to downstream systems where they can trigger incidents, tasks, or automated workflows.
With ZigiOps, Amazon CloudWatch can:
Send monitoring events and alerts to ITSM systems
Trigger incident and task creation in external platforms
Participate in end-to-end monitoring-to-resolution workflows
Operate without installing agents or custom scripts
Which Amazon CloudWatch versions are supported?
Using a supported version is mandatory.
Amazon CloudWatch
Cloud
All
Are there any environmental prerequisites for Amazon CloudWatch?
How do I generate an Amazon CloudWatch Access Key?
An AWS Access Key and Secret Key are required to authenticate Amazon CloudWatch with ZigiOps.
Steps:
Log in to your AWS account.
Navigate to Identity and Access Management (IAM).
Go to Users > Security Credentials.
Click Create Access Key to generate a new key.
Save the Access Key and Secret Key securely.
Make sure the IAM user has sufficient permissions to access the required CloudWatch resources.
How do I connect Amazon CloudWatch to ZigiOps?
Amazon CloudWatch - Connected System Configuration
Follow the steps below to add Amazon CloudWatch as a connected system in ZigiOps.
Log in to ZigiOps
Log in to your ZigiOps instance.
Open the Amazon CloudWatch connected system setup
Navigate to Connected Systems > Add New System > Amazon CloudWatch.
Configure the parameters
Configure the following parameters:
Access Key Enter the first part of your AWS access key.
Secret Key Enter the second part of your AWS access key.
AWS Region Enter the AWS region where your CloudWatch instance is located. The region can be identified from the AWS console or instance URL.
Proxy Settings (optional) Enable this option if a proxy server is required for outbound communication.
Review the configuration
Review the configuration.
Save the connected system
Click Save to store the connected system.
Once saved, Amazon CloudWatch becomes available for use in ZigiOps integration templates.
What are the most common Amazon CloudWatch integration use cases?
Use case 1: Sending CloudWatch alerts to ITSM systems
When Amazon CloudWatch detects threshold breaches or alarm conditions, ZigiOps can forward these events to ITSM platforms as incidents or tickets. Alert details, severity, timestamps, and metadata are mapped automatically, enabling faster incident response.
Use case 2: Monitoring-driven automation workflows
CloudWatch metrics and events can be used to trigger automated workflows across DevOps and operations systems. ZigiOps allows teams to react to infrastructure or application anomalies without manual intervention.
Use case 3: Centralized monitoring across enterprise tools
ZigiOps can act as a bridge between Amazon CloudWatch and multiple downstream systems, enabling organizations to consolidate monitoring data into a single operational workflow while maintaining traceability back to CloudWatch.
What integration templates are available for Amazon CloudWatch?
ZigiOps provides prebuilt integration templates for Amazon CloudWatch, depending on the target system and use case.
Related Templates
ZigiOps integration templates for Amazon CloudWatch are available depending on the paired system.
Each template includes:
Predefined entity mappings
Direction of synchronization
Entity-specific logic and filtering rules
For detailed information about available templates for Amazon CloudWatch integrations, please contact:
Email: support@zigiwave.com
Summary
The Amazon CloudWatch integration in ZigiOps provides:
Agentless, secure connectivity to AWS monitoring data
Support for all Amazon CloudWatch versions
IAM-based authentication using access keys
Flexible deployment with optional proxy support
Ready-to-use templates for monitoring-driven workflows
Last updated
Was this helpful?