Understanding the CloudFormation registry
The journey of the CloudFormation registry began in 2019, when the private registry was announced and released (along with other major and important updates; for more details, see https://aws.amazon.com/blogs/aws/cloudformation-update-cli-third-party-resource-support-registry/). This update introduced a centralized approach to modeling, building, and maintaining custom resources.
The first and main reason was to enable AWS service teams to onboard newly developed services faster. Previously, this was the responsibility of the CloudFormation team itself, and handing service onboarding tasks over to the service teams with the right tool in place improved the speed of onboarding to CloudFormation. Another good use was to centrally maintain custom resources in a single place.
Two years later, AWS released the public registry – a registry for resource types developed by various software vendors, such as MongoDB, Atlassian, DataDog,...
