DOP-C02 Practice Question 54: Service Catalog Launch Constraint
AWS Certified DevOps Engineer – Professional (DOP-C02) · Test 6 · question 4 of 10
A platform team wants application teams to be able to self-provision a standard set of resources (a VPC, an RDS instance and an Application Load Balancer) through AWS Service Catalog, without granting the application teams' own IAM identities any permission to call ec2:CreateVpc, rds:CreateDBInstance or elasticloadbalancing:CreateLoadBalancer directly. End users should only need permission to browse the portfolio and launch the product.
Which Service Catalog feature lets the product provision those resources with a more privileged role than the end user holds?
Show answer and explanation
Answer:
A launch constraint associates a portfolio's product with an IAM role. When an end user launches the product, Service Catalog assumes that role to run the underlying CloudFormation stack, so the end user only needs servicecatalog: actions to browse and launch, while the actual resource creation permissions live in the launch constraint's role, not in the end user's own IAM identity. This is the mechanism that lets a self-service portfolio provision privileged resources safely.
Option A defeats the purpose of Service Catalog entirely: giving end users direct create permissions removes the least-privilege boundary the launch constraint is meant to provide.
Option B, a template constraint, restricts which resource types or property values a product's template is allowed to declare; it governs what can be provisioned, not which role provisions it.
Option D, a StackSet, is a mechanism for deploying a template across multiple accounts and Regions from an administrator account; it does not address a single account's end users needing to self-provision without holding the underlying create permissions.
Reference: Launch constraints