<?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 Built Sleek</title><link>http://builtsleek.com/categories/iam/</link><description>Recent content in IAM on Built Sleek</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 11 Dec 2023 00:00:00 +0000</lastBuildDate><atom:link href="http://builtsleek.com/categories/iam/index.xml" rel="self" type="application/rss+xml"/><item><title>Delegate AWS IAM Policy management using Boundary Policies</title><link>http://builtsleek.com/posts/ops-aws-iam-boundary-policies/</link><pubDate>Mon, 11 Dec 2023 00:00:00 +0000</pubDate><guid>http://builtsleek.com/posts/ops-aws-iam-boundary-policies/</guid><description>When responsibility for fine-grained Policy creation is delegated to an Identity such as a Developer, the Identity often expects to utilize iam:createRole to configure permissions for cloud resources.
Developer Needs Link to heading Developers frequently need to create Identities like IAM Roles during deployment to oversee permissions for various software resources. Nevertheless, the Operations admin might feel uneasy granting AdministratorAccess. Even when avoiding Admin grants, the needed Action iam:create[Role/User] would enable the developer to create an Identity that grants a seperate Policy, thereby bypassing the developer&amp;rsquo;s Identity Policy document.</description></item></channel></rss>