Developing an AWS Service Catalog self-managed engine for governance
AWS Cloud Operations Blog
The article discusses how to develop a self-managed engine for AWS Service Catalog that supports custom Infrastructure as Code (IaC) tools. It provides a solution to modify the generic reference engine to work with IaC tools like Ansible, Chef, Pulumi, Puppet, and more.
Specifically, the article covers:
- Solution overview of the self-managed engine, which consists of a core and custom logic components
- Architecture and workflow of the self-managed engine core, responsible for parsing input parameters and publishing provisioning requests to SQS queues
- Architecture and workflow of the custom logic component, responsible for processing SQS messages, provisioning resources using the IaC tool, and notifying Service Catalog about results
- Steps for a Service Catalog admin to create and provision an external product type using the self-managed engine
- Conclusion highlighting the benefits of achieving consistent governance with custom IaC tooling through the self-managed engine
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Sep 10
2024
2024
Serverless Governance of Software Deployed with AWS Service Catalog
Jun 12
2024
2024
Enabling Self Service for Cloud Custodian policies on AWS using AWS Service Catalog
Dec 19
2025
2025
Search and discover governance controls with Control Catalog in AWS Control Tower
Jan 16
2026
2026
Implementing data governance on AWS: Automation, tagging, and lifecycle strategy – Part 1
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.