Description of problem: RHS Customers, who are running their storage environement in AWS environment, they should be able to manage their RHS nodes, by RHSC running as one of the AWS instance in the same AWS private cloud. For instance, if the customer has taken a AWS private cloud, in which he has 5 RHS nodes running ( N1 to N5 ), he should be able to run RHSC on another node 'R' (running on RHEL), in the same private cloud. Version-Release number of selected component (if applicable): both 2.x and 3.x It should be tested in 3.x with higher priority than 2.x How reproducible: This has to be tested to confirm or find issues Steps to Reproduce: 1. 2. 3. Actual results: Expected results: This is going to be a pure testing effort, unless otherwise issues are seen. This feature can be supported by confirming that RHSC on AWS instance is able to manage RHS nodes running on other AWS instances in the same private cloud space. Additional info: We suspect, there might be issue seen, when we bootstrap RHS nodes from RHSC, while both of them are running in AWS environment.
Removing from Everglads, as couple of things to be changed - Adding nodes using public key - Firewall setup in AWS (to be checked)
Closing duplicate of similar bug *** This bug has been marked as a duplicate of bug 850486 ***