Easy ReviewDOP-C02
Configuration Management and IaC37

Service Catalog

Distribute approved infrastructure templates with portfolio access, deployment constraints, and controlled version updates.

AWS Service Catalog organizes infrastructure products into portfolios. Administrators control access and deployment rules; users launch approved versions and manage their provisioned products.

Products, portfolios, and versions

AWS Service Catalog gives users approved infrastructure templates they can deploy themselves. A product is the offering, a portfolioA collection of products with configuration and access information. is its access-controlled collection, and a provisioned productA deployed instance of a catalog product, represented by a stack for CloudFormation products. is a deployed instance.

How it works

  1. An administrator imports a CloudFormation template describing resources and their relationships, or configures a Terraform provisioning engineThe component configured to create and manage resources from Terraform product configurations. for a Terraform product. ParametersAn input value a user supplies to configure resources described in a template. are inputs the user supplies at launch.
  2. The administrator adds the product to a portfolio, grants access to IAM users, groups, or roles, and configures constraintsA rule governing how a product can be deployed through a particular portfolio.. A constraint is a rule governing deployment through that portfolio.
  3. An authorized user chooses a product version and launches it. For a CloudFormation product, Service Catalog creates a stackA collection of resources created and managed together from a CloudFormation template., a collection of resources managed together.
  4. The administrator can publish additional versions. Users with portfolio access can select them.

Exam cues

  • If the question says different teams need different rules for the same template, think separate portfolios, because constraints belong to a product within a portfolio.
  • If the question says identify the deployed resources behind a CloudFormation catalog launch, think provisioned product, because that instance is a stack.

Remember

Concept Purpose
Product Infrastructure offering defined by a template
Version Template revision available for selection
Portfolio Products, access associations, and deployment rules
Provisioned product Deployed instance of a product
  • Current product types are CloudFormation, Terraform Cloud, and External. External supports Terraform Community Edition.
  • The October 2023 documentation update introduced the transition from Terraform Open Source to External. The legacy type cannot create new products or provisioned products; existing resources support only update or termination before migration.
  • IAM permissions govern catalog actions as well as portfolio access.
  • Constraints take effect immediately for versions that have not been launched.

Trap: A product and a provisioned product have different lifecycles. Publishing a version makes it available for selection; it does not describe a newly deployed stack.

From the AWS docs (12)
  • A product packages AWS resources for deployment from an infrastructure template.
  • A CloudFormation template describes resources, their relationships, and parameters that users supply at launch.
  • A portfolio groups products and manages who can use them and how.
  • Administrators grant portfolio access to IAM users, groups, or roles; IAM permissions govern catalog actions.
  • Products can have multiple template versions, and a new version becomes available to users with portfolio access.
  • For a CloudFormation product, a provisioned product is the deployed stack, a collection of resources managed together.
  • Constraints govern a product within a specific portfolio and take effect immediately for versions not yet launched.
  • Constraint types include launch, template, notification, tag update, and StackSet.
  • The product creation guide lists CloudFormation, Terraform Cloud, and External product types; External supports Terraform Community Edition.
  • Terraform Community Edition and Terraform Cloud products require a configured provisioning engine.
  • The October 2023 documentation update introduced the transition from Terraform Open Source to External.
  • Terraform Open Source is no longer valid for new products or provisioned products; existing resources support only update or termination before migration.

Launch constraints

A launch constraintA rule governing how a product can be deployed through a particular portfolio. lets AWS Service Catalog deploy approved resources with a designated IAM roleA set of permissions that a user or service can assume temporarily.. A role is a set of permissions that a service can assume temporarily, so users can request infrastructure without receiving its write permissions directly.

How it works

  1. Create a role whose trust policyA policy attached to a role identifying who may assume it. allows Service Catalog to assume it. A trust policy identifies who may use a role.
  2. Grant the role CloudFormation permissions, permissions for the resources in the template, and access to read the template from the service-owned S3 bucket. The documented read condition is s3:ExistingObjectTag/servicecatalog:provisioning=true.
  3. Attach the launch constraint to the product in its portfolioA collection of products with configuration and access information.. Choose either RoleArn, the role’s Amazon Resource NameAn identifier for a specific AWS resource. (ARN) identifying it, or LocalRoleName.
  4. Service Catalog uses that role for launches, updates, and termination. The caller still needs Service Catalog end-user permissions and portfolio access.

