* [AWS AMI](self-hosting/aws-ami.md)

Only workspace admins and developers can view the **Data Sources** page and create new data sources.

For each data source, workspace admins and the creator can change its **Access Control**. Go to Openblocks homepage > **Data Sources**, and click `···` > **Access Control**.

For more information on permissions for data sources, see [Data sources](../workspace-management/permissions-for-resources.md#data-sources).

Recommended system spec: 1-core CPU and 2 GB RAM.

Openblocks provides an Amazon Machine Image (AMI) for your self-hosting on [Amazon Web Services (AWS)](https://aws.amazon.com/).

1. Sign in to [Amazon Web Services (AWS)](https://aws.amazon.com/) or [Create and activate an AWS account](https://aws.amazon.com/premiumsupport/knowledge-center/create-and-activate-aws-account/?nc1=h\_ls) first.

2. Follow the steps in [Create a key pair using Amazon EC2](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/create-key-pairs.html#having-ec2-create-your-key-pair) to generate an SSH key pair.

<figure><img src="../.gitbook/assets/aws-ami-1.png" alt=""><figcaption></figcaption></figure>

3. Follow the steps in [Create a security group](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/working-with-security-groups.html#creating-security-group) to create a new AWS security group. While creating, add an inbound rule that sets port **3000** to be accessible from **anywhere**, as shown below.

<figure><img src="../.gitbook/assets/aws-ami-2.png" alt=""><figcaption></figcaption></figure>

4. Click **Images** -> **AMI Catalog** on the left sidebar. Type in **Openblocks** to search in **AWS Marketplace AMIs**. **Select** the Openblocks image from results, then click the **Launch Instance with AMI** button to proceed.

<figure><img src="../.gitbook/assets/aws-ami-3.png" alt=""><figcaption></figcaption></figure>

5. Configure the following settings:

1. Choose your desired **Instance type**. We'd recommend a system spec with 1 core CPU and 2 GB RAM or the above.

2. Select the **key pair** created in step 2.

3. **Enable** auto-assigning public IP.

4. Select the **security group** created in step 3.

<figure><img src="../.gitbook/assets/aws-ami-4.png" alt=""><figcaption></figcaption></figure>

6. You can check the settings again and click the **Lauch instance** button to proceed.

<figure><img src="../.gitbook/assets/aws-ami-5.png" alt=""><figcaption></figcaption></figure>

It usually takes a few minutes to start the instance.

<figure><img src="../.gitbook/assets/aws-ami-6.png" alt=""><figcaption></figcaption></figure>

After deployment, you can view the instance details on the **Instances** page and get the **public IPv4 address**.

<figure><img src="../.gitbook/assets/aws-ami-7.png" alt=""><figcaption></figcaption></figure>

Your new Openblocks instance should be available at **http://public\_ipv4\_address:3000**.&#x20;

In the welcome page, click **Sign up** to get started. Openblocks will automatically create a workspace for you. Then you can start building your apps and invite members to your workspace.

<figure><img src="../.gitbook/assets/aws-ami-8.png" alt=""><figcaption></figcaption></figure>

You can connect to your instance to update the image or customize deployment configurations.

&#x20;Click **Connect** on the **Instances** page. AWS provides four connection options.

<figure><img src="../.gitbook/assets/aws-ami-9.png" alt=""><figcaption></figcaption></figure>

<figure><img src="../.gitbook/assets/aws-ami-10.png" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}

For detailed information, see [Connect to your Linux instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstances.html).

{% endhint %}

For example, you can connect to your instance using an SSH client. Locate your private key file and get your public IPv4 DNS. Then run the following command:

ssh -i "your_private_key.pem" ubuntu@your_public_IPv4_DNS

<figure><img src="../.gitbook/assets/aws-ami-11.png" alt=""><figcaption></figcaption></figure>

For information about how to update the Openblocks image to the latest version, see [Update](./#update).

| Location | Usage |

| ------------------------------------------------------------ | --------------------------------------------------- |

| <p><code>~/openblocks/docker-compose.yml</code><br></p> | Setting up Docker ports, volumes, environments etc. |

| `~/openblocks/stacks/configuration/application-selfhost.yml` | Setting up Openblocks server configurations |

For information about how to customize deployment configurations, see [Customize deployment configurations](./#customize-deployment-configurations).

5. Choose a plan and size for your Droplet, which determines its RAM, disk space, and vCPUs as well as its price. We'd recommend a system spec with **1 core CPU and 2 GB RAM** or the above.

Note that the **Basic** shared CPU with **Regular with SSD (1 GB CPU / 25GB SSD Disk / 1000GB transfer)** CPU option is more than capable of hosting an Openblocks instance.

You can use Droplet Web Console to connect to your instance to update the image or customize deployment configurations.&#x20;

| Location | Usage |

| ------------------------------------------------------------ | --------------------------------------------------- |

| <p><code>~/openblocks/docker-compose.yml</code><br></p> | Setting up Docker ports, volumes, environments etc. |

| `~/openblocks/stacks/configuration/application-selfhost.yml` | Setting up Openblocks server configurations |