When creating cellular IoT devices, developers must decide the type of cellular embedded solution to use. The typical options are to use an embedded cellular chipset, an embedded module, or an embedded device board. All embedded applications that incorporate Cellular start with a chip that provides the RF radio in order to be able to connect to a cellular network. While it is certainly possible for an embedded designer to integrate a cellular chip into an embedded design, starting with a chip requires a larger investment of engineering time and effort, as well as the cost of certification of the device. Rather than using an embedded chipset, an embedded engineer can use a module, which is well suited for lower volumes due to the lower complexity and overall cost of the embedded solution. Modules are often commercially available and often the network certification has already been performed by the module manufacturer. AE-CLOUD2 uses a pre-configured cellular module to help speed up the development of the kit and to get the kit in the hands of developers sooner. While selecting a cellular module for an embedded design can speed up development, issues can still arise when integrating the module into the embedded application. For example, integrating the cellular module can often require negotiating the technical troubleshooting between the module manufacturer, cellular chip company, mobile carrier supplying the data plan, and the IoT Cloud to which the embedded device is connecting. To alleviate these issues for developers, AE-CLOUD2 provides a full-functional reference design.