aws-cdk-development

Define a NodejsFunction or PythonFunction construct with an entry point, then create a DynamoDB table and connect them using table.grantReadWriteData(lambda). Pass the table name via environment variables rather than hardcoding it in your handler code.

Use cdk-nag as a synthesis-time check by adding AwsSolutionsChecks as an Aspect to your CDK app, then run cdk synth. The included validate-stack.sh script adds meta-level checks for template size, resource counts, and synthesis success.

No, let CDK generate resource names automatically unless external systems require stable names. Automatic naming enables parallel deployments, stack cloning, and multiple environments in the same account without naming conflicts.

Yes, use the PythonFunction construct from @aws-cdk/aws-lambda-python-alpha, which handles dependency packaging and bundling automatically. Point it at your source directory and handler file, and CDK manages the rest.

Deployment fails when explicit resource names like functionName or bucketName collide with existing resources in the same region. Remove explicit names and let CloudFormation generate unique identifiers per stack.

cdk-nag is a validation library that checks CDK stacks against AWS best practice rules at synthesis time. Add it to every CDK project for security and compliance feedback, and document legitimate exceptions using NagSuppressions with reasons.