# Enabled modules in container yaml **URL:** \ **Category:** Ignition 8.3 Early Access\ **Tags:** vision, perspective\ **Created:** [August 14, 2025, 9:34am UTC](https://forum.inductiveautomation.com/t/enabled-modules-in-container-yaml/109762 "2025-08-14T09:34:33Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![boandersen](https://avatars.discourse-cdn.com/v4/letter/b/13edae/32.png) [@boandersen](https://forum.inductiveautomation.com/u/boandersen)\ **Post date:** [August 14, 2025, 9:34am UTC](https://forum.inductiveautomation.com/t/enabled-modules-in-container-yaml/109762/1 "2025-08-14T09:34:33Z")
I am a little stuck on how to activate the event streams module in 8.3 running in kubernetes. I have this line in my yaml config: - name: GATEWAY\_MODULES\_ENABLED value: "allen-bradley-drivers,vision,perspective,eventstream,mssql,postgresql,bacnet-driver,dnp3-driver,logix-driver,modbus-driver-v2,omron-driver,opc-ua,siemens-drivers,udp-tcp-drivers,web-developer" ( I also want to enable postgresql and mssql and have same problem) - I do not know what name the module has - I tried using the data/api/v1/resources/names/com.inductiveautomation.opcua/device API from python to list disabled modules (YES; API!!!) , and I get a list, but it seems to not correspond to the expected name in GATEWAY\_MODULES\_ENABLED com.inductiveautomation.sfc SFC com.inductiveautomation.sqlbridge SQL Bridge com.inductiveautomation.jdbc.mariadb MariaDB JDBC Driver com.inductiveautomation. **eventstream** Event Streams com.inductiveautomation.jdbc. **postgresql** PostgreSQL JDBC Driver com.inductiveautomation.sms-notification SMS Notification com.inductiveautomation.opcua.drivers.mitsubishi Mitsubishi Driver com.inductiveautomation.opcua.drivers.micro800 Micro800 Driver com.inductiveautomation.opcua.drivers.siemens-symbolic Siemens S7 Symbolic Driver com.inductiveautomation.reporting Reporting com.inductiveautomation.phone-notification Voice Notification com.inductiveautomation.connectors.kafka Kafka Connector com.inductiveautomation.symbol-factory Symbol Factory com.inductiveautomation.alarm-notification Alarm Notification com.inductiveautomation.jdbc. **mssql** MSSQL JDBC Driver com.inductiveautomation.opcua.drivers.iec61850 IEC 61850 Driver com.inductiveautomation.eam Enterprise Administration com.inductiveautomation.historian Historian com.inductiveautomation.historian.sql SQL Historian com.inductiveautomation.opcua.drivers.dnp3v2 DNP3 Driver I would of course like to know the names, so I can get unstuck, but I’d also love to know where I can find this myself I cannot enable the modules from the UI ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [August 14, 2025, 3:44pm UTC](https://forum.inductiveautomation.com/t/enabled-modules-in-container-yaml/109762/2 "2025-08-14T15:44:18Z")
> **[Docker Image | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.3/platform/docker-image#module-identifiers-table)** > > The Ignition Platform offers a container image for use on popular container runtimes such as Docker. You can find the image on Docker Hub at https://hub.docker.com/r/inductiveautomation/ignition. Our official image is a Linux container, based on... The reverse DNS name identifiers "should" be used (as far as I know). @kcollins can probably advise more 😃 ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [August 14, 2025, 4:17pm UTC](https://forum.inductiveautomation.com/t/enabled-modules-in-container-yaml/109762/3 "2025-08-14T16:17:02Z")
> [@paul-griffith](#): > > The reverse DNS name identifiers "should" be used (as far as I know). These are typically what are used for the fully-qualified module ID. If you want to extract the module ID for a given module, you can run the following (on Linux/macOS/WSL2 with `unzip` and `xmlstarlet` CLI tools installed): ```bash unzip -c -q /path/to/module.modl module.xml | \ xmlstarlet sel -t -v "/modules/module/id" ; echo ``` For example, this shows how to retrieve the module ID from Cirrus Link’s MQTT Transmission Module: ![SCR-20250814-kejh-3](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/f/dfb8cd280092ce588cc15f81416472e0bfbe6303.png) Since Event Streams (and the module-based JDBC drivers) is new with 8.3.0, you must use its fully qualified module ID, `com.inductiveautomation.eventstream` (as shown in the docs that @paul-griffith linked 🙏 ). Also of note is that these identifiers can also be used with the new `ACCEPT_MODULE_LICENSES` and `ACCEPT_MODULE_CERTS` [environment variables](https://www.docs.inductiveautomation.com/docs/8.3/appendix/reference-pages/platform-environment-variables#environment-variables) to apply automated acceptance of the applicable licenses and certificates for third-party modules. No more hackery needed to get a fresh out-of-box Ignition Gateway with third-party modules in a ready and `Running` state. ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [August 14, 2025, 4:19pm UTC](https://forum.inductiveautomation.com/t/enabled-modules-in-container-yaml/109762/4 "2025-08-14T16:19:50Z")
I should also mention for others who might be otherwise unaware that with Ignition 8.3, installation of third-party modules within our container image now flow to an area within the `data` volume. Module enabled/disable status is also persisted there. You no longer need to bake in third-party modules into a derived image to make sure that they’re still there on container lifecycle events. If you are driving `GATEWAY_MODULES_ENABLED`, you’ll notice that you cannot enable/disable modules through the web UI. This is by-design, as declaring this variable implies locking in the set of enabled modules. Finally, with the container image, built-in modules (i.e. ones in the image under `/usr/local/bin/ignition/user-lib/modules`) cannot be uninstalled through the web UI. You might notice that you _could_ do this with the Ignition 8.1.x container image, but the modules would magically re-appear if you recreated the container. ---
**Author:** ![drewdin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drewdin/32/3363_2.png) [@drewdin](https://forum.inductiveautomation.com/u/drewdin)\ **Post date:** [December 5, 2025, 5:22pm UTC](https://forum.inductiveautomation.com/t/enabled-modules-in-container-yaml/109762/5 "2025-12-05T17:22:37Z")
I am spinning up an 8.3.2 version of maker using `GATEWAY_MODULES_ENABLED` But I still get modules that are not listed and marked as error “Not eligible for use with Ignition Maker Edition“ Any idea why or is this a bug? Modules showing up that I don’t have in enabled: - Kafka Connector - Omron Driver - Logix Driver - Siemens Drivers - Mitsubishi Driver - Micro800 Driver - Allen-Bradley Driver What I have Specified in my Gateway modules enabled: - com.inductiveautomation.connectors.mongodb - com.inductiveautomation.jdbc.postgresql - com.inductiveautomation.jdbc.mariadb - com.inductiveautomation.jdbc.mssql - com.inductiveautomation.eventstream - com.inductiveautomation.alarm-notification - com.inductiveautomation.opcua - com.inductiveautomation.perspective - com.inductiveautomation.reporting - com.inductiveautomation.sfc - com.inductiveautomation.sqlbridge - com.inductiveautomation.historian - com.inductiveautomation.historian.sql - com.inductiveautomation.webdev - com.inductiveautomation.opcua.drivers.tcpudp - com.inductiveautomation.opcua.drivers.modbus ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [December 5, 2025, 9:02pm UTC](https://forum.inductiveautomation.com/t/enabled-modules-in-container-yaml/109762/6 "2025-12-05T21:02:10Z")
This behavior surprised me, but it looks like we do have a ticket in our system for this, IGN-14320. Thankfully, it looks like if you just omit `GATEWAY_MODULES_ENABLED` env var, things work correctly. With 8.3.x, you don't need this variable to persist module enable/disable state. ---
**Author:** ![drewdin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drewdin/32/3363_2.png) [@drewdin](https://forum.inductiveautomation.com/u/drewdin)\ **Post date:** [December 5, 2025, 9:28pm UTC](https://forum.inductiveautomation.com/t/enabled-modules-in-container-yaml/109762/7 "2025-12-05T21:28:07Z")
Thanks! I had that in there from 8.1, i just removed it and it works fine.