This message was deleted.

Hi @tall-scientist-89115 Drop the ARN and just add the name of the LoadBalancer to the import...

No luck there, tried the DNS name (the-name-122293299.us-west-2.elb.amazonaws.com) and the name name (the-name)

So the name of the ELB in the import statement needs to be the name of the ELB in the resource declaration

Right on, yeah it is, here is the full statement for reference (this yields not found):

const main = new aws.elb.LoadBalancer("redjade-qa", {
    name: "redjade-qa",
    availabilityZones: ["us-west-2c", "us-west-2a"],
    listeners: [{
        instancePort: 80,
        instanceProtocol: "http",
        lbPort: 80,
        lbProtocol: "http",
    }, {
      instancePort: 443,
      instanceProtocol: "https",
      lbPort: 443,
      lbProtocol: "https"
    }],
}, { import: "redjade-qa" });

The actual resource copied out of the UI:

Name
redjade-qa
ARN
arn:aws:elasticloadbalancing:us-west-2:115325214166:loadbalancer/app/redjade-qa/ac143d25c93cb8fa
DNS name
<http://redjade-qa-122293299.us-west-2.elb.amazonaws.com|redjade-qa-122293299.us-west-2.elb.amazonaws.com>

so you are all good now?

Nah sadly, I was just stating that the name does match the existing resource