Refactoring to L3 constructs without changing resource IDs

[ajspetner]

I have a single-file CDK stack which has ballooned out of control. I want to organize the resources into custom L3 constructs. However I cannot have the resource IDs change. Additionally, hard-coding the resource names is very inconvenient, given that I have multiple instances of the stack on different AWS accounts (dev, prod, etc).

According to #482 this can be achieved by setting the id of the L3 construct to "Default", but the issue is that I can only do this for one construct, or I will get the error "There is already a Construct with the name 'Default'..."

Is there a way to get this "Default" functionality for multiple constructs in the same stack? There must be a way to organize my stack without having the IDs changed and the resources (including RDS and EC2 instances) recreated.