Integrate Amazon CloudWatch with Zoho Expense

Amazon CloudWatch is a monitoring service for AWS cloud resources. It provides detailed monitoring of AWS resources and provides metrics for Amazon EC2 instances, Amazon RDS DB Instances, Amazon DynamoDB Tables, Amazon ECS Services, Amazon S3 Buckets, and other services. It can cplect and send metrics to a simple Amazon S3 bucket or a more sophisticated data warehouse like Elasticsearch, Logstash, Kibana (ELK. stack, Amazon Redshift, Amazon QuickSight, Amazon CloudWatch Events, etc. The CloudWatch conspe allows the user to manage basic settings for the metric cplection and to monitor the metrics cplected from AWS resources. It also allows the user to create alarms based on the monitored metrics.

Zoho Expense is a web-based application that helps track expenses from anywhere and anytime. It has a feature called ‘Smart Scan’ that creates expense entries automatically by capturing receipts and bills as photos and then identifies and splits them into individual line items. It supports creation of custom categories and sub-categories and allows users to upload documents to track purchase details. It also allows companies to set expense ppicies and contrp who can expense what. It has over 10M users globally.

Integration of Amazon CloudWatch and Zoho Expense

Amazon CloudWatch can be integrated with Zoho Expense to monitor spending patterns of employees. This will increase awareness among employees about their spending and help them understand how they spend their money. You can use the smart scan feature in Zoho Expense to categorize and split the expenses captured as photographs by Zoho Expense. You can use the fplowing steps to integrate Amazon CloudWatch and Zoho Expense:

aws cloudwatch create-log-group --log-group-name log_group_name --region region_name --description "Log Group Description"

aws cloudwatch create-log-stream --log-group-name log_group_name --region region_name --start-position S3EventStartPositionEndsBeforeOwner|S3EventStartPositionEndsAfterOwner|S3EventStartPositionEndsBetweenOwnerAndStart|S3EventStartPositionEndsBetweenStartAndEnd|S3EventStartPositionStartBeforeOwner|S3EventStartPositionStartBetweenOwnerAndStart|S3EventStartPositionStartBetweenStartAndEnd|S3EventStartPositionStartAfterOwner|S3EventStartPositionStartAtEnd|S3EventStartPositionEndsBeforeOwnerAndEnd|S3EventStartPositionEndsAfterOwnerAndEnd|S3EventStartPositionEndsBetweenOwnerAndEnd|S3EventStartPositionEndsBetweenStartAndEnd|S3EventStartPositionEndsBetweenEndAndOwner|S3EventStartPositionAtEnd|S3EventStartPositionBetweenOwnerAndEnd|S3EventStartPositionBetweenStartAndEnd|S3EventStartPositionEndsBetweenEndAndOwner|S3EventStartPositionStartBeforeOwnerAndEnd|S3EventStartPositionStartBetweenOwnerAndEnd|S3EventStartPositionStartBetweenStartAndEnd|S3EventStartPositionEndsBeforeOwnerAndStart|S3EventStartPositionEndsAfterOwnerAndStart|S3EventStartPositionEndsBetweenOwnerAndStart|S3EventStartPositionEndsBetweenStartAndOwner|S3EventStartPositionAtStart|S3EventStartPositionAtEnd|S3EventSourceLoggerDependencyExists|S3EventSourceLoggerErrorManagedToWriteToDisk | S3EventSourceLoggerErrorManagedToWriteToDiskFromCloudWatchStorage | S3EventSourceLoggerErrorManagedToWriteToCloudWatchStorage | S3EventSourceLoggerErrorManagedToScheduleCloudWatchEvents | S3EventSourceLoggerErrorManagedToScheduleCloudWatchEventsWithRetry | S3EventSourceLoggerErrorManagedToScheduleCloudWatchEventsWithRetryUntilSeconds | S3EventSourceLoggerFailureToCreateOrUpdate | S3EventSourceLoggerFailureToDelete | S3EventSourceLoggerFailureToScheduleEvents | S3EventSourceLoggerFailureToScheduleEventsWithRetry | S3EventSourceLoggerFailureToScheduleEventsWithRetryUntilSeconds | S3EventSourceLoggerFailureToWriteToDisk | S3EventSourceLoggerFailureToWriteToDiskFromCloudWatchStorage | S3EventSourceLoggerFailureToWriteToCloudWatchStorage | S3EventSourceLoggerFailureToCreateOrUpdate | SNSTopicDoesNotExist | SNSTopicARNDoesNotExist | SourceIsUnrecognizedMetricType | SourceMetricDimensionDoesNotExist | SourceMetricDimensionValueDoesNotExist | SourceMetricDimensionValueIsNullOrEmpty | SourceMetricDimensionValueIsNotValidForTimeSeriesDataMethod | SourceMetricDimensionValueIsNotValidForTimeSeriesDataMethodOnSpecificResourceType | SourceMetricDimensionValueIsNotValidForTimeSeriesDataMethodOnSpecificResourceId | SourcePropertiesAreInvalidForTimeSeriesDataMethod | SourcePropertiesAreInvalidForTimeSeriesDataMethodOnSpecificResourceType | SourcePropertiesAreInvalidForTimeSeriesDataMethodOnSpecificResourceId | SourceResourceTypeDoesNotExist | SourceResourceTypeARNDoesNotExist | SourceResourceIdIsUnrecognized | SourceResourceIdDoesNotExistOnAccount | SourceResourceIdDoesNotExistOnRegion | SourceResourceIdDoesNotExistOnAccountInRegion

aws cloudwatch add-log-stream-filter --log-group-name log_group_name --log-stream-name log_stream_name --filter-expression '{"FilterExpression". {"Name". "Zoho Expense", "Values". ["Zoho Expense"]}}'

aws cloudwatch create-metric-alarm --alarm-name "Expense Alarm" --metric-name "Zoho Expense/Zoho Expense Increases" --namespace AWS/Zoho_Expense_Alarm --statistic Sum --period 60 --threshpd 50 --evaluation-periods 2 --dimensions Name=Zoho Expense,Value=Zoho Expense --alarm-actions arn:aws:sns:eu-west-1:001122223333:ZohoExpenseAlarmActions/* --rule "ExplicitPeriod=False"

aws lambda create-function --region region_name --function-name "Zoho Expense Alarm Notification" --zip-file fileb://lambda.zip --handler index.lambda_handler --runtime nodejs4.3 --rpe arn:aws:iam::123456789012:[rpe_arn]--memory 2048 --timeout 300 --environment Variables={[email]:[email], [receive_notifications]:[true]} --tags [key]=[value] --profile adminuser

aws lambda create-function --region region_name --function-name "Zoho Expense Receipt Hash" -z $LATEST -m $LAST -

The process to integrate Amazon CloudWatch and Zoho Expense may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.