reference deployment
JFrog Container Registry with Amazon ECS on AWS
Universal artifact repository manager
This Quick Start deploys JFrog Container Registry in a highly scalable and redundant configuration in the Amazon Web Servies (AWS) Cloud.
This Quick Start is for administrators who want the flexibility, scale, and availability of AWS through products such as Amazon Virtual Private Cloud (Amazon VPC), Amazon Elastic Compute Cloud (Amazon EC2), Amazon Elastic Kubernetes Service (Amazon EKS), Amazon Simple Storage Service (Amazon S3), Elastic Load Balancing (ELB), and Amazon Relational Database Service (Amazon RDS) to deploy Container Registry as their Docker container and Helm Chart repository manager.
-
What you'll build
-
How to deploy
-
Cost and licenses
-
What you'll build
-
Use this Quick Start to automatically set up Container Registry on AWS. The deployment includes the following:
- A highly resilient architecture that spans two 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.*
- A Network Load Balancer attached to the public subnets connecting via port 443 to the NGINX container, providing reverse-proxy and SSL termination for the Container Registry node listening on port 8081.
- A private and encrypted S3 bucket for repository storage.
- In the public subnets:
- Managed NAT gateways to allow outbound internet access for resources in the private subnets.*
- A Linux bastion host in an Auto Scaling group to allow inbound Secure Shell (SSH) access to EC2 instances in public and private subnets.*
- In the private subnets:
- One Amazon ECS service group for the Container Registry deployment.
- Container Registry and NGINX containers.
- An Auto Scaling group configured specifically for Container Registry.
- An Amazon RDS instance accessible only from the private subnets on port 5532.
* The template that deploys the Quick Start into an existing VPC skips the components marked by asterisks and prompts you for your existing VPC configuration.
-
How to deploy
-
To deploy JFrog Container Registry on AWS in about 1 hour, follow the instructions in the deployment guide. The deployment process includes these steps:
- If you don't already have an AWS account, sign up at https://aws.amazon.com, and sign in to your account.
- Launch the Quick Start. You can choose from the following two options:
- Set up Container Registry.
Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on this solution.
- If you don't already have an AWS account, sign up at https://aws.amazon.com, and sign in to your account.
-
Cost and licenses
-
You are responsible for the cost of the AWS services used while running this Quick Start reference deployment. There is no additional cost for using the Quick Start.
The AWS CloudFormation template for this Quick Start includes configuration parameters that you can customize. Some of these settings, such as instance type, will affect the cost of deployment. For cost estimates, see the pricing pages for each AWS service you will be using. Prices are subject to change.
Tip After you deploy the Quick Start, we recommend that you enable the AWS Cost and Usage Report to track costs associated with the Quick Start. This report delivers billing metrics to an S3 bucket in your account. It provides cost estimates based on usage throughout each month, and finalizes the data at the end of the month. For more information about the report, see What are AWS Cost and Usage Reports?.
The Quick Start requires a subscription to the Amazon Machine Image (AMI) for Container Registry, which is available from AWS Marketplace. Additional pricing, terms, and conditions may apply. For instructions, see "Subscribe to the Container Registry" in the deployment guide.
This Quick Start does not require you to purchase any license as JFrog Container Registry is a free product.