<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>security on Chris Murton</title>
    <link>https://www.chrismurton.uk/tags/security/</link>
    <description>Recent content in security on Chris Murton</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Wed, 22 Feb 2017 18:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.chrismurton.uk/tags/security/index.xml" rel="self" type="application/rss+xml" />
    
    
    <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>