Axis IS CDK — Extending

The Axis IS CDK principle isn’t just how the framework is built — it’s how you should extend it. When you write your own construct or stack alongside Axis, follow the same rules and your code inherits the same no-ceiling ergonomics.

Extend, never wrap

Your construct props should extend Omit<CdkProps, ...fields-you-control>, exposing every CDK prop you don’t deliberately own:

export interface MyThingProps extends Omit<
  someservice.CfnThingProps,
  "thingName" | "removalPolicy"
> {
  // your additions
}

This gives consumers of your construct the same full autocomplete and same-day access to new CDK props that Axis constructs give.

No index signatures

[key: string]: unknown is prohibited in Axis config types because it kills autocomplete and lets typos compile silently. Keep your extension types just as strict.

Explicit wiring

Every wiring decision should be visible at the call site — name your trigger types, import your configs explicitly, and never match things up by naming convention (it breaks silently when a name changes).

Where to go next

• Extend an Abstract Stack to subclass a framework stack.
• Add Your Own Stack for a fully independent stack.