Viewing existing EC2 instances in Sclar

[rajnemani]

Hi,

I am new to Scalr and just configured a new installation with AWS.  I can see all the information such as EC2 EIPs, Security groups, S3 buckets etc but cannot see the list of existing EC2 instances under AWS menu.  I even see the DB isntances and other RDS related stuff under RDS menu. I have not created any farms or roles yet.  I am just trying to see if I can see the listing of existing EC2 instances.  Is it possilble or am I missing something?

Also, does Scalr show and allow editing of the tag informmation that is associated with various AWS resources?

Thank you for any help in advance.

Thanks

Raj

[Daniele Testa]

Hi!

Welcome to Scalr :)

Existing EC2 instances needs to be imported to Scalr before they can be managed through Scalr.

https://scalr-wiki.atlassian.net/wiki/x/1w8b

Note that this only imports the server as a "template" which is called images/roles in Scalr.

You can then launch new instances based on on those Roles.

Regards,

Daniele

[rajnemani .]

Hi Daniele,

Thank you for your answer.  I aprreciate it.  So even after importing the server, I cannot do anything with it since it is a template such as managing tags, stopping, restarting etc.  Also, how can I manage the tags on the existing other AWS resources such as ELBs, EBS volumes etc, once I see them in Scalr.  As I am new to Scalr, I have a lot fo questions about the problem that Scalr is trying to solve.  There is a lot of good documentaion on how to do things but I could not find anything that desscribes the overall picture for Solr and the typical use cases for it.  Any pointers towards this is appreciated.

Thanks again for your help.

Raj

--
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 scalr-discus...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Daniele Testa]

Hi!

Yes, it is correct. Scalr will not touch existing instances. Scalr will only control instances that has been launched from Scalr (thus not existing ones).

Same applies to most other things, like EBS volumes.

The main purpose of Scalr is to get a single control panel (and a unified workflow) across different cloud providers. If you build your infrastructure through Scalr, it is easy to switch between providers.

Scalr also helps you to adapt correct cloud practices. When building application in the cloud, you should always make the "crash-safe". Any instance can die at any time and your application must be built to survive this. That's the main purpose of Roles in Scalr.

As they work as templates for you instances, you can easily launch new identical instances if one would die. Same if you need to scale up or down.

I hope this answers your questions.

Regards,

Daniele