Beyond Native Types

When a Native Resource Type Is Not Enough

The registry's resource types (Registry and Providers) cover AWS 24 's services, but not every deployment step is a service resource: seeding reference data, emptying a bucket so that its stack can delete it, calling a third-party API. Check the cheaper options first. A Parameter Store value arrives through an AWS::SSM::Parameter::Value<String> parameter, a generated password through AWS::SecretsManager::Secret's GenerateSecretString, and many third-party services publish registry extensions. What remains is work that must follow the stack's life cycle. A pipeline script runs once, whatever the stack does; a custom resource runs when the stack creates it, again when its properties change, and once more when the stack is deleted. The price is code to maintain, and a stack that waits on it.