> 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-pls62-w-wireless-module/data-security.md).

# Data security

When you create a thing within AWS IoT Console, the associated SIM enables the Cinterion® PLS62‑W Wireless Module to register on a cellular network.

The Amazon Trust Service (ATS) uses the cellular network to securely deliver the following information to the Cinterion® PLS62‑W Wireless Module.

For identification purposes:

* The unique AWSthing name
* The Amazon Resource Name (ARN) that defines which AWS endpoint supports the thing

For security purposes:

* A set of X.509 certificates
* An encrypted private key – AWS and the

  Cinterion® PLS62‑W Wireless Module

  use key pairs for signing data

The certificates and private key are stored in a secure Java keystore. The end user cannot see or handle the security materials throughout their use.

When a thing is deleted in AWS, the data within the device keystore remains in the keystore. If you reuse the device with a new SIM and recreate it as a new thing within AWS, then any existing security information in the keystore is replaced by the new certificates and a new private key.

## AWS security compliance

The Cinterion® PLS62‑W Wireless Module meets AWS security requirements:

* Each connected device has a set of credentials to access the message broker or device shadow service
* Device credentials are stored safely in order to send data securely to the message broker
* All traffic to and from AWS IoT is encrypted over Transport Layer Security (TLS)

For more information, see the AWS documentation **Security** section, including: <https://docs.aws.amazon.com/iot/latest/developerguide/iot-security.html>.

## Processing updates

Updates to the certificates and keys are handled in the same way as all security data. This enables you to apply a managed certificate rotation policy, as well as automatically protecting the device against changes in rootCA providers.


---

# 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-pls62-w-wireless-module/data-security.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.
