Azure Monitor Proof of Concept with 3rd Party Cloud Provider
This solution demonstrates how data and metrics collected from a third-party cloud provider can be delivered to a Log Analytics Workspace for analysis using Azure Monitor's HTTP Data Collector API.
What problem does this solve?
Organizations strive to achieve a single pane of glass for monitoring across cloud services. Many of times this data is spread across cloud services making it challenging for operations to monitor the environment. The Azure Monitor HTTP Data Collector API provides a mechanism to deliver data from 3rd party cloud services or on-premises services to an Azure Log Analytics Workspace. Rich visualizations can then be created using Azure Monitor Log Analytics to achieve a single pane of glass view of an enterprise's environment.
The solution uses an AWS Lambda to gather information about access key usage and delivers that data to a Log Analytics Workspace in an Azure subscription. The data can then be visualized using Azure Monitor's Log Analytics.
Python Runtime and Modules
AWS Permissions Requirement
- KMS:Decrypt and KMS:Encrypt for KMS key used to secure Lambda environment variables
The can be pushed using the provided CloudFormation template. The code must be placed into a ZIP file in an S3 bucket the user creating the CloudFormation stack has permissions to. The CloudFormation template requires the Workspace ID and Workspace Key from a Log Analytics Workspace in Azure.