Terraform plan to watched AWS deploy

Play the combo

Foe: Storm Elemental, an outage, a failed deploy or a slow pipeline.

Storm Elemental

1. Storm Elemental

   The Storm Elemental blocks the way.

   What really happensIt stands for an outage, a failed deploy or a slow pipeline.

   Castellan: Context 100/100.

2. Lightning

   Lightning splits the sky and the servers go dark.

   What really happensAn outage or a broken pipeline stops everything until someone finds the cause.

   Castellan takes 7. Castellan takes 7. Castellan: Context 86/100.

3. HashiCorp Terraform MCP Server

   A seeing stone that reads the Terraform Registry before you write a line.

   What really happensLooks up current provider and module docs so the HCL uses real arguments.

   Storm Elemental takes 33.

4. Lightning

   The Storm Elemental uses Lightning.

   Castellan takes 7. Castellan takes 7. Castellan: Context 72/100.

5. Agent Toolkit for AWS (aws-core)

   A war banner that brings AWS skills and the AWS MCP Server into camp.

   What really happensBuilds and deploys the service on AWS with the AWS MCP Server.

   Storm Elemental takes 33.

6. Lightning

   The Storm Elemental uses Lightning.

   Castellan takes 7. Castellan takes 7. Castellan: Context 58/100.

7. Datadog Plugin and MCP Server

   A watchtower that reads Datadog logs, traces and monitors on request.

   What really happensChecks logs, traces and monitors for the new service after the deploy.

   Storm Elemental takes 34. Storm Elemental falls.

8. Victory

   The Storm Elemental falls.

   What really happensWrite infrastructure from current docs, deploy it, then confirm it is healthy from real telemetry. Each step needs its own account: HCP Terraform is optional, AWS and Datadog are not.