Steps (plugins) are really handy for fixing problems you didn’t even realize you had, not to mention help increase productivity.
What is a Step?
A Step is a self-contained bash script or compiled binary for accomplishing specific automation tasks. For example, a pip install, kubectl or a Docker push.
Because they are small isolated actions, they are portable, repeatable and reusable. Making them awesome.
Here are some of our most popular steps for integrating directly with AWS:
Install AWS CLI
The Install AWS CLI step is one of the most downloaded Steps on the Wercker Steps Registry. It's a relatively simple shell script that gets the latest AWS CLI application from AWS, installs it, and configures access keys, which allows any subsequent steps access to a given AWS account.
name: "Push application build to S3"
aws s3 cp artifact.tar.gz s3://myamazingnamespace/my-wordpress-app-1.2.1.tar.gz
In the above example you would have installed the AWS CLI, configured it with keys that would have been set as environment variables on Wercker Web, then pushed a build artefact to Amazon S3.
Elastic Beanstalk Deploy
The EB-Deploy plugin Step deploys applications to AWS Elastic Beanstalk from within your pipelines.
In the above example, the step would have triggered an AWS Elastic Beanstalk deploy of your application using environment variables you would have defined on Wercker Web.
In the above example, you would have triggered the creation of an AWS EC2 stack for a single instance Wordpress deployment, based on this public AWS Cloudformation template.
The Wercker-submitted Kubectl Step on the Steps Registry allows you to interact with Kubernetes clusters. Since Amazon EC2 is a popular hosting platform for Kubernetes deployments, you could, for example:
command: create -f my-wordpress-app-deployment.json
This example would have used the
kubectl tool to create a new deployment for your Wordpress application on your EC2-based Kubernetes cluster.
Create your own
The above examples are just a tiny snapshot of the most popular Wercker Steps that integrate with AWS. Check out the Steps Registry for the full directory, and if we happen to be missing a Step that performs an action you require on AWS, you can use our Steps documentation to write your own!
Why not join our early access club. We’ll invite you to try our beta products and treat you nice.
As usual, if you want to stay in the loop follow us on twitter @wercker or hop on our public slack channel. If it’s your first time using Wercker, be sure to tweet out your #greenbuilds, and we’ll send you some swag!