Not showing instances in Sao Paulo datacenter

[lfcipriani]

After installation, claws is not showing instances present in Sao Paulo datacenter. Not tested in other regions to check if it's only there.

[wbailey]

That would be great if you could test it against another region. Admittedly I only have instances in the US east region so any help debugging would be appreciated. I am assuming your security group allows ssh access to that region already from your origin?

[lfcipriani]

Yes, it's all configured correctly and I can ssh my server without any problem. I will do more tests later and let you know my findings.

Usually, the US east is default for the ec2 clients, when we use for other region we need to pass a parameter telling what region we want.

Would be great also to add multiple account support.

[wbailey]

Thanks for the help in advance. Multiple account support should be on the roadmap so I am going to a separate issue for it.

[iconara]

The problem is on line 10 of lib/claws/collection/ec2.rb. The default region is us-east-1. Change it to AWS::EC2.new.regions['eu-west-1'] it will work with eu-west-1 instead. That should probably be configurable in the claws.yml.

[wbailey]

Thank Theo. It wasn't readily obvious to me in the aws-sdk documentation that this was the default or how to change it. Let me know if you want to take a shot at forking and fixing it.

[iconara]

I realized there's an even simpler way: just add ec2_endpoint to your ~/.claws.yml, like this

aws: 
  access_key_id: XYZ
  secret_access_key: abc
  ec2_endpoint: ec2.eu-west-1.amazonaws.com

[wbailey]

I have figured out a way to do it so that you can specify and array of regions in the claws.yml file so it will choose instances from those regions. If it is not specified it will get all instances from all regions. Patch coming soon.

[lfcipriani]

Thanks folks