Deploy to Amazon EC2
If you are new to Buddy, check out our quickstart guides that will tell you how to create build, test and deploy your type of application.
Buddy turns deployments into a breeze, allowing you to update your EC2 servers on every push to branch. You can also deploy manually on click, or recurrently on time intervals.
Example AWS EC2 pipeline
AWS EC2 deployment configuration
We recommend setting an Elastic IP in your EC2 instance. Without it, the Public IP may change whenever the EC2 is restarted.
- Log in to your AWS account and copy the Public IP of your EC2 instance:
Public IP of your EC2 instance - Create a new project, select your Git provider and choose the repository with your project.
- Add a new pipeline and configure the details: name, trigger mode, and branch from which you want to deploy.
- Deployment to EC2 is similar to deploying to a regular SFTP server. Look up and click SFTP on the action list:
SFTP action location - Configure EC2 server details:
- Change the Authentication mode to Password and paste the IP of the EC2 instance to Hostname
- Enter the Login and Password that you use to authenticate on EC2
EC2 action configuration
- When ready, click Add this action to finish configuration.
Click the Test button to verify connection details before saving the action.
Buddy's deployment is based on changesets. This means only changed files are deployed, which makes it lightning fast ⚡️. The first deployment is always performed from scratch, unless you set a revision on the server beforehand.
What you need to know
- Select Repository as the Source to deploy only the files from your repository. If you use build actions, select Pipeline Filesystem as the Source to add artifacts, processed files & uploaded static files.
- You can use environment variables to store authentication details to your servers.
- You can use Ignore paths to exclude files for deployment in More Options.
Last modified on April 26, 2022