<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Iam on fstehle.com</title>
    <link>https://fstehle.com/tags/iam/</link>
    <description>Recent content in Iam on fstehle.com</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 22 Jul 2018 14:41:51 +0200</lastBuildDate>
    <atom:link href="https://fstehle.com/tags/iam/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Handling multiple AWS accounts with aws-vault</title>
      <link>https://fstehle.com/posts/aws-multiaccount-aws-vault/</link>
      <pubDate>Tue, 10 Jul 2018 22:47:00 +0200</pubDate>
      <guid>https://fstehle.com/posts/aws-multiaccount-aws-vault/</guid>
      <description>&lt;p&gt;When using AWS in larger organizations, it&amp;rsquo;s a best practice to use &lt;strong&gt;multiple AWS accounts&lt;/strong&gt; for&#xA;different teams, applications or environments. AWS provides &lt;a href=&#34;https://aws.amazon.com/documentation/organizations&#34;&gt;AWS organizations&lt;/a&gt;&#xA;to support creating multiple AWS accounts for one organization.&lt;/p&gt;&#xA;&lt;p&gt;When using AWS organizations you usually create &lt;strong&gt;IAM users&lt;/strong&gt; in the &lt;strong&gt;master account&lt;/strong&gt; and provide&#xA;different &lt;strong&gt;IAM roles&lt;/strong&gt; in the &lt;strong&gt;member accounts&lt;/strong&gt;, which the users in the master accont can assume.&#xA;As a security best practice it is also recommended to require &lt;strong&gt;MFA&lt;/strong&gt; to assume roles in the member accounts.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
