Preconfigured Platform AWS EB
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.
Buddy turns deployments into a breeze, allowing you to update your Elastic Beanstalk applications on every push to branch. You can also deploy manually on click, or recurrently on time intervals.
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 for your service:
elasticbeanstalk:DescribeApplications elasticbeanstalk:DescribeEnvironments elasticbeanstalk:CreateApplicationVersion elasticbeanstalk:DescribeApplicationVersions elasticbeanstalk:UpdateApplication elasticbeanstalk:UpdateEnvironment elasticbeanstalk:UpdateApplicationVersion s3:CreateBucket s3:PutObject s3:CopyObject s3:GetObject s3:GetObjectAcl s3:GetObjectMetadata s3:ListBucket s3:ListBuckets s3:ListObjects cloudformation:GetTemplate
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 Elastic Beanstalk 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 Elastic Beanstalk on the action list:
- Configure AWS integration:
- enter the name of your integration
- paste the Access and Secret keys that you copied from the AWS console
- Configure action details:
- select your AWS region, Application and Environment where you want to upload your files
- When ready, click Add this action to finish configuration.
Click the Test button to verify connection to your server 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.
[Option] Configure Monitoring action
Uploading files to Elastic Beanstalk doesn't have to mean that the deployment was successful. For example, the latest changes might might cause the application not to install properly.
To make sure everything is okay you can add the Elastic Beanstalk Monitoring action. It will check if the new version of the app has successfully started:
What you need to know
- You can enter custom Version label for your Elastic Beanstalk registry. By default, the version is
- 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.