> For the complete documentation index, see [llms.txt](https://docs.taskforce.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taskforce.sh/on-premises/aws/launch-aws-ami.md).

# Launch AWS AMI

You can find the latest Taskforce.sh AMI on-premise product on the AWS Marketplace. All versions are listed [here](https://aws.amazon.com/marketplace/seller-profile?id=36523b71-72b9-4cc6-a5e6-89c3af6b2719).

Simply follow the configuration steps provided by the AWS Marketplace and launch the instance.

It is convenient to create a new security group directly on the launch configuration wizard:

![](/files/-MjStCSTSGnG0P7u6SKq)

{% hint style="danger" %}
Note that by convenience the source IP is 0.0.0.0/0, however you can later restrict sources to narrow ranges, like only the loadbalancer used for routing the traffic to the instance for example.
{% endhint %}

You can also optionally create the security group after the AMI has been launched:

![](https://gblobscdn.gitbook.com/assets%2F-MG01zoyzHgr18e2IutZ%2F-MgopRqwDR9dNlW4UI9I%2F-MgopfwjLxirSmmywS9i%2Fimage.png?alt=media\&token=2a97f125-78ba-43ed-8a6c-2db1eb346b6a)

Create two inbound rules, one for accessing the config tool and the other for accessing the Taskforce.sh dashboard itself.

![](/files/-MgopseenF_78Tw-AR1I)

{% hint style="info" %}
We are allowing all sources in this guide, but probably you will only want to allow a loadbalancer as source and configure TLS endpoints for production security.
{% endhint %}

You will also need to manually add an outbound rule, which normally is created automatically if using the wizard:

<figure><img src="/files/DueSzCsKxbazlRcsgdLn" alt=""><figcaption></figcaption></figure>

Finalize by creating the security group.

![](/files/-MgopXnawBqF4xz7MSA3)

Go back to your instance and choose "modify security groups":

![](/files/-Mgoqu1ybrP0iOHBBTMb)

Add the new security group and save.

![](/files/-Mgoqo13FFMvXVou19EQ)