Exam cues

  • If the question says developers must create approved databases without direct database write permissions, think launch constraint, because Service Catalog assumes the deployment role.
  • If the question says a shared product must deploy locally in each account, think LocalRoleName, because it resolves to a role in the launching account.
  • If the question says launches work but console resource viewing fails, think user CloudFormation read permissions, because that view does not use the launch role.

Remember

  • Without a launch constraint, the user’s own permissions must cover provisioning.
  • The constraint belongs to a product in a particular portfolio.
  • A local role name must exist in both the creating account and the launching account.
  • A role ARN selects the specific role; its account provisions and pays for the resources.
  • ProvisionProduct, UpdateProvisionedProduct, and TerminateProvisionedProduct belong to the end user’s permissions.

Trap: A launch role removes the need for direct resource write permissions, but it does not grant portfolio access or console read permissions to the user.

From the AWS docs (15)
  • A launch constraint selects an IAM role that Service Catalog assumes for product launch, update, and termination.
  • An IAM role provides permissions that a user or AWS service can assume temporarily.
  • A launch constraint applies to a product-portfolio association, not every product or every portfolio.
  • Without a launch constraint, end users need their own Service Catalog, CloudFormation, and underlying service permissions.
  • A CloudFormation launch role needs CloudFormation permissions, permissions for template resources, and read access to the template in a service-owned S3 bucket.
  • The launch role trust policy must allow Service Catalog to assume the role.
  • The documented template-read policy uses s3:GetObject with s3:ExistingObjectTag/servicecatalog:provisioning equal to true.
  • ProvisionProduct, UpdateProvisionedProduct, and TerminateProvisionedProduct are end-user permissions, not permissions assigned to the launch role.
  • Viewing provisioned CloudFormation products and resources in the console requires end-user CloudFormation read access and does not use the launch role.
  • A local launch role name resolves in the launching account and must exist there and in the account that created the constraint.
  • A launch role ARN selects that specific role even for a user in another account; the role-owning account provisions and pays for the resources.
  • A launch constraint specifies either RoleArn or LocalRoleName, never both.
  • End users need portfolio access and IAM permissions for catalog actions.
  • A role trust policy identifies the principals allowed to assume the role.
  • An Amazon Resource Name (ARN) identifies a specific AWS resource.

Template constraints and TagOptions

Template constraintsA rule governing how a product can be deployed through a particular portfolio. restrict the input parametersAn input value a user supplies to configure resources described in a template. a user can choose for a CloudFormation product. TagOptionsA managed key-value template from which Service Catalog creates an AWS tag. provide approved key-value choices that become tagsA key-value label attached to a resource. at launch. Parameters configure resources; tags label them.

How it works

  1. Apply a template constraint to the product in a portfolioA collection of products with configuration and access information.. Its rules narrow values already exposed as template parameters.
  2. Define required AssertionsA rule check that must evaluate to true for supplied template parameters to be accepted., the checks that must pass. Add an optional RuleCondition to decide when the checks apply; without it they always apply.
  3. Associate TagOptions with the portfolio, product, or both. Service Catalog collects them at launch and turns selected values into tags.
  4. If both levels define the same tag key, Service Catalog offers values allowed at both levels. An empty intersection produces a conflict-marker tag for administrator correction.
  5. A TransformA CloudFormation template section specifying processing that modifies template content. section requests template processing before deployment. If present, the catalog console skips Rules evaluation; CloudFormation evaluates those rules after processing the transform.
  6. Align TagOptions and optional user tags with enforced Organizations tag policies, which define tag spelling and allowed values across accounts.

Exam cues

  • If the question says restrict instance sizes differently for each team, think template constraints in each portfolio, because they narrow launch parameters across product versions.
  • If the question says approved cost allocation labels, think TagOptions, because selected values become tags on the provisioned productA deployed instance of a catalog product, represented by a stack for CloudFormation products..
  • If the question says invalid parameters pass the catalog console for a transformed template, think CloudFormation Rules evaluation after Transform, because the console skips that evaluation.

Remember

Requirement Feature
Restrict CloudFormation input values Template constraint
Offer approved tag keys and values TagOptions
Define tagging rules across accounts Organizations tag policy
Allow later resource tag changes Tag update constraint
  • Template constraints cover subsequent launches of all versions in that portfolio.
  • Template constraints and TagOptions do not support Terraform Open Source or Terraform Cloud products.
  • A tag policy blocks noncompliant operations only where enforcement applies.

Trap: TagOption values on a product and its portfolio use an intersection, not a union. Disjoint values produce a conflict marker; an enforced tag policy can also reject noncompliant tags.

From the AWS docs (14)
  • A template constraint narrows CloudFormation parameter values for a product in a portfolio.
  • Template constraints apply immediately to subsequent launches of every version in that portfolio, not the same product in another portfolio.
  • Template constraints do not support Terraform Open Source or Terraform Cloud products.
  • A rule has required Assertions and an optional RuleCondition; without a condition its assertions always apply.
  • If a template contains Transform, the Service Catalog console skips Rules evaluation; CloudFormation evaluates the rules after the transform and invalid parameters fail the stack operation.
  • A TagOption is a managed key-value template for an AWS tag, associated with a product or portfolio.
  • TagOptions do not support Terraform Open Source or Terraform Cloud products.
  • At launch Service Catalog gathers product and portfolio TagOptions and applies the selected value for each key as a tag.
  • For the same key on both portfolio and product, available TagOption values are their intersection.
  • If the intersection is empty, Service Catalog uses a conflict-marker tag value so an administrator can find and correct the conflict.
  • Organizations tag policies define tag key and value rules; enforcement must be selected to block noncompliant operations on specified resource types.
  • A launch with noncompliant TagOptions or custom tags can fail when Organizations tag policy enforcement applies.
  • A tag update constraint controls whether new product or portfolio tags reach resources during a provisioned product update.
  • The CloudFormation Transform section specifies processing macros that modify template content.

Notification and tag update constraints

Notification constraintsA rule governing how a product can be deployed through a particular portfolio. deliver stackA collection of resources created and managed together from a CloudFormation template. events to Amazon Simple Notification Service (SNS). TagA key-value label attached to a resource. update constraints control whether tag changes can reach resources in an existing provisioned productA deployed instance of a catalog product, represented by a stack for CloudFormation products.. A tag is a key-value label attached to a resource.

How it works

  1. For stack notifications, create an SNS topicA named communication channel that delivers published messages to subscribers., a named destination to which subscribers can receive messages. For email delivery, add and confirm an email subscription.
  2. Add a notification constraint to the product in its portfolioA collection of products with configuration and access information. and select the topic.
  3. For resource tag changes, add a tag update constraint and allow or disallow user tag updates.
  4. When updates are allowed, update the provisioned product to apply new tags associated with its product or portfolio.

Exam cues

  • If the question says email the operations team about catalog stack events, think notification constraint and confirmed SNS subscription, because the constraint chooses the event destination.
  • If the question says new portfolio tags have not reached running resources, think tag update constraint and provisioned product update, because that update applies the new tags.

Remember

  • Notification constraints do not support Terraform Open Source or Terraform Cloud products.
  • Tag update constraints do not support Terraform Open Source products.
  • Allowing tag updates and performing a product update are separate actions.

Trap: A notification constraint sends stack events. A tag update constraint governs resource tags; it does not configure an event destination.

From the AWS docs (8)
  • A notification constraint selects an SNS topic to receive CloudFormation stack event notifications.
  • To receive email notifications from the SNS topic, create an email subscription and confirm it.
  • Notification constraints do not support Terraform Open Source or Terraform Cloud products.
  • A tag update constraint allows or disallows end-user tag updates on resources associated with a provisioned product.
  • When tag updates are allowed, new product or portfolio tags reach provisioned resources during a provisioned product update.
  • Tag update constraints do not support Terraform Open Source products.
  • An SNS topic is a communication channel that delivers published messages to subscribers.
  • A tag is a key-value label attached to a resource.

Provisioned product updates

Publishing an AWS Service Catalog version changes what users can select. Updating a provisioned productA deployed instance of a catalog product, represented by a stack for CloudFormation products. changes an existing deployment. Keeping these actions separate lets teams release a corrected template before moving running resources to it.

How it works

  1. Publish the changed template as a new product version. For automated publication, connect a Git-synced product to an authorized repository, branch, and template file path.
  2. A commit to the connected template creates a new version automatically. GitHub, GitHub Enterprise, and Bitbucket are supported repository providers. Last Sync Status and the version’s source revision ID help trace publication.
  3. Update each provisioned product with the selected version and parametersAn input value a user supplies to configure resources described in a template.. For a CloudFormation product, this changes its stackA collection of resources created and managed together from a CloudFormation template..
  4. Use version status and guidance to control selection. Use Terminate when the provisioned resources are no longer needed.

