Frequently Asked Questions

A CloudFormation extension is a resource type registered in the CloudFormation registry. You declare it in a template and it participates in the stack lifecycle — create, update, delete, and rollback — like any built-in AWS resource type.

Updraft Extensions are professionally maintained CloudFormation primitives that close specific capability gaps without requiring Lambda-backed custom resources, pipeline preprocessing, or out-of-band tooling. See How It Works for a full explanation of the model.

A Lambda-backed custom resource requires you to maintain a Lambda function, handle CloudFormation response signaling, implement idempotency, and debug failures through CloudWatch logs. Each one is a bespoke operational system alongside the infrastructure it was supposed to simplify.

An Updraft Extension replaces that overhead. You declare the resource type in your template; the extension handles execution, lifecycle events, and error reporting. There is no Lambda function for you to maintain.

No. You add an extension resource type to a new or existing CloudFormation template the same way you add any resource type. Existing stacks and resources are unaffected until you introduce the extension into a stack.

The SSM Parameter extension shows exactly what a template declaration looks like.

The current extension addresses data lookups — resolving SSM Parameter Store values at stack evaluation time without a Lambda-backed custom resource. See the SSM Parameter extension for details on what it covers and when to reach for it.

Additional capability categories — secure generation, orchestration, and cross-account patterns — are on the product roadmap.

Extensions are activated through the AWS CloudFormation registry. Activation requires an IAM execution role that CloudFormation can assume when running the extension, and a license key obtained at purchase.

The required IAM policy and step-by-step activation instructions are included in the documentation provided with your license.

Extensions are sold as individual commercial licenses. You purchase a license for the specific extension you need; it covers installation and use in your AWS environment under the terms issued at purchase.

The complete license agreement — including scope, account coverage, and renewal terms — is delivered with your license key. See the pricing page for current options.

Your license funds compatibility testing against new CloudFormation and AWS releases, lifecycle correctness fixes, and long-term availability with a stability commitment. Extensions that enter your infrastructure vocabulary must remain reliable as the underlying platform evolves — licensing is what makes that commitment durable.

See the pricing page for the full breakdown of what is included.