bash -c "$(curl -sS http://get.armory.io)"
That’s it! Our Installer will prompt you for the information listed in the System Requirements section below.
Note: We currently support all US regions. Here are some FAQs about the release. If you find bugs, let us know at email@example.com.
Learn more about Armory Spinnaker, including its features, roadmap, pricing, how it compares to the open source version, and how Armory runs customer engagements.
Get "Ridiculously Responsive" Support during the install
Five minute demo of the install process:
You’ll need an AWS account with an existing VPC and Subnet. The Installer will prompt you to enter the following:
- AWS Secret Access Key ID
- AWS Secret Access Key
- S3 Path Prefix and Bucket Name
- AWS Region
- AWS VPC ID
- AWS Subnet ID
- AWS Availability Zone
- AWS Keypair
You will also need to Docker installed and running on your local machine to run the install script.
What Armory Spinnaker does:
The installer will create following AWS resources behind the scenes:
- Autoscaling group and launch configuration
- Elastic Load Balancer
- Security group for the ELB
- Security group for the Spinnaker stack
- Elastic Cache (Redis)
- IAM Role for Spinnaker instances
- IAM Role for Spinnaker managed account
- IAM Policy Spinnaker S3 Access
- IAM Policy Spinnaker assume role permissions
- IAM Policy Spinnaker ECR read access
Upcoming Features for Armory Spinnaker:
- Audit Logging: Track and query every change made to production.
- Configuration Management: An easy way to inject application configs into dev, qa, stg, and production environments.
- Secrets Management: A safe and secure way to encrypt and decrypt secrets, passwords, and keys and manage them within your deployment pipelines.
- Deployment of Stateful Services: A simpler way to deploy databases and other stateful services.
Where can I learn more about Armory?
If you're not familiar with Armory and would like to learn more about us before you install Armory Spinnaker, here are some great places to start:
- Our website: http://www.Armory.io
- Recommended Armory Evaluation Process: http://go.Armory.io/Evaluate
- Armory Spinnaker Pricing: http://go.Armory.io/Pricing
- Our Company Manifesto: Why we believe it's important to make software a core competency within your business
- Want to work at Armory? Learn why Life at Armory is Awesome
Here's a transcript of the demo above:
Daniel: Hey, guys. It’s Daniel and Isaac from Armory. And we just have a first version of an Armory Spinnaker for AWS that I’m going to try installing for the first time. And Isaac is here, and he’s going to talk about why we made this and what problems it’s solving. I’ve got some very early instructions. We’re going to publish some better instructions on the blog. But before we start here, Isaac, is there anything that you would say just to give us some context.
Isaac:: Yeah, absolutely. Spinnaker is a product that has a lot of moving pieces and a lot of dependencies on Amazon infrastructure. And getting that all up wired correctly is difficult. And really, as an end user of Spinnaker, you really shouldn’t have to deal with those kinds of problems. You want to get started and be able to deploy safely and predictively without really worrying about the administration and the upkeep of Spinnaker itself. And so we built this installer really to get you started as quickly as possible to bypass all of the problems that we see on Slack every single day. We know a lot of them become common. And so we built this product really to get over those hurdles and get started with Spinnaker as quickly as possible.
Daniel: We’re making this video right at the end of 2016, so if you’re one of the first people to try this, you probably will encounter an error. We would absolutely like to hear about it if you do. So please reach out to us either on Slack or just firstname.lastname@example.org to let us know. And we’re going to keep making this better. All right, so let’s go ahead and jump into it. We’re going to start with this command here. Type this in terminal:
bash -c "$(curl -sS http://get.armory.io)"
Isaac:: What’s happening is we have a script that we’ve created. It’s just a very simple shell script that will download the Terraform templates and install it into your AWS account. Feel free to just go to get.armory.io and download the script and run it locally just to see exactly what we’re doing. So there’s nothing that we’re trying to hide in there. So if you want to understand a little bit more about what’s happening behind the scenes, you can absolutely go in there and see it. The very first prompt that we give you here is telling you exactly what we are going to do, which is creating a lot of these resources so that Spinnaker can work with them and you can see all the bits and pieces that we’re adding value to here and being able to bypass. So you don’t have to deal with stuff on your own.
Daniel: I’m going to go ahead and press Enter to continue.
Isaac:: Now we need to be able to start up these resources in a particular AWS account. Daniel is going to put in our secret keys [inaudible – 02:36] stuff. So we’re going to break away here for a little bit. But this is where you’re going to have to get access to a particular Amazon account.
Daniel: I’ll be right back after putting these in. Stand by. Okay, guys, so I just put in my secret ID on AWS. And I just minimized this to not show this. You can see that the next question it asks was for the bucket and the path and the region. Do you want to talk a little bit about that, Isaac?
Isaac:: Yeah. So we use the S3 bucket and the S3 path prefixes for two reasons. The first one is to be able to maintain the state of the Terraform templates or the infrastructure that we put into your Amazon account. And then the second is for Spinnaker to use as a backing store. The region is just the region that you want to deploy to. And then we get into specifics around VPCs and subnets so that we know exactly where to place the particular instances and that you have access to them. We also ask for a key pair as well so that you can actually [associate it into – 03:42] the machine if you ever need to. So I’m going to pause again and handle the VPC info. I’ll be right back.
Daniel: Okay, so I just entered the VPC info and created the key pair. You can see that I’ve got an error here because I’m not running Docker.
Isaac:: What we do is we actually depend on just Docker as the only dependency for this script. And so that way, you don’t have to install things like Terraform and a whole bunch of other dependencies. Instead, we can encapsulate that inside of Docker. And then all you need is Docker to be running on the background. Daniel doesn’t have Docker running. In the future, we’ll probably make this a little bit more user-friendly. But for now, Daniel is just going to start the Docker container. We’re going to start Docker, and we’ll be right back.
Daniel: Now I’ve got Docker. I’ll be running. I’m just going to start from the beginning command again. And I’ll just actually pause it until we get past this error. So I’ll be right back. We’re back. And I just reentered the information after restarting Docker. And now [inaudible – 04:56] the infrastructure. This process will take about 20 minutes. I’m just going to pause it again. We’ll be back in a bit. Okay, so we’re back. And I reentered the information. You can see here that Armory created the infrastructure and got Spinnaker up and running. The Armory Spinnaker instance is up. Check it out. I’m just going to paste in this URL. And you can see that we now have Spinnaker up and running. So we’d love to have you give us a shot and give us feedback. Thanks.