Menu

IAM and Identity Across Clouds: Why Permissions Take Longer Than the Install
📰

IAM and Identity Across Clouds: Why Permissions Take Longer Than the Install

DEV Community: azure·Nerav Doshi·about 6 hours ago
#10UtniPq
#devtoazure#devto#dev#role#identity
Reading 0:00
15s threshold

Pipeline & Prompts | Byte size guides on DevOps, Cloud and AI

DevOps from Zero #12

⚡ Byte Size Summary

Tell the difference between authentication (who is this?) and authorization (what can it do?) on AWS, Azure and GCP

Map the same idea to each cloud's vocabulary: IAM roles, managed identities and role assignments, service accounts and IAM bindings

Add an identity pre-check to your runbook so approvals stop blocking installs

The Story

A ROSA install cannot start until the customer has accepted the terms and activated the ROSA listing on the AWS Marketplace. That part takes minutes. The part after it is where the time goes.

ROSA installs with an STS-based installer role. That role carries an elevated trust policy, so the customer's cloud security team has to review it before anyone creates it. On the engagements I worked, that review took 3 to 5 days. One customer took almost 2 weeks.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.