Exam cues

  • If the question says template commits must publish catalog versions, think Git-synced product, because committed template changes create versions automatically.
  • If the question says running deployments need a corrected template, think provisioned product update, because publication alone only makes a version available.
  • If the question says block new launches while preserving existing deployments, think Deprecated guidance on an active version, because it blocks new launches without terminating existing products.

Remember

Setting Effect
Active status Version appears and supports launch
Inactive status Version is hidden; existing deployments are unaffected
Deleted status Version is removed; deletion cannot be undone
None guidance Default guidance; launch and update are allowed
Deprecated guidance Blocks new launches; existing products can update using the same or a new version
  • Updates require Available or Tainted state.
  • Guidance affects only active versions.
  • Terminate deletes resources. Ignore errors can leave resources unmanaged if deletion fails.

Trap: A successful repository sync proves that a version was published. It does not prove that existing provisioned products adopted that version.

Template publication and deployment update are separate
commit + sync1explicit update2Template repoProduct versionRunning stack
  1. A committed template change creates a product version through Git sync.

  2. A user or automation updates the provisioned product to adopt the selected version.

From the AWS docs (13)
  • Updating a product template creates a new product version available to users with portfolio access.
  • A provisioned product requires an update to adopt a new version or changed parameters.
  • Only Available or Tainted provisioned products can be updated; starting, updating, terminating, or failed products cannot.
  • An Active version appears in the version list and can be launched.
  • An Inactive version is hidden from the version list without affecting existing provisioned products.
  • Deleting a version removes it from the version list and cannot be undone.
  • Version guidance defaults to None and only affects active versions.
  • Deprecated guidance blocks new launches; existing products on that version can update using their existing version or a new version.
  • Git-synced products connect to a template in GitHub, GitHub Enterprise, or Bitbucket; committed changes automatically create a product version.
  • Git sync requires an authorized connection plus the repository, branch, and template file path.
  • Last Sync Status shows synchronization details, and version details include the source revision ID.
  • Terminate removes a provisioned product and its resources; Ignore errors can stop management even when underlying resource deletion fails.
  • For CloudFormation products the deployed instance is a stack managed as a unit.

StackSet constraints

A StackSetA collection of stacks deployed from a common template across target accounts and Regions. constraintA rule governing how a product can be deployed through a particular portfolio. lets an AWS Service Catalog product deploy across accounts and Regions through CloudFormation StackSets. A stack set manages related stacksA collection of resources created and managed together from a CloudFormation template., each deployed in a target account and Region.

How it works

  1. Add a StackSet constraint to a CloudFormation product in its portfolioA collection of products with configuration and access information..
  2. Configure the target account list, Region list, and Region deployment order.
  3. Configure the StackSet administrator and execution roles. The administrator role manages target accounts; the constraint parametersAn input value a user supplies to configure resources described in a template. include AdminRole and ExecutionRole.
  4. A product launch creates a CloudFormation stack set using those deployment settings.

Exam cues

  • If the question says one catalog launch must deploy into multiple accounts and Regions, think StackSet constraint, because it launches a stack set with configured targets.
  • If the question says adding a StackSet constraint fails on a product that has a launch constraint, think incompatible constraint types, because LAUNCH and STACKSET cannot coexist on that association.

Remember

  • Settings include AccountList, RegionList, AdminRole, and ExecutionRole.
  • Omitting an administrator role uses the default StackSet ARNAn identifier for a specific AWS resource..
  • A product-portfolio association can have only one StackSet constraint.
  • Terraform Open Source products do not support StackSet constraints.
  • AutoTagsTags that Service Catalog automatically applies to identify a provisioned resource's origin., the origin metadata tagsA key-value label attached to a resource. Service Catalog adds automatically, are not supported with CloudFormation StackSets.

Trap: Sharing a portfolio makes products available in recipient accounts. A StackSet constraint deploys a product across target accounts and Regions. Choose based on whether the question asks for distribution or deployment.

One catalog launch deploys to StackSet targets
launch122Service CatalogStackSetaccounts + RegionsTarget stack Aaccount / RegionTarget stack Baccount / Region
  1. Service Catalog launches a CloudFormation stack set using its StackSet constraint.

  2. StackSet deployment settings select target accounts, Regions, and Region order.

