QuestionQ31

VerifiedDesign Solutions for Organizational Complexity

A company has an application that uses Amazon EC2 instances in an Auto Scaling group. The quality assurance (QA) department needs to launch a large number of short-lived environments to test the application. The application environments are currently launched by the manager of the department using an AWS CloudFormation template. To launch the stack, the manager uses a role with permission to use CloudFormation, EC2, and Auto Scaling APIs. The manager wants to allow testers to launch their own environments, but does not want to grant broad permissions to each user.

Which set up would achieve these goals?

Explanation

AWS Service Catalog with launch constraints is the standard pattern for allowing self-service provisioning while restricting permissions. Launch constraints grant resource-creation permissions to the Service Catalog engine without giving those permissions directly to end users, achieving granular access control. Users receive only Service Catalog API permissions, not CloudFormation or EC2 permissions directly, minimizing the blast radius of permissions.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!