# Elastic Network Interfaces (ENI)

![](/files/-MBbXKLOmAoBKmZODa-r)

![](/files/-MBbXd0WjZVChd2fc35l)

![](/files/-MBbXhDOl6WqfUEAzUV6)

When we launch two instances , each one having its own ENI.

![](/files/-MBbY3xRoQMk5GaIexE7)

We can attach & detach the ENI in between our EC2 instances.

**ENI - Extra Reading**

**Clarification on ENI**

> It's possible that for some of you, ENIs are not clear just yet.

That's okay, they are an advanced concept in AWS and one that can take time to master.

If you'd like to learn more on ENI, I found that many students were helped by reading this blog:  <https://aws.amazon.com/blogs/aws/new-elastic-network-interfaces-in-the-virtual-private-cloud/>[![](https://i.udemycdn.com/redactor/raw/2020-06-26_07-44-47-559eeb8a4230b6b5f0a8fea5e013edd8.png)](https://aws.amazon.com/blogs/aws/new-elastic-network-interfaces-in-the-virtual-private-cloud/)

I hope this will help you. If you still don't understand it, no worries, **this is not a blocker for the course**. Keep on going, and come back to this concept towards the end.

**Happy learning!**<br>


---

# 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://architectures.gitbook.io/project/aws-certified-solutions-architect-associate-certification-saa-c02/elastic-network-interfaces-eni.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.
