> For the complete documentation index, see [llms.txt](https://docs.hava.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hava.io/importing/aws/getting-started-with-aws.md).

# Getting Started with AWS

When you log into Hava for the first time, you will be presented with the opportunity to import some demo environments and also jump right into connecting to your own AWS accounts.

![Getting Started with AWS](/files/pSYyfVAQDl2E2LSZeixU)

The first step in creating accurate AWS infrastructure diagrams with Hava is to connect Hava to your AWS account.

We **strongly advise** creating a **Cross Account Role** to allow access to your AWS environment. Hava is built on AWS and this method is considered AWS best practice.

You may also create a new IAM user with **Read Only Permissions**. Either way, there can be no doubt from an infrastructure integrity and security perspective that Hava cannot change or update anything in your environment and is limited to reading the data it needs to visualise your AWS environment.

{% embed url="<https://youtu.be/mbXJyKpC9jU>" %}

You may also create a Minimum Access Read Only IAM User with customisable permissions if you wish to exclude access to any components of your AWS environment.


---

# 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://docs.hava.io/importing/aws/getting-started-with-aws.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.