# API Scanning: Could not connect to SSL/TLS (v7)

To solve this, you can still be in the latest version on our product and keep your API Scanning working by changing the TLS version of the API's load balancer:

In AWS, in the API Agent's region, go to **EC2 > LoadBalancers > CloudStorageSecApiLB-{appId} > Listeners and Rules > Https: 443 Listener**

<figure><img src="/files/IDqU0qOBZqT9C3RAUAw6" alt=""><figcaption><p>EC2 > Load Balancers > CloudStorageSecAPILB</p></figcaption></figure>

Once there, go to **Actions > Edit Listener**

<figure><img src="/files/g5EmSCPkUXRp7gBrbkkt" alt=""><figcaption><p>EC2 > Load Balancers > CloudStorageSecAPILB > Https:443 Listener</p></figcaption></figure>

Scroll down to the **Secure listener settings** and change the Security Policy from TLS1.3 to the (recommended) one.

<figure><img src="/files/Ej263LaUyeW2x3spWVFD" alt=""><figcaption><p>EC2 > Load Balancers > CloudStorageSecAPILB > Https:443 Listener > Edit Listener</p></figcaption></figure>

Once this is done, Save the changes, wait a few minutes, and try your API/Token call again.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.cloudstoragesec.com/trouble-shooting/api-scanning-could-not-connect-to-ssl-tls-v7.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.