<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Splunk Add-on for VPC logs on AWS GovCloud in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-VPC-logs-on-AWS-GovCloud/m-p/246931#M73724</link>
    <description>&lt;P&gt;This looks like its a limitation of the AWS boto library.  When you add an input using the AWS add-on, Splunk uses a REST endpoint to list the regions for the particular service you're selecting.  That Splunk REST endpoint is using the Python boto library to list out the regions:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;elif self.callerArgs.data['aws_service'][0] in ('cloudwatch-logs', 'cloudwatchlog', 'cloudwatchlogs'):
            import boto.logs
            regions = boto.logs.regions()
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Running this bit of python code in the REPL shows:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;gt;&amp;gt;&amp;gt; import boto.logs
&amp;gt;&amp;gt;&amp;gt; regions = boto.logs.regions()
&amp;gt;&amp;gt;&amp;gt; print regions
[RegionInfo:us-east-1, RegionInfo:ap-northeast-1, RegionInfo:ap-northeast-2, RegionInfo:ap-southeast-1, RegionInfo:ap-southeast-2, RegionInfo:us-west-2, RegionInfo:us-west-1, RegionInfo:eu-central-1, RegionInfo:eu-west-1]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;As opposed to the same command for Cloudwatch metrics (notice us-gov-west-1 is listed):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;gt;&amp;gt;&amp;gt; import boto.ec2.cloudwatch
&amp;gt;&amp;gt;&amp;gt; regions = boto.ec2.cloudwatch.regions()
&amp;gt;&amp;gt;&amp;gt; print regions
[RegionInfo:us-east-1, RegionInfo:cn-north-1, RegionInfo:ap-northeast-1, RegionInfo:ap-southeast-2, RegionInfo:sa-east-1, RegionInfo:ap-southeast-1, RegionInfo:ap-northeast-2, RegionInfo:us-west-2, RegionInfo:us-gov-west-1, RegionInfo:us-west-1, RegionInfo:eu-central-1, RegionInfo:eu-west-1]
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Mon, 25 Jan 2016 23:10:40 GMT</pubDate>
    <dc:creator>Jeremiah</dc:creator>
    <dc:date>2016-01-25T23:10:40Z</dc:date>
    <item>
      <title>Splunk Add-on for VPC logs on AWS GovCloud</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-VPC-logs-on-AWS-GovCloud/m-p/246930#M73723</link>
      <description>&lt;P&gt;I'm trying to ingest VPC logs into Splunk  using the Splunk add-on for AWS 2.0.1. My VPC logs are in GovCloud, but GovCloud isn't an option on the "Add AWS CloudWatch Logs Input" dialog. Is AWS GovCloud VPC logs supported for Splunk?&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jan 2016 20:14:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-VPC-logs-on-AWS-GovCloud/m-p/246930#M73723</guid>
      <dc:creator>leontp587</dc:creator>
      <dc:date>2016-01-25T20:14:02Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for VPC logs on AWS GovCloud</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-VPC-logs-on-AWS-GovCloud/m-p/246931#M73724</link>
      <description>&lt;P&gt;This looks like its a limitation of the AWS boto library.  When you add an input using the AWS add-on, Splunk uses a REST endpoint to list the regions for the particular service you're selecting.  That Splunk REST endpoint is using the Python boto library to list out the regions:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;elif self.callerArgs.data['aws_service'][0] in ('cloudwatch-logs', 'cloudwatchlog', 'cloudwatchlogs'):
            import boto.logs
            regions = boto.logs.regions()
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Running this bit of python code in the REPL shows:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;gt;&amp;gt;&amp;gt; import boto.logs
&amp;gt;&amp;gt;&amp;gt; regions = boto.logs.regions()
&amp;gt;&amp;gt;&amp;gt; print regions
[RegionInfo:us-east-1, RegionInfo:ap-northeast-1, RegionInfo:ap-northeast-2, RegionInfo:ap-southeast-1, RegionInfo:ap-southeast-2, RegionInfo:us-west-2, RegionInfo:us-west-1, RegionInfo:eu-central-1, RegionInfo:eu-west-1]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;As opposed to the same command for Cloudwatch metrics (notice us-gov-west-1 is listed):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;gt;&amp;gt;&amp;gt; import boto.ec2.cloudwatch
&amp;gt;&amp;gt;&amp;gt; regions = boto.ec2.cloudwatch.regions()
&amp;gt;&amp;gt;&amp;gt; print regions
[RegionInfo:us-east-1, RegionInfo:cn-north-1, RegionInfo:ap-northeast-1, RegionInfo:ap-southeast-2, RegionInfo:sa-east-1, RegionInfo:ap-southeast-1, RegionInfo:ap-northeast-2, RegionInfo:us-west-2, RegionInfo:us-gov-west-1, RegionInfo:us-west-1, RegionInfo:eu-central-1, RegionInfo:eu-west-1]
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 25 Jan 2016 23:10:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-VPC-logs-on-AWS-GovCloud/m-p/246931#M73724</guid>
      <dc:creator>Jeremiah</dc:creator>
      <dc:date>2016-01-25T23:10:40Z</dc:date>
    </item>
  </channel>
</rss>

