(elbv2): Cross stack references missing from BaseLoadBalancer

Can’t reference an ALB created in Account A on a Stack B in Account B to create R53 Record.

Reproduction Steps

const ENV1 = { account: '11111', region: 'us-east-1' };
const ENV2 = { account: '2222', region: 'eu-west-2' };

class ProducerStack extends Stack {
  public readonly alb: ApplicationLoadBalancer;

  constructor(scope: Construct, id: string) {
    super(scope, id, { env: ENV1 });

    this.alb = new elbv2.ApplicationLoadBalancer(this, 'ApplicationLoadBalancerPrivate', {
      loadBalancerName: cdk.PhysicalName.GENERATE_IF_NEEDED,
    });
  }
}

interface ConsumerStackProps {
  readonly alb: ApplicationLoadBalancer;
}

class ConsumerStack extends Stack {
  constructor(scope: Construct, id: string, props: ConsumerStackProps) {
    super(scope, id, { env: ENV2 });

    new route53.ARecord(this, 'AliasRecord', {
      zone,
      target: route53.RecordTarget.fromAlias(new alias.LoadBalancerTarget(props.alb)),
    });
  }
}

const producer = new ProducerStack(app, 'producer');
const consumer = new ConsumerStack(app, 'consumer', { 
  alb: producer.alb 
});

What did you expect to happen?

Using reference between Stacks/Accounts

What actually happened?

Error: Stack "B" cannot consume a cross reference from stack "A". Cross stack references are only supported for stacks deployed to the same environment or between nested stacks and their parent stack

Other

Please see reference in https://github.com/aws/aws-cdk-rfcs/issues/226 with @skinny85 :

@Cloudrage you’re right. It turns out there’s some logic missing from BaseLoadBalancer that is required for making these references work.

Do you mind creating us a bug for it in the main CDK repo? Thanks!

_Originally posted by @skinny85 in https://github.com/aws/aws-cdk-rfcs/issues/226#issuecomment-742178105_

---

This is 🐛 Bug Report

[Cloudrage]

@njlynch , not really integrated and native 😕 That’s why the Feature Request is very important in a multi-account strategy.

[skinny85]

@njlynch yes, you’re right, and that’s probably why we didn’t add it originally 😕. If the ARN cannot be derived from the name in a stable way, we can’t use these facilities for cross-environments references.

Sorry @Cloudrage . Looks like your feature request is still needed then.