> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-analyzer/aws-marketplace/subscription.md).

# Subscription

## Subscribe To IZ Suite

The AWS Marketplace is an online store that makes it easy for customers to start using IZ Suite and its services that run on the Amazon Web Services (AWS) cloud.

IZ Analyzer suite consists of Mule and API components for implementing enterprise grade Source Code Analysis along with a cloud offering of IZ Analyzer

### Marketplace Listing

1. Navigate to **`AWS Marketplace`** - <https://aws.amazon.com/marketplace>
2. Search for **`IZ Analyzer`** <br>

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FoqYxoVoj5AcBH9qfr1dX%2Faws-search.png?alt=media&amp;token=067bb9f9-a855-486d-ba47-eb7fc6db1e1e" alt=""><figcaption></figcaption></figure>

### How To Subscribe

1. Click on `Continue to Subscribe` <br>

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F4A02MeOfJQIOdZ6MvaA1%2Faws-subscribe.png?alt=media&amp;token=db539927-c8af-45e9-be87-59b2a257bd58" alt=""><figcaption></figcaption></figure>
2. Click on `Continue to Configure` <br>

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F7xWj8uJThtCYOzcIfhj3%2Faws-configure.png?alt=media&amp;token=559e03cf-70ef-435b-88ca-1c0fe61d0c0d" alt=""><figcaption></figcaption></figure>
3. Select the software version, Fulfillment option, region and click on `Continue to Launch` <br>

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F6kOLdXLB2DBxxEcaix5c%2Faws-launch.png?alt=media&amp;token=9e52b4f6-697c-49ce-bcb2-af5910763125" alt=""><figcaption></figcaption></figure>
4. Select the instance type, VPC Setting, Subnet Setting, Security Group and click on `Launch` <br>

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FkXqZukvaLBZXukMWzami%2Faws-instance-type.png?alt=media&amp;token=cf773a67-6578-4c31-872d-9f15a0596f9f" alt=""><figcaption></figcaption></figure>
5. A new EC2 instance will be created in the selected region

### Create a Database

{% hint style="info" %}

* This step is required if the instance is being configuring for the first time.
* This step can be ignored if the marketplace product instance is being updated to a new version.
  {% endhint %}

1. Login to AWS management console. <https://aws.amazon.com/console/>
2. Navigate to **`Services`** -> **`RDS`** and click on **`Create Database`**
3. Select **`PostgreSQL`** engine type, username, password, storage, backup options and click on `Create Database` <br>

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FiM3k3epYGcgRTff8xmVH%2Frds.png?alt=media&amp;token=0ead0329-a875-49ce-a05d-e4a7218aa975" alt=""><figcaption></figcaption></figure>
4. Click on the created RDS database instance and copy the endpoint <br>

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FHY3RvaIyvpj2zOoKHAAn%2Ffalcon-suite-rds.png?alt=media&amp;token=05284897-5a8a-4685-8ca8-81ab45e07d67" alt=""><figcaption></figcaption></figure>
5. Click on **`Actions`** -> **`Setup EC2 Connection`**. Select the EC2 Instance created earlier and click on `Continue` to setup the connection between EC2 and RDS.\
   &#x20;

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F1pLdnQsEkl4QxQyRtBxI%2Fsetup-ec2-connection.png?alt=media&amp;token=028e3862-a135-487b-bf32-78c774ce4d44" alt=""><figcaption></figcaption></figure>

### Configure Database details and start the server

1. Login to the created EC2 instance using the downloaded pem file. E.g.: ssh -i \<downloaded.pem> ubuntu@\<publicip>
2. Navigate to **`/home/ubuntu/sonarqube.x.x.x/conf`**
3. Open sonar.properties file and update the database connection details
   1. **`sonar.jdbc.url`** - Update the RDS host, port and database name
   2. **`sonar.jdbc.username`** - RDS username
   3. **`sonar.jdbc.password`** - RDS password
4. Navigate to /home/ubuntu/sonarqube.x.x.x/bin/linux-x86-64 and start the server
   1. ./sonar.sh start
5. This will run the server in background
6. Navigate to **`http://<publicip>:9000`** in the browser


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-analyzer/aws-marketplace/subscription.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.
