> 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/anynet-sim/device-integration.md).

# Device integration

The AnyNet 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.

### Before you begin

Complete the following setup:

1. [Create an AWS account](https://aws.amazon.com), or log in to an existing account.

   For setup instructions, see the [AWS account activation guide](https://aws.amazon.com/premiumsupport/knowledge-center/create-and-activate-aws-account/).
2. In **AWS IoT Core**, [create a thing with AnyNetThingType](/anynet-sim/device-integration/creating-a-thing-with-anynetthingtype.md). Use the AnyNet Secure SIM number as its identifier.
3. Install the matching AnyNet Secure SIM in your IoT device.
4. Power on the modem.
5. Connect a GPS antenna.
6. Confirm the modem can acquire a network signal.

## Connecting securely to AWS

AWS provisions the AnyNet Secure SIM over a cellular network. During provisioning, the AnyNet Secure service transfers the following identity and security information to your AnyNet Secure SIM:

* The unique AWS thing name
* The Amazon Resource Name (ARN) that defines which AWS endpoint supports the thing
* A set of X.509 certificates
* An encrypted private key – AWS and the modem use key pairs for signing data

You must extract this information into the modem to enable the secure data connection from your device to the AWS IoT Core platform.

For information about monitoring provisioning progress, see [Provisioning the AnyNet Secure SIM](/anynet-sim/device-integration/provisioning-the-anynet-secure-sim.md).

For information about which files to extract from the AnyNet Secure SIM, see [About AnyNet Secure SIM files](/anynet-sim/device-integration/about-anynet-secure-sim-files.md).

For information about how to extract the files, see [AT+CRSM – reading files from the SIM](/anynet-sim/device-integration/at+crsm-reading-files-from-the-sim.md).


---

# 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/anynet-sim/device-integration.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.
