All Topics
All Topics
Technology
Technology
AI
AI
Business
Business
Entertainment
Entertainment
News
News
Programming
Programming
Science
Science
Design
Design
Environment
Environment
Finance
Finance
Crypto
Crypto
Politics
Politics
Sports
Sports
Education
Education
Gaming
Gaming
Art
Art
Music
Music
Health
Health
Security
Security
Books
Books
Food
Food
Travel
Travel
Personal
Personal
Bluesky
Twitter

Solving the Chicken-and-Egg Problem of Self-Referencing AWS CDK Deployments

By

Joanne Skiles

1mo ago· 3 min readenInsight

Summary

This article addresses a common challenge faced by AWS CDK (Cloud Development Kit) users: the chicken-and-egg problem where certain infrastructure resources (like ALB endpoints, service URLs, and auto-assigned DNS names) are only known after CloudFormation has provisioned them, not at CDK synthesis time. The article explains that this is not a bug but a fundamental issue, and hints at a solution for handling resources that need to know about themselves after deployment.

Source

bskySolving the Chicken-and-Egg Problem of Self-Referencing AWS CDK Deploymentsdev.to

Key quotes

· 4 pulled
There is a moment that catches a lot of people out who are new to AWS CDK.
This is not a CDK bug. It is a genuine chicken-and-egg problem, and once you understand it, the solution is straightforward-ish.
Some resources only exist after CloudFormation has provisioned them: ALB endpoints, service URLs, and auto-assigned DNS names.
These values are not known at the cdk synth time.
Snippet from the RSS feed
There is a moment that catches a lot of people out who are new to AWS CDK. You deploy a service, the...

You might also wanna read

Comments

Sign in to join the conversation.

No comments yet. Be the first.