# Ignition cloud - Gateway Command-line Utility?

**URL:** <https://forum.inductiveautomation.com/t/ignition-cloud-gateway-command-line-utility/97500>\
**Category:** Ignition\
**Created:** [October 19, 2024, 8:31am UTC](https://forum.inductiveautomation.com/t/ignition-cloud-gateway-command-line-utility/97500 "2024-10-19T08:31:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![eichler-eng](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/eichler-eng/32/21259_2.png) [@eichler-eng](https://forum.inductiveautomation.com/u/eichler-eng)\
**Post date:** [October 19, 2024, 8:31am UTC](https://forum.inductiveautomation.com/t/ignition-cloud-gateway-command-line-utility/97500/1 "2024-10-19T08:31:50Z")

</div>

Hi All

I have mistakenly renamed the default user source and now I cannot log in. Ignition is hosted on AWS

Is there an option for Ignition Cloud to reset the admin password like gwcmd?

Cheers

---

<div class="post-metadata">

**Author:** ![Kevin.Collins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.collins/32/13497_2.png) [@Kevin.Collins](https://forum.inductiveautomation.com/u/Kevin.Collins)\
**Post date:** [October 19, 2024, 12:10pm UTC](https://forum.inductiveautomation.com/t/ignition-cloud-gateway-command-line-utility/97500/2 "2024-10-19T12:10:49Z")

</div>

You can SSH into the node and invoke gwcmd.sh like a normal Linux installation of Ignition. You can also use EC2 Instance Connect in many cases as well (where you might understandably not have SSH opened in your security group configuration).

---

<div class="post-metadata">

**Author:** ![eichler-eng](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/eichler-eng/32/21259_2.png) [@eichler-eng](https://forum.inductiveautomation.com/u/eichler-eng)\
**Post date:** [October 19, 2024, 7:46pm UTC](https://forum.inductiveautomation.com/t/ignition-cloud-gateway-command-line-utility/97500/3 "2024-10-19T19:46:21Z")

</div>

Thanks for the information. We ended up restoring the EC2 instance. Luckily this happened just after spinning up.
