Hi James,

Can you test with scalr.instances_connection_policy = local.  
scalr.aws.instances_connection_policy 
= local is not sufficient for a VPN connected VPC as described in our Using 
VPC 
<https://scalr-wiki.atlassian.net/wiki/display/docs/Using+VPC+-+Internal+Scalr+Deployment>
 
documentation.  Remember to reconfigure after changing scalr-server.rb.  If 
some Farm Roles in the test farm are launching correctly but others are 
throwing this error, can you test removing the failing farm roles, save the 
farm, and then re-add the farm roles while selecting the correct subnet 
when you re-add the Farm Role? If the behavior persists, is the experience 
different if you create a new Farm from scratch (do not clone) using the 
same Farm Role and VPC subnet?

Many thanks,
Wm. Marc O'Brien
Scalr Technical Support



On Tuesday, November 22, 2016 at 3:17:39 PM UTC-7, James Smith wrote:
>
> Greetings, all
>
> I'm experiencing an issue with Community version 5.11.22. My AWS account 
> has a single VPC with 4 private subnets, one subnet per AZ, and no VPC 
> router (our AWS VPCs are connected to the corporate network via 
> site-to-site VPN and we're prohibited by corporate policy from attaching a 
> VPC router). aws.instances_connection_policy is set to local.
>
> If I try to launch a farm with multiple servers, some of the systems are 
> created but many are stuck in "Pending Launch" status with the following 
> error:
> Unable to launch instance:AWS Error. Request DescribeSubnets failed. The 
> subnet ID 'subnet-xxxxxxxx' does not exist
>
> I've tried setting the governance policy to only allow use of one of the 
> subnets, I've tried adding multiple subnets to the farm roles in my farm. 
> Is this not a supported configuration, or is there a configuration option 
> I'm missing?
>
> Any guidance would be appreciated.
>

-- 
You received this message because you are subscribed to the Google Groups 
"scalr-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to