> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/modules/cinterion-r-els61-wireless-module/about-the-eseye-enabled-cinterion-els61-wireless-module.md).

# About the Eseye-enabled Cinterion® ELS61 Wireless Module

The Eseye-enabled Cinterion® ELS61 Wireless Module coupled with anAnyNet SIM provides simple, easy integration and secure cellular connection between your thing and your chosen cloud provider, from anywhere in the world. This enables you to remotely extract data from your thing for a variety of industrial and commercial applications, such as metering, monitoring, transportation, security, and so on.

<details>

<summary>What do I need?</summary>

* Thales Cinterion® ELS61 Wireless Module with seamless fallback to 2G/3G – enables a secure connection to AWS after the Eseye security and identity information is installed
* Single Eseye SIM with multi-IMSI capability – enables worldwide wireless connectivity

</details>

<details>

<summary>How connectivity is established with the cloud</summary>

The Eseye-enabled Cinterion® ELS61 Wireless Module uses the following:

* MQTT URL – the AWS Custom Endpoint used to establish a connection between a thing and AWS IoT Core, for example:

  a2efgh321joea3-ats.iot.eu-west-1.amazonaws.com
* Transport Layer Security (TLS) – for the IP connection, established using the certificates from the SIM

  For more information, see [Data security](https://docs.eseye.com/modules/cinterion-r-els61-wireless-module/data-security.md) .
* Publish and subscribe topics – preconfigured in the Eseye Telemetry Module application using AT commands
* AWSthingname – appended to the topics as a suffix to uniquely identify the thing in AWS IoT Core

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eseye.com/modules/cinterion-r-els61-wireless-module/about-the-eseye-enabled-cinterion-els61-wireless-module.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
