Short answer: the ACXD SDK is the only infrastructure-as-code path for ACXD itself today. There's no CloudFormation support — and because the AWS CDK synthesizes to CloudFormation, CDK can't manage ACXD either. Terraform, CloudFormation, and the CDK can only manage the surrounding AWS resources used for customisation — not the ACXD application, flows, nodes, or guardrails.
What's Available Today
| IaC tool | Can it manage ACXD itself? |
|---|---|
| ACXD SDK | Yes — the only way to manage ACXD applications, builds, and deployments as code |
| CloudFormation (CFN) | No — no CFN support for ACXD at all |
| AWS CDK | No for ACXD itself — CDK synthesizes to CloudFormation, so with no CFN support it can only manage surrounding/customisation resources |
| Terraform | No for ACXD itself — only for surrounding/customisation resources (e.g. Lambda, IAM) the application depends on |
The key distinction: "IaC for ACXD" and "IaC for the AWS resources around ACXD" are two different things. Terraform, CloudFormation, and the AWS CDK handle the latter — the supporting Lambda functions, IAM roles, and integrations. Only the ACXD SDK handles the former — the actual conversational application, its flows, nodes, prompts, and guardrails.
Why the SDK Is the Answer (For Now)
The ACXD SDK lets you treat the application as code: build it, package it into an immutable build, deploy it to an environment, diff versions, and roll back — all programmatically. That's what makes version control and CI/CD possible for ACXD today, even without CloudFormation or a Terraform provider for the application layer.
Note on scope: the SDK is currently Node/TypeScript, which is worth factoring in if your team standardises on Python, Java, or .NET. For the deeper dive, see CI/CD for ACXD: the SDK, MCP tools, and what to explore.
Q&A
Can you manage ACXD as infrastructure as code?
Partly. Today the only infrastructure-as-code path for ACXD itself is the ACXD SDK, which lets you define and deploy applications, flows, and guardrails programmatically as code. There is no CloudFormation support for ACXD, and Terraform/CloudFormation only cover the surrounding AWS resources, not the ACXD application itself.
Does ACXD support CloudFormation?
No. There is no CloudFormation (CFN) support for ACXD at the moment. You cannot define or deploy an ACXD application through a CloudFormation template. The SDK is the mechanism for managing ACXD as code.
Can I use Terraform for ACXD?
Not for the ACXD application itself. Terraform (and CloudFormation) can only manage the surrounding, supporting AWS resources used for customisation — such as Lambda functions, IAM roles, or integrations the application calls — not the ACXD application, flows, nodes, or guardrails. Those are managed through the ACXD SDK.
Can I use the AWS CDK for ACXD?
Not for the ACXD application itself. The AWS CDK synthesizes to CloudFormation under the hood, and because there is no CloudFormation support for ACXD, the CDK can't manage the ACXD application, flows, nodes, or guardrails either. Like Terraform, it can only manage the surrounding, supporting AWS resources. The ACXD SDK remains the only IaC path for ACXD itself.
What is the ACXD SDK?
The ACXD SDK is a Node/TypeScript package that lets you treat ACXD as infrastructure as code — building applications, packaging them into immutable builds, deploying to environments, diffing, and rolling back programmatically. It is the foundation for putting ACXD under version control and CI/CD today.
This changes over time: ACXD is evolving quickly. CloudFormation support or a Terraform provider for the application layer may arrive in future — always confirm the current state against the official AWS documentation before planning your IaC approach.