From the AWS docs (9)
  • A StackSet constraint launches a CloudFormation stack set, which deploys the product to multiple accounts and Regions.
  • The constraint configures target accounts, target Regions, and Region deployment order.
  • The administrator selects an IAM StackSet Administrator Role; if omitted, StackSets uses its default ARN.
  • StackSet constraint parameters include AccountList, RegionList, AdminRole, and ExecutionRole.
  • A product-portfolio association cannot have both LAUNCH and STACKSET constraints or multiple STACKSET constraints.
  • StackSet constraints do not support Terraform Open Source products, and AutoTags do not support CloudFormation StackSets.
  • AutoTags are origin metadata tags automatically applied to provisioned resources by Service Catalog.
  • A StackSet groups stacks deployed from a common template across specified accounts and Regions.
  • Portfolio sharing distributes catalog products across accounts without itself launching them.

Portfolio sharing and local access

PortfolioA collection of products with configuration and access information. sharing distributes AWS Service Catalog products to other accounts while the source administrator keeps control of the catalog. An imported portfolio is a reference that follows source changes. A local portfolio belongs to the recipient account.

How it works

  1. Enable Service Catalog trusted access for Organizations integration when using organizational sharing. Choose an account, organizational unitA grouping within an organization that can be used as a portfolio-sharing target. (OU), or the organization. An OU groups accounts within an organization.
  2. Share the portfolio. Account-to-account recipients import it in the same Region; Organizations recipients do not need a manual import.
  3. Grant recipient users, groups, or roles access. Optional PrincipalAn identity, such as an IAM user or role, that can receive portfolio access. Name Sharing for Organizations automatically associates matching local IAM principals, the identities receiving access.
  4. If the product uses a local launch roleA set of permissions that a user or service can assume temporarily. name, create that role in the source and launching accounts. Service Catalog assumes the launching account’s role to provision resources.
  5. Source catalog changes propagate to the imported reference. Existing provisioned productsA deployed instance of a catalog product, represented by a stack for CloudFormation products. need their own update to adopt a new product version.

Exam cues

  • If the question says centrally maintain a catalog across accounts, think portfolio sharing, because imported references stay synchronized.
  • If the question says a visible catalog is unavailable to developers, think local principal access and launch role checks, because sharing alone does not authorize everyone.
  • If the question says one recipient needs a different launch role, think local portfolio with a replacement launch constraintA rule governing how a product can be deployed through a particular portfolio., because that is the documented override path.

Remember

Distribution Result Catalog update behavior
Account share Imported reference after recipient import Source changes propagate
Organizations share Imported reference without manual import Source changes propagate
StackSetsA collection of stacks deployed from a common template across target accounts and Regions. catalog deployment Separate catalog copy Redeploy catalog changes
  • Imports use the same Region. Imported products cannot be re-shared.
  • Recipients can add local access but cannot edit imported products or constraints.
  • Removing a shared product stops future launches; running provisioned products remain.

Trap: Ordinary sharing does not inherit users, groups, and roles. Principal Name Sharing is an explicit Organizations option that associates matching local identities.

Share a portfolio and launch with a local role
Hub account (catalog admin)Spoke accountnew versionshare1launch2assume3provision4Portfolioproducts + constraintsiProduct versionsv1, v2 templatesiImported portfoliostays in synciEnd userlaunch requestiLaunch rolelocal role nameiProvisioned productCloudFormation stacki
  1. The administrator shares the portfolio. Account-to-account recipients import it; Organizations recipients do not need a manual import.

  2. An authorized user in the spoke account launches a product version.

  3. The launch constraint tells Service Catalog which role to assume.

  4. Service Catalog provisions the stack with that role's permissions, not the user's.

Box details (6)
Portfolio

The original (shared) portfolio. Launch and template constraints set here travel with the share.

Product versions

A template change is a new version. Existing provisioned products stay on their version until someone updates them.

Imported portfolio

An imported portfolio stays in sync with the original in the same Region. The recipient grants local access, unless Principal Name Sharing already associates matching principals.

End user

The user needs portfolio access and Service Catalog end-user actions. CloudFormation console resource viewing separately needs user read permissions.

Launch role

A local role name resolves to the role in the launching account. That name must also exist in the constraint-creating account.

Provisioned product

The running instance of a product version. Update or terminate it through Service Catalog.

