Associating ELB with ASG failed in the Tokyo region (ap-northeast-1)

[snaga]

I just found that "Create New Auto Scaling Group" does not show available ELBs in "Load Balancers (cannot be added or removed later): " section when attempting it in the Tokyo region (ap-northeast-1).

The following step would reproduce it.

1. Create an "Application".
2. Create a "Security Group" in the Tokyo region.
3. Create an "ELB" in the Tokyo region.
4. Create an "ASG" with associating with an ELB in the Tokyo region.
5. Any ELB not found in "Create New Auto Scaling Group" panel.

Is this a bug? or a kind of limitations because of AWS?

I could do this correctly when attempting in the Verginia region (us-east-1).

[joesondow]

My first guess is that your ELB and your ASG might be in different VPC contexts. Check your ELB to see if it's in a VPC, and if so, what Asgard-style "VPC Purpose" is it in? Then go back to the Create Auto Scaling Group screen and choose the same VPC purpose as the ELB, and then try to type the ELB name into the ELB input.

If that still doesn't work, then there may be a bug.

[snaga]

Thanks for the response.

Our ELB is not in a VPC so far (we will use it though), but I still can't find any ELB under this environment.

However, when I tried another testing environment to build a cluster in the Tokyo region, it succeeded.

I'm not sure why, but I'm moving on the next item on my check-list to use Asgard now. So, this issue can be closed.

I wish Asgard would have some capability to produce "verbose debug messages" to determine such issues.

[jeparkinson]

We are having a similar issue. When attempting to create an ASG, the field for 'Load Balancers (cannot be added or removed later):' is blank and not editable. Everything else seems to be sync'd up correctly with AWS.

Anyone have any thoughts/hints/tips/suggestions?