Summary

In this chapter, we learned about one of the biggest features of CloudFormation for managing custom resource types. We managed not only to activate and use public resource types, but also to develop our own.

Resource types were built for third-party services such as those from other cloud service providers, but they also allow us to build powerful automations for our internal tools.

And that is what we did! We generated our own resource schema, built some code that communicates with our database, and adopted it to work with the CloudFormation native handler. Before submitting the resource type, we ensured it matches the contract by running an acceptance test.

Deployments using publicly accessible databases are not, however, a secure option. Think, how could you harden it and make it more secure? Would you try using IAM authentication or some secure endpoint such as RDS Proxy?

I leave these answers to you. Try out answering the following questions to test your knowledge...