> For the complete documentation index, see [llms.txt](https://awsnotes.dendron.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://awsnotes.dendron.so/migration-and-transfer/aws-datasync/topics/requirements.md).

# Requirements

{% hint style="info" %}
This page was generated from content adapted from the [AWS Developer Guide](https://github.com/awsdocs/aws-datasync-user-guide.git)
{% endhint %}

## Agent requirements

* **Note**\
  An exception to this recommendation is if you're running DataSync on an AWS Snowcone device. Use the default instance snc1.medium, which provides 2 CPU cores and 4 GiB of memory.

## Network requirements

* **Note**\
  Depending on your network, you might need to allow traffic on ports other than what's listed here for DataSync to connect with your self-managed storage.
* **Note**\
  The total number of network interfaces depends on your DataSync task locations. For example, transferring from an Amazon EFS location to FSx for Lustre requires four network interfaces. Meanwhile, transferring from an FSx for Windows File Server to an Amazon S3 bucket requires two network interfaces.


---

# 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 dynamically by asking a question.

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

```
GET https://awsnotes.dendron.so/migration-and-transfer/aws-datasync/topics/requirements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.