From the AWS docs (15)
  • Account-to-account and Organizations sharing provide an imported portfolio reference kept in sync with the original.
  • Deploying catalog copies with CloudFormation StackSets requires redeployment to propagate catalog changes.
  • Recipients can grant local IAM users, groups, and roles access to an imported portfolio or distribute imported products through a local portfolio.
  • Recipients cannot edit imported products or constraints or re-share imported products.
  • To override a shared launch constraint, add the product to a local portfolio and apply a different launch constraint there.
  • Removing a shared product removes it from imported and associated local portfolios; existing provisioned products continue running.
  • Portfolio imports occur in the same Region between the source and recipient accounts.
  • Users, groups, and roles are not inherited by ordinary portfolio sharing.
  • Optional Principal Name Sharing is available for Organizations shares and automatically associates matching local IAM principals.
  • Account-to-account sharing requires a recipient import, while Organizations sharing needs no manual import.
  • Organizations shares can target an account, an OU, or the whole organization; sharing to a parent OU includes its accounts and child OUs.
  • Service Catalog trusted access enables Organizations integration for portfolio sharing.
  • A local role name resolves in the launching account and must exist there and in the account that created the constraint.
  • Service Catalog assumes the launch role to provision the product; end-user actions and console CloudFormation read access remain caller permissions.
  • New product template versions become available for users to select; provisioned products need an update to adopt them.

Flashcards

tap to flip
Answer

·

All 37 cards as a list

Auditors need to know who can launch an AWS Service Catalog product and which role and parameter restrictions apply. Where should they look?

The portfolio access associations and the product constraints in that portfolio. IAM permissions also govern catalog actions.

A platform team needs one AWS Service Catalog template offered to different teams with different launch rules. What should it configure?

Put the product in separate portfolios and configure access and product constraints in each portfolio.

In AWS Service Catalog, how does a product version differ from a provisioned product?

A version is an available template revision. A provisioned CloudFormation product is a running stack created from a selected version.

A platform team needs approved infrastructure templates that users can deploy with their own launch inputs. What should it use in AWS Service Catalog?

A product based on a CloudFormation template. The template describes the resources and accepts parameters at launch.

How can an organization control who can deploy approved AWS Service Catalog products?

Group products in a portfolio and grant access to IAM users, groups, or roles. IAM permissions also govern catalog actions.

Developers must launch an RDS product through AWS Service Catalog without direct RDS write permissions. What should the administrator configure?

A launch constraint with an IAM role that can provision the product. Give developers portfolio access and the required Service Catalog end-user actions.

What happens when an AWS Service Catalog CloudFormation product has no launch constraint?

The end user launches and manages it with their own credentials and needs Service Catalog, CloudFormation, and resource permissions.

What must an AWS Service Catalog CloudFormation launch role permit?

Its trust policy must allow Service Catalog to assume it. Its permissions must cover CloudFormation, template resources, and template reads from the service-owned S3 bucket. Catalog end-user actions belong to the caller.

A shared AWS Service Catalog product must deploy into each recipient account using a role with the same name. Should the constraint specify a name or an ARN?

Use LocalRoleName. That role must exist in the creating account and each launching account. An ARN selects a specific role.

Does an AWS Service Catalog launch constraint automatically cover every product in a portfolio or the same product in other portfolios?

No. Apply it separately to each product-portfolio association.

An AWS Service Catalog user can launch a CloudFormation product through a role but cannot view its resources in the console. What permission is missing?

Check the user's CloudFormation read permissions. Console resource viewing does not use the launch role.

How can an AWS Service Catalog administrator restrict EC2 instance-type parameters without editing a product template for each team?

Apply a template constraint to the product in each team's portfolio. It covers all versions for subsequent launches and does not support Terraform Open Source or Terraform Cloud products.

An AWS Service Catalog administrator needs restricted parameter choices and approved Environment and CostCenter tag values. What should they configure?

Template constraints for parameters and TagOptions for tag choices on the product or portfolio. Align tags with any enforced Organizations tag policy. Use a tag update constraint for later resource tag changes.

AWS Service Catalog portfolio TagOptions allow Environment=dev or test, while its product allows Environment=test or prod. What can users choose?

Only test. Values for the same key are intersected across product and portfolio.

An AWS Service Catalog template contains Transform and invalid Rules parameters pass the console check. Will provisioning necessarily succeed?

No. CloudFormation evaluates the rules after applying the transform and fails the stack operation for invalid values.

