Armory provides a scalable and flexible platform for automating software delivery. To help companies deploy software into multiple clouds, the core of Armory’s platform is powered by Operator, an open-source, continuous-delivery platform developed by Netflix and Google. Continuous delivery is a process that builds production software on a consistent basis.
Armory Operator acts as a workflow engine by combining build, provision, and deploy steps into an automated pipeline. It deploys your workloads (for example, containers, packages, and Amazon Machine Images) to your AWS environment, including Amazon Elastic Compute Cloud (Amazon EC2), Amazon Elastic Kubernetes Service (Amazon EKS), Amazon Elastic Container Service (Amazon ECS), and AWS Lambda.
With Armory's integrations, you can automate your code from commit to production, where users can then monitor applications, scale up, scale down, roll back, or roll forward. You can use Armory to view and automate all of these actions.
This Quick Start was developed by Armory in collaboration with AWS. Armory is an AWS Partner.
-
What you'll build
-
How to deploy
-
Cost and licenses
-
What you'll build
-
Use this Quick Start to set up the following Armory environment on AWS:
- A highly available architecture that spans three Availability Zones.
- A virtual private cloud (VPC) configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS.
- In the public subnets:
- A Linux bastion host, configured for Kubernetes, in an Auto Scaling group to allow inbound Secure Shell (SSH) access to Amazon Elastic Compute Cloud (Amazon EC2) instances in the private subnets.
- A managed network address translation (NAT) gateway to allow outbound internet access for resources in the private subnets.
- In the private subnets:
- A group of Kubernetes nodes.
- ElastiCache Redis for caching storage for Orca and Clouddriver.
- Amazon Aurora for persistent storage of Orca and Clouddriver assets.
- Amazon EKS for the underlying Kubernetes infrastructure and platform.
- Amazon Simple Storage Service (Amazon S3) for persistent storage of Armory objects.
- An Armory Operator installation in an Amazon EKS cluster, which creates the Kubernetes control plane.
- A highly available architecture that spans three Availability Zones.
-
How to deploy
-
To build your Armory Enterprise environment on AWS, follow the instructions in the deployment guide. Depending on the parameter values you choose, the deployment process takes about 15–90 minutes and includes these steps:
- Sign in to your AWS account. If you don't have an account, you can sign up for one at https://aws.amazon.com.
- Launch the Quick Start. Choose the Region from the top toolbar before creating the stack.
- Test the deployment.
Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on this solution.
- Sign in to your AWS account. If you don't have an account, you can sign up for one at https://aws.amazon.com.
-
Cost and licenses
-
You are responsible for the cost of the AWS services and any third-party licenses used while running this Quick Start reference deployment. There is no additional cost for using this Quick Start.
The Armory Quick Start is free to try but requires an Armory license for production environments. To obtain a production license, contact Armory.
The AWS CloudFormation templates for this Quick Start include configuration parameters that you can customize. For cost estimates, see the pricing pages for each AWS service you use. Prices are subject to change.
Tip: After you deploy the Quick Start, create AWS Cost and Usage Reports to track costs associated with the Quick Start. These reports deliver billing metrics to an Amazon S3 bucket in your account. They provide cost estimates based on usage throughout each month and aggregate the data at the end of the month. For more information, see What are AWS Cost and Usage Reports?
