# Catch 22 for complete automation of a gateway setup **URL:** \ **Category:** Ignition\ **Tags:** ignition83\ **Created:** [March 7, 2026, 1:18am UTC](https://forum.inductiveautomation.com/t/catch-22-for-complete-automation-of-a-gateway-setup/114373 "2026-03-07T01:18:02Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\ **Post date:** [March 7, 2026, 4:55am UTC](https://forum.inductiveautomation.com/t/catch-22-for-complete-automation-of-a-gateway-setup/114373/2 "2026-03-07T04:55:44Z")
I haven’t migrated my 8.1 automated deployment yet, but I’m not anticipating any showstoppers. > [@justin3](#): > > use a gateway back up I reckon I’ll add myself to the list, and echo to **start** with a gateway backup. Configure a single gateway in the UI, then use that gwbk for all future gateways. The gwbk can be restored via script (immediately following your automated install), and would contain the base config for your client - things **common** to every gateway. With any luck, that could include MQTT configuration… Personally, I’m not a believer in Docker for bare metal Edge installs. To each their own… Regarding the API key: > [@Is there way to create/generate api token?](https://forum.inductiveautomation.com/t/is-there-way-to-create-generate-api-token/109761/5): > > If you want to 'preconfigure' a gateway with an API key, you can store one in the external resource collection, as mentioned in the post @Sfenwick linked: Note that this same principle can be applied a layer higher. If you want to preconfigure a gateway connection - you can do the exact same thing (move a configured resource to the external collection) but with your configured DB connection. Regarding any other **specific** hurdles you encounter, inquire here. --- _[View the full topic](https://forum.inductiveautomation.com/t/catch-22-for-complete-automation-of-a-gateway-setup/114373)._