AWS Service Catalog
#153 · Level 4 · Operations and specialized areas · DevOps and Infrastructure as CodeConcept
Section titled “Concept”In AWS Service Catalog a company makes a list of approved AWS resources, and employees pick from that list and launch them. Each item on the list is called a product, which is really a CloudFormation or Terraform template. Several products make a portfolio, and a portfolio is given to specific users. With constraints, you can fix the rules a launch must follow. As a result, employees don’t need direct permission for every service.
Simple example
Section titled “Simple example”The office’s approved stationery list — ask for anything on the list and you get it, but nothing from outside is allowed.
Why it’s needed
Section titled “Why it’s needed”If everyone is allowed to build everything, controlling cost and security is hard.
Where it’s used
Section titled “Where it’s used”“Approved database”, “approved server” — employees launch them on their own while following the rules.
Azure equivalent
Section titled “Azure equivalent”Azure Managed Applications / Template Specs
Learn more
Section titled “Learn more”For details and the latest information, see the official documentation: