Infrastructure Architecture Patterns

Patterns and conventions for the Arda-cards/infrastructure repository — the AWS CDK codebase that defines every Arda cloud resource. Pages in this section describe the structural rules that keep the IaC codebase navigable, reusable, and safe to evolve as new Apps, Stacks, and Constructs are added.

Pages in this section

• IaC Functional Design — the layered script → instances → apps → stacks → constructs architecture, layer responsibilities, the dependency-direction rule, and the anti-patterns it rules out.

More pages will join this section as the codebase grows: a Construct catalog, a Stack catalog, the deployment topology / runner taxonomy, and per-App design notes (Root, Corporate, the Platform-Partition Apps).

See also

• Design Pattern Index — the parent catalog of architectural patterns.
• Implementation Patterns — code-level patterns; the IaC layer hosts its own Configuration / Props / Built three-interface pattern at the construct boundary.
• AWS CDK Infrastructure — technology reference for CDK mechanics in this codebase: construct conventions, cross-stack export keys, custom resources, removal policies, cdk import, assertions, and common pitfalls. The export-key pattern subsection covers the legacy/newer form distinction, the -API-/-I- marker enforcement, and publish-from-app-wiring discipline in detail.
• cdk-infrastructure skill — agent-loaded skill that pulls these conventions into a working session when CDK code is being authored or reviewed.
• The infrastructure repository’s own knowledge-base/cdk-construct-patterns.md — repo-local mechanical conventions (Configuration/Props/Built shape, ExportKeys, publish(), naming) that this section’s pages reference rather than duplicate.