Deploy to Amazon CodeDeploy
If you are new to Buddy, check out our quickstart guides that will tell you how to build, test and deploy your type of application.
đź“š Learn more about CodeDeploy action features, integrations and alternatives.
Buddy turns deployments into a breeze, allowing you to update your EC2 and on-premises servers on every push to branch. You can also deploy manually on click, or recurrently on time intervals.
Example Buddy pipeline with codedeploy
Configure AWS permissions
- Log in to your AWS account and go to IAM → Users.
- Click Add user and fill in the details. Make sure to check the Programmatic access type.
- On the permissions page switch to Attach existing policies directly.
- Click Create Policy and add the following policies:
codedeploy:ListApplications
codedeploy:ListDeploymentGroups
codedeploy:ListDeploymentConfigs
codedeploy:CreateDeployment
codedeploy:GetDeployment
codedeploy:GetDeploymentConfig
codedeploy:GetApplicationRevision
codedeploy:RegisterApplicationRevision
s3:ListBucket
s3:ListObjects
s3:CreateBucket
s3:PutObject
Creating a user in CodeDeploy
Once you create the user, make sure to copy the Access key and Secret key. You will need them to add the AWS integration to Buddy.
Configure CodeDeploy action
- 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
- Look up and click CodeDeploy on the action list:
AWS actions in Buddy
Configure AWS integration:
- enter the name of your integration
- paste the Access and Secret keys that you copied from the AWS console
Adding na AWS integration
- Configure action details:
AWS CodeDeploy 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