Deploy to Amazon S3

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 assets in your S3 buckets on every push to branch. You can also deploy manually on click, or recurrently on time intervals.

Pipeline example using AWS S3

Configure AWS permissions

  1. Log in to your AWS account and go to IAMUsers
  2. Click Add user and fill in the details. Make sure to check the Programmatic access type.
  3. On the permissions page switch to Attach existing policies directly and check the following policies:
s3:ListAllMyBuckets
s3:GetObject
s3:PutObject
s3:PutObjectAcl (required for Public flag)
s3:DeleteObject

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.

Creating AWS S3 policy

Configure Amazon S3 action

  1. Create a new project, select your Git provider and choose the repository with your project.
  2. Add a new pipeline and configure the details: name, trigger mode, and branch from which you want to deploy.
  3. Look up and click S3 on the action list:

AWS actions

  1. Configure AWS integration:
  • enter the name of your integration
  • paste the Access and Secret keys that you copied from the AWS console

Adding AWS integration

  1. Configure action details:
  • select the Bucket ID where you want to upload your files
  • set the Remote path to deploy to a specific path in the bucket

Configuring AWS S3 action in Buddy

If you are using build actions in your pipeline, make sure to select the Filesystem as the source to deploy artifacts and processed files.

  1. 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.
  • Tick the Public box in More Options if you want the files to be accessible via HTTP.
  • Tick Use Reduced Redundancy Storage to send the files in RRS mode. You can find out more about RRS here.