Get Activepieces up & running on AWS with Pulumi for IaC
activepieces-dev
, ap-prod
etc.
This solution uses the stack name as a prefix for every AWS service created<stack name>-vpc
.yes
when prompted. Once the deployment has finished, you should see a bunch of Pulumi output variables that look like the following:activePiecesUrl
as that is the URL for our Activepieces deployment.
If you chose to add a fully qualified domain during your stack configuration, that will be displayed here.
Otherwise you’ll see the URL to the application load balancer. And that’s it.
Congratulations! You have successfully deployed Activepieces to AWS.
deploy/pulumi
folder & install the necessary npm packages:Pulumi.activepieces-dev.yaml
and Pulumi.activepieces-prod.yaml
.
These files already contain all the configurations we need to create our environments. Feel free to have a look & edit the values as you see fit.
Lets continue by creating a development stack that uses the existing Pulumi.activepieces-dev.yaml
file & kick off the deploy.activepieces-dev
or activepieces-prod
for the pulumi stack init
command is required here as the stack name needs to match the existing stack file name in the folder.yes
, a new image will be built based on the Dockerfile
in the root of the solution (make sure Docker Desktop is running) and then pushed up to a new ECR, along with provisioning all the other AWS services for the stack.index.ts
file inside the deploy
folder.
Or maybe you’d still like to deploy the official Activepieces Docker image instead of a local build, but would like to change some of the services. Simply set the deployLocalBuild
config option in the stack file to false
and make whatever changes you’d like to the index.ts
file.
Checking out the Pulumi docs before doing so is highly encouraged.