I also stumbled on that same post to start/stop AGW and helped me resolve some other issues, now using it for cost savings on my sandbox environment.
Wanted to still lower costs, and saw some conflicting info online about manual Vs Autoscale. However this post and this help article are worth reading.
Two options to lower costs, suited for a sandbox environment and maybe some production environments that have steady traffic, depending on SLAs:
- Manual, you can set to minimum of 1 instance over default 2.
- Autoscale, you can set min of 0 and max of 2.
As I understand it:
- Autoscale says that even with 0, 'High availability is ensured, even if set to zero.' (so no cold start with fresh/new connections)
- Autoscale will always reserve capacity units as long as AGW is started.
- Autoscale costs should be lower than manual for a low traffic site.
I will report back on how the monthly bill looks.
Of course, for a sandbox environment, maybe the best approach is to start/stop the gateway with a manual instance of 1, just when you need it. Currently doing that via the history in the GUI-powershell to do this, but I will likely forget! Should probably look into a local powershell script to spin up/down the environment that starts/ends with spinning up the AGW.
![SimonGIS_0-1688266700418.png SimonGIS_0-1688266700418.png](https://community.esri.com/t5/image/serverpage/image-id/74676i7C8358BA523A4937/image-size/medium?v=v2&px=400)
@ChristopherPawlyszyn @DavidHoy - let me know if you have learnt differently from this, will also report back on how autoscaling option helps with my azure costings in a month or so.