What makes an AWS Service Catalog template constraint rule conditional?

An optional RuleCondition. Assertions are required; without a condition they always apply.

Which AWS Service Catalog constraint sends CloudFormation stack events to an SNS topic?

A notification constraint. It is not supported for Terraform Open Source or Terraform Cloud products.

What does an AWS Service Catalog tag update constraint control?

Whether users can update tags on provisioned resources. When allowed, new product or portfolio tags are applied during a provisioned product update.

An operations team needs email notifications about AWS Service Catalog CloudFormation stack events. What should it configure?

Create an SNS topic and a confirmed email subscription, then attach a notification constraint naming the topic.

An administrator adds portfolio tags, but existing AWS Service Catalog resources still have their old tags. What should the team do?

Allow tag updates with a tag update constraint and update the provisioned product. New tags are applied during that update.

How should an AWS Service Catalog administrator release a changed template without automatically altering running deployments?

Publish a new product version. Update each provisioned product separately to adopt it. Inactive versions are hidden; Deprecated guidance blocks new launches of an active version.

How does an AWS Service Catalog user adopt a new product version, and what does Terminate do?

Use Update on the provisioned product with the new version and parameters. Terminate removes the provisioned product and its resources; Ignore errors can leave undeleted resources unmanaged.

A central team publishes a corrected AWS Service Catalog template, but existing deployments still use the old template. What must happen?

Update each provisioned product to the new version. Publishing the version only makes it available.

A platform team wants AWS Service Catalog product versions published automatically after template commits to GitHub. What should it configure?

A Git-synced product with an authorized connection, repository, branch, and template file path. Commits publish versions; deployed products still need updates.

Can an AWS Service Catalog user update a provisioned product while it is starting or in Failed state?

No. Updates require Available or Tainted state.

What is the default AWS Service Catalog version guidance, and does Deprecated guidance hide the version?

None is the default. Deprecated guidance applies only to active versions and blocks new launches; Inactive status hides a version.

How does AWS Service Catalog configure accounts, Regions, and deployment order for a product launched as a StackSet?

Use a StackSet constraint on the product in its portfolio, with account and Region settings and the StackSet permissions configuration.

A team needs an AWS Service Catalog CloudFormation product deployed to several named accounts and Regions through one catalog launch. What should the administrator configure?

A StackSet constraint with the target accounts, Regions, Region order, and StackSet roles.

An AWS Service Catalog administrator tries to add a StackSet constraint where a launch constraint already exists. Why does the request fail?

LAUNCH and STACKSET constraints cannot coexist on the same product-portfolio association.

Which AWS Service Catalog product type does the StackSet constraint guide explicitly exclude?

Terraform Open Source products. The guide also states that AutoTags are unsupported with CloudFormation StackSets.

How does sharing an AWS Service Catalog portfolio differ from deploying catalog copies with StackSets?

Sharing maintains a reference synchronized with the source. Catalog copies deployed with StackSets need redeployment for catalog changes.

What can a recipient administrator change in an imported AWS Service Catalog portfolio?

Grant local principal access and distribute its products through local portfolios. Imported products and constraints cannot be edited, and imported products cannot be re-shared.

Does an AWS Service Catalog portfolio share automatically grant every user in the recipient account access?

No. Grant local access, or use optional Organizations Principal Name Sharing to associate matching local principals. Neither grants all users access.

A shared AWS Service Catalog launch constraint must be replaced for one recipient account. How can its administrator do this?

Add the product to a local portfolio and apply a different launch constraint there.

What happens to existing AWS Service Catalog provisioned products when their product is removed from a shared portfolio?

They keep running. The product is removed from imported and associated local portfolios and is unavailable for future launches.

A platform team needs centrally maintained AWS Service Catalog products with deployments in each member account. What sharing and role configuration fits?

Share the portfolio through Organizations, grant local access or enable matching Principal Name Sharing, and use a local launch role name available in every launching account and the source account.

A shared AWS Service Catalog portfolio is visible in a member account but developers cannot launch products. What should its administrator check?

Check local portfolio access and whether any enabled Principal Name Sharing matches their IAM principals. Also check the required local launch role.

You finished every topic of DOP-C02!

Your badge turned gold. Next step: book the exam on AWS. Once you pass, add yourself to Who passed.

Share

Share that you finished this certification

I finished every topic of AWS Certified DevOps Engineer - Professional (DOP-C02) on Easy Review. Come study too!