> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/references/cli/connect.md).

# sdm connect

```shell
NAME:
   sdm connect - open port to resource

USAGE:
   sdm connect [command options] name/ID [port]

OPTIONS:
   --all, -a       connect to all datasources. Port overrides must be enabled.
   --filter value  filter e.g. 'field:name tag:key=value ...'
   --filters-help  show valid filter strings and examples
```

### Resource Connection Limits

Depending on your operating system, you may be limited in the number of resources to which you can connect. This limit is known as the file descriptor limit. Standard limits are as follows:

* Linux-based: 1,024 resources
* MacOS: 256 resources
* Windows: 512 resources

Note the following potential scenarios that may occur if you reach the limit for your OS:

* If you run `sdm connect --all` and the number of resources you currently have access to is greater than the standard limit for your OS, the operation may fail.
* If you run `sdm connect --filter` and the number of results for that filter is greater than the standard limit for your OS, the operation may fail.

For more information on the use of filters in the CLI, see the [Filters](https://docs.strongdm.com/references/cli/filters.md) documentation.


---

# 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.strongdm.com/references/cli/connect.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.
