# 11. Kinesis Firehouse - Exercise3

![](/files/-MCp2VVZWsbioLb4tpMm)

Attach IAM role into our EC2 instance instead of copying them in the code :

\>>Remove file pattern from the above as it is used for Kinesis Data Stream shown below :

![](/files/-MCp3tzIehkinIb7hgRF)

Now start the kinesis agent :

![](/files/-MCp48thEPOmyQ6z8QvZ)

![](/files/-MCp4R_BIeEut0BnaAZS)

![](/files/-MCp4oGAbhoLYFiRkjf8)

**Troubleshooting Info for the Following Exercise**

In the next exercise, we'll set up a Kinesis data stream and use it.

In the video, we leave the kinesis.endpoint property empty in our agent.json configuration file. This works as long as your EC2 instance is in the same region as your Kinesis endpoint.

But if it isn't, you'll get 400 "Resource Not Found" exceptions when running this example, and the it can be confusing.

If you encounter this, simply specify your kinesis endpoint in the agent.json file, in the form:

"kinesis.endpoint": "kinesis.\<region>.amazonaws.com"

...subsituting your region (ie, eu-west-3,) for "\<region>".

So, just keep this info handy in case you run into that!


---

# 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-data-analytics-speciality-course-das-c01/section2-domain-1-collection/11.-kinesis-firehouse-exercise3.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.