> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/overview/aws-services/elastic-file-system-efs/mount-an-efs-in-an-ec2-instance.md).

# Mount an EFS in an EC2 instance

Mount an EFS in an EC2 instance using a script

## Mounting an EFS in an EC2 instance

If you want to connect an EFS to a Native Docker Service, for example, you can mount it in an EC2 instance.

```bash
btoa(`#!/bin/bash
sudo su
echo "confirm it is running" >> /tmp/startup_log
apt-get install -y nfs-common
cd /
mkdir efs
mount -t nfs4 -o 
nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,nore
svport fs-121345b8.efs.us-west-2.amazonaws.com:/ efs
echo "fs-121345b8.efs.us-west-2.amazonaws.com:/ /efs nfs4 
defaults,_netdev 0 0" >> /etc/fstab`);
```

1. Create a `bash` script, as in the example above, and replace `nfs4` with your EFS endpoint. You can run the script below on an existing EC2 instance or run an EC2 user data script to configure the instance at first launch (bootstrapping).
2. In the DuploCloud Portal, [edit the DuploCloud Service](/docs/automation-platform/overview/aws-services/containers/eks-containers-and-services.md#services).
3. On the **Edit Service** page, click **Next**. The **Advanced Options** page displays.
4. On the **Advanced Options** page, in the **Volumes** field, enter the configuration YAML to mount the EFS endpoint as a volume.


---

# 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.duplocloud.com/docs/automation-platform/overview/aws-services/elastic-file-system-efs/mount-an-efs-in-an-ec2-instance.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.