> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/setting-up/cloud/creating-an-account-in-astera-cloud-portal.md).
# Creating an Account in Astera Cloud Portal
The Astera Cloud Portal provides secure access for managing your data integration projects in the cloud. In this document, we will walk through the steps to create an account on the Cloud Portal.
1. Go to [cloudastera.com](https://cloudastera.com/).
2. Click *Create an account*.
3. Astera offers two methods to create your account:
* *Sign Up with Microsoft* – Useful for users who have an active Microsoft account.
* *Sign Up with Email* – Suitable for any other email domains.
Select your preferred method and go through the MFA steps.
4. Once you have signed up, Step 2: *Profile* will appear. Enter your *First Name* and *Last Name* here.
5. Click *Start Trial,* you will be directed to the portal home page
You can now launch your designer by clicking *Launch Designer* to start designing data integration flows in Astera.
---
# 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://documentation.astera.com/setting-up/cloud/creating-an-account-in-astera-cloud-portal.md?ask=&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.
