---
title: "Deploying a package to AWS with Systems Manager"
description: "Alchemy Compatibility Packages can be deployed to servers in Amazon Web Services (AWS)."
product: "Alchemy"
edition: "Public"
type: "workflow"
url: "https://docs.cloudhouse.com/public/deploying-packages/technical-reference/aws/deploying-a-package-to-aws-with-systems-manager/"
---
# Deploying a package to AWS with Systems Manager

Cloudhouse Alchemy Compatibility Packages can be deployed to servers in Amazon Web Services (**AWS**).

Applies to: `Alchemy`

![Deploying a Cloudhouse Compatibility Container in Amazon Web Services (AWS)](https://docs.cloudhouse.com/public/assets/images/helpjuice-import/deploying-an-alchemy-compatibility.png)

!!! note

    See [Sample Systems Manager Document for Deploying a Package to AWS](https://docs.cloudhouse.com/public/deploying-packages/technical-reference/aws/sample-systems-manager-document/index.md) for more details.

## Deploy an Alchemy Compatibility Package to AWS

To deploy an Alchemy Compatibility Package to AWS requires an Identity and Access Manager (**IAM**) user with permissions to:

- Administer all Elastic Compute Cloud (**EC2**) instances within the relevant region.
- Read from the Simple Storage Service (**S3**) resource(s).

Complete the following steps:

1. The Systems Manager documents must also be in the same region as the EC2 instances.
2. Create a ZIP of the Compatibility Package as detailed in [Zipping and Deploying a Package](https://docs.cloudhouse.com/public/deploying-packages/technical-reference/zipping-and-deploying-a-package/index.md).
3. Upload the ZIP to an AWS S3 bucket and record the URL.
4. Upload a copy of the `DeployZippedPackage.ps1` script from [Zipping and Deploying a Package](https://docs.cloudhouse.com/public/deploying-packages/technical-reference/zipping-and-deploying-a-package/index.md) to an AWS S3 bucket recording the URL.
5. Create a new AWS Systems Manager Document called `Cloudhouse-DeployPackage`.
6. Paste the contents of [Sample Systems Manager Document for Deploying a Package to AWS](https://docs.cloudhouse.com/public/deploying-packages/technical-reference/aws/sample-systems-manager-document/index.md) into the new document, then click **Create document**.
7. Open the `Cloudhouse-DeployPackage` document and click the **Details** tab followed by the **Parameters** tab to show the required/supported parameters.
8. From the **Actions** menu, select **Run Command**.
9. For each host and package, run the `Cloudhouse-DeployPackage` document with the following settings:

    1. Source Type – Set this to `S3`.
    2. **Source info** – Set this to the URL of the S3 bucket the `DeployZippedPackage.ps1` is stored on, for example:

        ```
        {"path" : "https://s3.eu-west-2.amazonaws.com/xxxxredactedname/DeployZippedPackage.ps1"}
        ```

    3. **Source Zip** – Set this to the URL of the S3 bucket the `Package.zip` is stored on, for example:

        ```
        {"path" : "https://s3.eu-west-2.amazonaws.com/xxxxredacted-name/SQLServer2005-Package-1666.zip"}
        ```

    4. **Command Line** – Should be `DeployZippedPackage.ps1` with the relevant switches (as detailed in [Zipping and Deploying a Package](https://docs.cloudhouse.com/public/deploying-packages/technical-reference/zipping-and-deploying-a-package/index.md)), which extracts the zipped Compatibility Package and then runs the `Cloudhouse.Container.Deployment.exe` with the specified deployment arguments (detailed in [Deploy an Alchemy Compatibility Package to a Machine](https://docs.cloudhouse.com/public/deploying-packages/deploy-to-a-machine/index.md)). For example:

        ```
        DeployZippedPackage.ps1 -sourcezip SQLServer2005-Package-1666.zip -deploycmd Cloudhouse.Container.Deployment.exe -deployargs '/deploydir c:\\programdata /deploytype machine /acceptEULA'
        ```

    5. Working Directory – Should be the folder to download the files to. For example `C:\Temp`.

10. On the **Output** screen, verify each step has run successfully (including expanding the **Step 3 – Output** section to verify the commands successfully ran).
11. Sign in to the target computer the Compatibility Package has been deployed to.
12. Verify the application is installed, loads, and functions as expected.