reference deployment

JFrog SaaS Log Collector on AWS

Collect and store JFrog application logs for Splunk data-analytics platform

This Partner Solution deploys the JFrog software-as-a-service (SaaS) log collector on the Amazon Web Services (AWS) Cloud. The log collector retrieves logs from your JFrog SaaS environment, parses them, and then forwards them to Splunk data analytics platform.

The JFrog Platform uses its Cloud Log Collection function to collect standardized logs for all JFrog products and their services. Each log provides information about various use cases, including cloud usage, billing, and real-time system debugging. Once the Cloud Log Collection function collects the logs, they are stored in a dedicated JFrog Artifactory repository. For more information about the JFrog SaaS log collector, refer to Cloud Log Collection.

JFrog logo

This Partner Solution was developed by JFrog in collaboration with AWS. JFrog is an AWS Partner.

  •  What you'll build
  • This Partner Solution sets up the following:

    • A highly available 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.*    
    • 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 Amazon Elastic Compute Cloud (Amazon EC2) instances in public and private subnets.*
    • In the private subnets:
      • One Amazon EC2 instance that runs the JFrog SaaS log collector and Fluentd, an open-source data collector, to send log-analytics data to Splunk. 
    • AWS Secrets Manager to store the JFrog Platform administrator token and the Splunk HTTP Event Collector (HEC) token. 

    * The template that deploys the Partner Solution into an existing VPC skips the components marked by asterisks and prompts you for your existing VPC configuration.

  •  How to deploy
  • To deploy this Partner Solution, follow the instructions in the deployment guide, which includes these steps. 

    1. Sign in to your AWS account. If you don't have an account, sign up at
    2. Subscribe to the CentOS Amazon Machine Image (AMI) and obtain a JFrog cloud instance subscription
    3. Launch the Partner Solution. The deployment process takes about 15 minutes. Choose the Region from the top toolbar before creating the stack. You can choose from the following options:

    Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on this solution.  

  •  Costs and licenses
  • This Partner Solution requires a subscription to the CentOS AMI and a JFrog cloud instance subscription.

    You are responsible for the cost of the AWS services and any third-party licenses used while running this solution. There is no additional cost for using the solution.

    This solution includes configuration parameters that you can customize. Some of these settings, such as instance type, affect the cost of deployment. For cost estimates, refer to the pricing pages for each AWS service you use. Prices are subject to change.

    Tip: After you deploy a solution, create AWS Cost and Usage Reports to track associated costs. These reports deliver billing metrics to an Amazon Simple Storage Service (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, refer to What are AWS Cost and Usage Reports?