Platform engineers often deploy a single AWS CDK codebase across multiple accounts for development, staging, and production. A key limitation is that CDK cannot make decisions during deployment based on account-specific values, like those stored in AWS Systems Manager Parameter Store. This creates a gap for environment-aware infrastructure configuration.

To solve this, developers use a Lambda-backed Custom Resource. During stack deployment, CloudFormation invokes a Lambda function that reads the environment parameter from SSM. It computes the correct configuration—like setting ingress-nginx replicaCount to 1 for development or 2 for staging/production—and returns the value to CDK for the Helm chart installation.

This pattern delivers a single CDK codebase with environment-aware behavior, eliminating manual overrides. It provides deploy-time intelligence by acting on real account metadata, not synthesis-time context variables. This approach is scalable for adding other EKS add-ons like cert-manager or cluster-autoscaler, ensuring consistent, automated infrastructure across environments.