<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AWS on Chris Murton</title>
    <link>https://www.chrismurton.uk/categories/aws/</link>
    <description>Recent content in AWS on Chris Murton</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Fri, 07 Apr 2017 20:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.chrismurton.uk/categories/aws/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>CloudWatch isn&#39;t just for the cloud</title>
      <link>https://www.chrismurton.uk/2017/04/07/cloudwatch-isnt-just-for-the-cloud/</link>
      <pubDate>Fri, 07 Apr 2017 20:00:00 +0000</pubDate>
      
      <guid>https://www.chrismurton.uk/2017/04/07/cloudwatch-isnt-just-for-the-cloud/</guid>
      <description>Amazon CloudWatch is an inexpensive way to monitor your solution in AWS and due to the extensive set of metrics provided for every AWS service out of the box, it&amp;rsquo;s easy and quick to adopt. Granted it&amp;rsquo;s not going to replace your enterprise monitoring solution overnight, but for those who haven&amp;rsquo;t got the time or justification to spin up their own Nagios/Zabbix/OpsView solution it can do basic event monitoring and alerting.</description>
    </item>
    
    <item>
      <title>How to rid yourself of AWS API access keys</title>
      <link>https://www.chrismurton.uk/2017/02/22/how-to-rid-yourself-of-aws-api-access-keys/</link>
      <pubDate>Wed, 22 Feb 2017 18:00:00 +0000</pubDate>
      
      <guid>https://www.chrismurton.uk/2017/02/22/how-to-rid-yourself-of-aws-api-access-keys/</guid>
      <description>It&amp;rsquo;s fairly legacy these days to use hardcoded IAM Access Key ID and Secret Access Key values to call the AWS API, which has spawned a variety of different ways to obtain and utilise IAM credentials.
Wait, what&amp;rsquo;s wrong with hardcoded credentials? The issues are numerous, some of which have come to the surface because of data breaches. Dev put AWS keys on Github or leaked access keys resulting in a $6,000 bill for starters.</description>
    </item>
    
  </channel>
</rss>