Loading Profile...
Issue with starting EC2 image from Cloud Manager
In cloud manager, attempting to launch the EC2 instance I created yesterday comes back with this error message: Amazon EC2 reported a problem launching your instance: The security group 'hyperstratus' does not exist. I've looked at my account thru elasticfox and see that there is a security group with the name hyperstratus-cohesive-ft-trial-394053-1235081229. So it seems like there is an incomplete mapping from the instance info at cohesiveft and what's up on amazon. Also, in cloud manager, when the 'i' is hovered over in the "EC2 Images" section, it states that "this image appears to have been created outside Elastic Server On-Demand." It definitely was created from within the CohesiveFT system; I have started and stopped it with Elasticfox -- does that make a difference to how cloud manager views the instance?
Can you identify what's going on?
Can you identify what's going on?
I’m unsure
2
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has a solution in progress.
The best solution from the company
-
We've released the fix for the cloud manager that will hopefully solve your problems. Please note that if an image was created outside of Elastic Server, it can only be launched with the default security group. Images created using ES will use the security group that was automatically created for them by our service. We will be releasing more features for security group management and selection soon.
I’m happy
The company says
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Bernard, sorry you're having problems.
We're looking into the mapping error between the security groups. In fact both problems you mentioned are mapping errors. We found one of them yesterday and we hope to have a fix in place today. Thank you for helping to find the second one.
The use of ElasticFox - or, indeed, any external tool - should not make a difference in how the Cloud Manager perceives your systems.
Again, we're sorry about the issues and we hope to have things fixed in a short while.
Nicholas -
Inappropriate?Hi Bernard,
The issue is due to new functionality we launched that lets you pick the destination bucket for your images. We are working on a fix and should have it out soon. In the mean time, you should be able to use external tools like ElasticFox to manage your instances. We're sorry for the inconvenience.
thanks!
I’m sayin oops!
1 Comment Add a comment
This solves the problem
-
Yan,
Any news on this?
Thanks,
David -
Inappropriate?Hi guys, apologize for how long this is taking. We'll hopefully be able to release the fix tomorrow. I will update this thread as soon as I have more info for you. Thanks for your patience!
-
Inappropriate?We've released the fix for the cloud manager that will hopefully solve your problems. Please note that if an image was created outside of Elastic Server, it can only be launched with the default security group. Images created using ES will use the security group that was automatically created for them by our service. We will be releasing more features for security group management and selection soon.
I’m happy
The company says
this solves the problem
EMPLOYEE
