Skip to main content

AWS Lambda: Function to stream logs via SQS

 AWS Lambda: Function to stream logs via SQS

Summary

As part of logging and monitoring strategy it is quite important to emit data from AWS services to another service or system or aggregation layer. AWS SQS (Amazon Simple Queue Service) is a great tool to communicate between such micro-services with real-time & between software components at any volume.

Aim of this article is a snippet to stream logs via SQS to an external service (like logstash or siem tools) using Lambda Function

Pre-Reqs

  • Permission to pull data from specific SQS queue

Steps

  • Ensure lambda function can reach the SQS queue
  • Below is a snippet of code to push the data in real-time

import gzip
import json
import base64
import boto3
import time

def lambda_handler(event, context):
    sqs = boto3.client('sqs')
    account = boto3.client('sts').get_caller_identity()['Account']

    queue_url = "https://sqs.eu-west-1.amazonaws.com/12345567928/my-app-{}.fifo".format(account)
    cw_data = event['awslogs']['data']
    compressed_payload = base64.b64decode(cw_data)
    uncompressed_payload = gzip.decompress(compressed_payload)
    payload = json.loads(uncompressed_payload)
    log_events = payload['logEvents']
    log_group = payload['logGroup']
    log_stream = payload['logStream']
    event=    {}
    for log_event in log_events:
        event['AccountID']=account
        event['LogGroup']=log_group
        event['LogStream']=log_stream
        event['Log']=log_event
        response = sqs.send_message(
            QueueUrl=queue_url,
            MessageGroupId="my_logging",
            MessageDeduplicationId="%.20f" % time.time(),
            MessageBody=json.dumps(event)
        )

  • Now pull data using logstash or similar service

input {
      sqs {
         queue => "MYQUEUENAME-SQS"
         access_key_id => "ABCDEFGHIJK"
         secret_access_key => "WW1123ABCDEFGHIJK"
         region => "us-west-1"
         proxy_uri => "https://10.20.30.40:1234"
         id_field => "sqs_message_id"
         sent_timestamp_field => "sqs_sent_timestamp"
         add_field => { "[my][queue]" => "my-app-queue" }
      }
}

filter {

}

output {
    elasticsearch {
        hosts => "my_elastic_hostname"
        data_stream => "true"
    }
}

Please provide your feedback


Popular posts from this blog

Create your own Passport Photo using GIMP

This tutorial is for semi-techies who knows a bit of GIMP (image editing).   This tutorial is for UK style passport photo ( 45mm x 35 mm ) which is widely used in UK, Australia, New Zealand, India etc.  This is a quick and easy process and one can create Passport photos at home If you are non-technical, use this link   .  If you want to create United States (USA) Passport photo or Overseas Citizen of India (OCI) photo, please follow this link How to Make your own Passport Photo - Prerequisite GIMP - One of the best image editing tools and its completely Free USB stick or any memory device to store and take to nearby shop A quality Digital camera Local Shops where you can print. Normally it costs (£0.15 or 25 US cents) to print 8 photos Steps (Video Tutorial attached blow of this page) Ask one of your colleague to take a photo  of you with a light background. Further details of how to take a photo  yourself       Take multiple pictures so that you can choose from th

Syslog Standards: A simple Comparison between RFC3164 & RFC5424

Syslog Standards: A simple Comparison between RFC3164 (old format) & RFC5424 (new format) Though syslog standards have been for quite long time, lot of people still doesn't understand the formats in detail. The original standard document is quite lengthy to read and purpose of this article is to explain with examples Some of things you might need to understand The RFC standards can be used in any syslog daemon (syslog-ng, rsyslog etc.) Always try to capture the data in these standards. Especially when you have log aggregation like Splunk or Elastic, these templates are built-in which makes your life simple. Syslog can work with both UDP & TCP  Link to the documents the original BSD format ( RFC3164 ) the “new” format ( RFC5424 ) RFC3164 (the old format) RFC3164 originated from combining multiple implementations (Year 2001)

VS Code & Portable GIT shell integration in Windows

Visual Studio Code & GIT Portable shell Integration Summary Many of your corporate laptop cannot install programs and it is quite good to have them as portable executables. Here we find a way to have Portable VS Code and Portable GIT and integrate the GIT shell into VS Code Pre-Reqs VS Code (Install version or Portable ) GIT portable Steps Create a directory in your Windows device (eg:  C:\installables\ ) Unpack GIT portable into the above directory (eg it becomes: C:\installables\PortableGit ) Now unpack Visual Studio (VS) Code and run it. The default shell would be windows based Update User or Workspace settings of VS Code (ShortCut is:  Control+Shift+p ) Update the settings with following setting { "workbench.colorTheme": "Default Dark+", "git.ignoreMissingGitWarning": true, "git.enabled": true, "git.path": "C:\\installables\\PortableGit\\bin\\git.exe", "terminal.integrated.shell.windows"