Unable to start/stop EC2 Instances on AWS Dashboard
Within an AWS Dashboard console session -- clicking the 'Start' or 'Stop' buttons from either the right-click context menu option or the top menu bar (as shown in screenshot below) will NOT do anything for any AWS EC2 instance listed within the dashboard.
That is, if the EC2 Instance was in the 'Stopped' state, after clicking the 'Start' button, the instance will remain stopped, and vice-versa, if the EC2 Instance was in the 'Running' state, then after clicking on the 'Stop' button the instance will remain running.
Screenshot attachment:
My Environment Details:
I am currently running the 'free' version of the 'Remote Desktop Manager' app on Windows 10 Pro (OS Build 19043.1165).
The RDP Manager app is on the latest version of 2021.1.41.0 64-Bit (See below for full screenshot of the version pane):
FYI - in case this helps, and there are NO add-ons loaded.
AWS_Dashboard_Issue_on_RDP_Manager_Img_1630327595.png
All Comments (5)
Hello,
There does seem do be an issue with the buttons not updating their states after an action is performed, so we'll look into that.
That being said, the start/stop actions themselves are working properly on our end. If you start an instance, then wait about a minute and refresh the console, is the instance running ?
Regards
Jonathan Del Signore
Hi Jonathan,
I will test that again but this time I'll make sure that I wait at least 1 full minute before checking for the status of the instances. Though I think I had waited that long before, I am not exactly sure of it so I won't hurt testing it again. I will let you know what is the result on my end, thanks!
I tested today and waiting 2 minutes just to be on the safe side and the instance never got started - and just to be 100% sure that it is not just the view and/or buttons not updating, I then went on to the AWS dashboard on my web browser to see the status of the EC2 instance in question and confirmed that the instance in deed did not start.
I am sure that there may be some difference between your environment and mine since the behaviors are different - being that for me, the buttons will just do nothing.
Let me know if there is any additional details I can provide from my end should you try to reproduce the behavior I am getting.
Thanks,
Gabe
Hi Gabriel,
Would you mind going in Help -> Profiler, in the Debug Only tab, and setting the Debug level to 1. Then with the profiler still opened, try to start an EC2 instance. This may show some info about the error you're getting.
Also, if you go in Help -> Application Logs, do you see anything related to the AWS console ?
Regards
Jonathan Del Signore
Thanks for the helpful article!