<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SNS on Brian Beach</title>
    <link>http://blog.brianbeach.com/tags/sns/</link>
    <description>Recent content in SNS on Brian Beach</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 20 Jan 2014 20:50:00 -0500</lastBuildDate><atom:link href="http://blog.brianbeach.com/tags/sns/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fun with AWS CloudTrail and SQS</title>
      <link>http://blog.brianbeach.com/2014/01/fun-with-aws-cloudtrail-and-sqs.html</link>
      <pubDate>Mon, 20 Jan 2014 20:50:00 -0500</pubDate>
      
      <guid>http://blog.brianbeach.com/2014/01/fun-with-aws-cloudtrail-and-sqs.html</guid>
      <description>CloudTrail is new service that logs all AWS API calls to an S3 bucket. While the obvious use case is creating an audit trail for security compliance, there are many other purposes. For example, we might use the CloudTrail logs to keep a Change Management Database (CMDB) up date by looking for all API calls that create, modify or delete an instance. In this exercise I’ll use CloudTrail, Simple Storage Service (S3), Simple Notifications Services (SNS), Simple Queue Service (SQS) and PowerShell to parse CloudTrail logs looking for new events.</description>
    </item>
    
  </channel>
</rss>
