amazon-cloudwatch

On my project there is REST API which implemented on AWS API Gateway and AWS Lambda. As AWS Lambda functions are serverless and stateless while we make a call to it, AWS starts a container with code of the Lambda function which process our call. According AWS documentation after finishing of lambda function execution AWS don't stop the container and we are able to process next call in that container. Such approach improves performance of the service - only in time of first call AWS spend time to start container (cold start of Lambda function) and all next calls are executed faster because

I can view the log using the following command. aws logs get-log-events --log-group-name groupName --log-stream-name streamName --limit 100 what is the command to get feature like tail -f so that i can see the log real time Have a look at awslogs . If you happen to be working with Lambda/API Gateway specifically, have a look at apilogs . I was really disappointed with awslogs and cwtail so I made my own tool called Saw that efficiently streams CloudWatch logs to the console (and colorizes the JSON output): You can install it on MacOS with: brew tap TylerBrock/saw brew install saw It has a

I'm trying to set up a Lambda function that will process a file when it's uploaded to an S3 bucket. I need a way to see the output of console.log when I upload a file, but I can't figure out how to link my Lambda function to CloudWatch. I figured about by looking at the context object that my log group is /aws/lambda/wavToMp3 and the log stream is 2016/05/23/[$LATEST]hex_code_redacted . So I created that group and stream in CloudWatch, yet nothing is being logged to it. For the lambda function to create log stream and publish logs to cloudwatch, the lambda execution role needs to have the

When I use CloudWatch alarm to trigger an AutoScaling action, it repeatedly trigger the ASG actions. In other words, a subsequent set of N Alarms with state ALARM will trigger N actions on ASG. This behavior was not observed for a SNS action, instead it's triggering only within the 1st event when the Alarm changes from OK to ALARM. Is it possible achieve the same action behavior on SNS similar to ASG? An Amazon CloudWatch alarm will only trigger an Amazon SNS notification when the alarm enters the ALARM state . That is, it triggers only once, and only when moving from something that isn't

I'm writing a web application that has steadily increasing traffic through the day. I'd like to create an Alarm that can detect if my read / write limits have reached a certain percentage (like 80%), and then increase that limit. I will then decrease it again at midnight. I've tried creating an Alarm - "Average" seems a bit useless and is always 1.0. "Sum" is more useful so I assume i should use this. I also assume i should use Consumed Write/Read Capacity at the metric name. Problems: Sum seems to use an absolute value of "Count" for its limits. If my DynamoDB is set to 100 writes, and i

I am facing an issue. My main motive is to send an email whenever there is state change happened to ec2 instances. I tried cloud watch events directly with SNS and its work also but the email template which I am receiving is not having the proper information to understood. I was expecting Server name and its IP in the email template which SNS does not give me the option to modify it. So What I am thinking is to involve lambda so that cloudwatch events to monitor EC2 instances state change and give input to Lambda which will have customized email template which is then invoke SNS to send email

I got a $1,200 invoice from Amazon for Cloudwatch services last month (specifically for 2 TB of log data ingestion in "AmazonCloudWatch PutLogEvents"), when I was expecting a few tens of dollars. I've logged into the Cloudwatch section of the AWS Console, and can see that one of my log groups used about 2TB of data, but there are thousands of different log streams in that log group, how can I tell which one used that amount of data? On the CloudWatch console, use the IncomingBytes metrics to find the amount of data ingested by each log group for a particular time period in uncompressed bytes