StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Log Management
  4. Log Management
  5. AWS CloudTrail vs Logback

AWS CloudTrail vs Logback

OverviewDecisionsComparisonAlternatives

Overview

AWS CloudTrail
AWS CloudTrail
Stacks304
Followers280
Votes14
Logback
Logback
Stacks5.6K
Followers76
Votes0

AWS CloudTrail vs Logback: What are the differences?

Developers describe AWS CloudTrail as "Record AWS API calls for your account and have log files delivered to you". With CloudTrail, you can get a history of AWS API calls for your account, including API calls made via the AWS Management Console, AWS SDKs, command line tools, and higher-level AWS services (such as AWS CloudFormation). The AWS API call history produced by CloudTrail enables security analysis, resource change tracking, and compliance auditing. The recorded information includes the identity of the API caller, the time of the API call, the source IP address of the API caller, the request parameters, and the response elements returned by the AWS service. On the other hand, Logback is detailed as "A logging framework for Java applications". It is intended as a successor to the popular log4j project. It is divided into three modules, logback-core, logback-classic and logback-access. The logback-core module lays the groundwork for the other two modules, logback-classic natively implements the SLF4J API so that you can readily switch back and forth between logback and other logging frameworks and logback-access module integrates with Servlet containers, such as Tomcat and Jetty, to provide HTTP-access log functionality.

AWS CloudTrail and Logback belong to "Log Management" category of the tech stack.

Netflix, Slack, and Seat Pagine Gialle are some of the popular companies that use AWS CloudTrail, whereas Logback is used by Montoux, movix, and immmr. AWS CloudTrail has a broader approval, being mentioned in 50 company stacks & 59 developers stacks; compared to Logback, which is listed in 4 company stacks and 9 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on AWS CloudTrail, Logback

Jigar
Jigar

Security Software Engineer at Cisco

Jul 2, 2020

Needs adviceonAWS IAMAWS IAMAmazon EC2Amazon EC2Splunk CloudSplunk Cloud

We would like to detect unusual config changes that can potentially cause production outage.

Such as, SecurityGroup new allow/deny rule, AuthZ policy change, Secret key/certificate rotation, IP subnet add/drop. The problem is the source of all of these activities is different, i.e., AWS IAM, Amazon EC2, internal prod services, envoy sidecar, etc.

Which of the technology would be best suitable to detect only IMP events (not all activity) from various sources all workload running on AWS and also Splunk Cloud?

168k views168k
Comments

Detailed Comparison

AWS CloudTrail
AWS CloudTrail
Logback
Logback

With CloudTrail, you can get a history of AWS API calls for your account, including API calls made via the AWS Management Console, AWS SDKs, command line tools, and higher-level AWS services (such as AWS CloudFormation). The AWS API call history produced by CloudTrail enables security analysis, resource change tracking, and compliance auditing. The recorded information includes the identity of the API caller, the time of the API call, the source IP address of the API caller, the request parameters, and the response elements returned by the AWS service.

It is intended as a successor to the popular log4j project. It is divided into three modules, logback-core, logback-classic and logback-access. The logback-core module lays the groundwork for the other two modules, logback-classic natively implements the SLF4J API so that you can readily switch back and forth between logback and other logging frameworks and logback-access module integrates with Servlet containers, such as Tomcat and Jetty, to provide HTTP-access log functionality.

Increased Visibility- CloudTrail provides increased visibility into your user activity by recording AWS API calls. You can answer questions such as, what actions did a given user take over a given time period? For a given resource, which user has taken actions on it over a given time period? What is the source IP address of a given activity? Which activities failed due to inadequate permissions?;Durable and Inexpensive Log File Storage- CloudTrail uses Amazon S3 for log file storage and delivery, so log files are stored durably and inexpensively. You can use Amazon S3 lifecycle configuration rules to further reduce storage costs. For example, you can define rules to automatically delete old log files or archive them to Amazon Glacier for additional savings.;Easy Administration- CloudTrail is a fully managed service; you simply turn on CloudTrail for your account using the AWS Management Console, the Command Line Interface, or the CloudTrail SDK and start receiving CloudTrail log files in the Amazon Simple Storage Service (Amazon S3) bucket that you specify.;Reliable- CloudTrail continuously transports events from AWS services using a highly available and fault tolerant processing pipeline.;Timely Delivery- CloudTrail typically delivers events within 15 minutes of the API call.;Log File Aggregation- CloudTrail can be configured to aggregate log files across multiple accounts and regions so that log files are delivered to a single bucket. Please refer to the of the AWS CloudTrail User Guide for detailed instructions.;Notifications for Log File Delivery- CloudTrail can be configured to publish a notification for each log file delivered, thus enabling you to automatically take action upon log file delivery. CloudTrail uses the Amazon Simple Notification Service (SNS) for notifications.;Choice of Partner Solutions- Multiple partners including AlertLogic, Boundary, Loggly, Splunk and Sumologic offer integrated solutions to analyze CloudTrail log files. These solutions include features like change tracking, troubleshooting, and security analysis.
-
Statistics
Stacks
304
Stacks
5.6K
Followers
280
Followers
76
Votes
14
Votes
0
Pros & Cons
Pros
  • 7
    Very easy setup
  • 3
    Good integrations with 3rd party tools
  • 2
    Very powerful
  • 2
    Backup to S3
No community feedback yet
Integrations
Boundary
Boundary
Loggly
Loggly
Splunk Cloud
Splunk Cloud
No integrations available

What are some alternatives to AWS CloudTrail, Logback?

Papertrail

Papertrail

Papertrail helps detect, resolve, and avoid infrastructure problems using log messages. Papertrail's practicality comes from our own experience as sysadmins, developers, and entrepreneurs.

Logmatic

Logmatic

Get a clear overview of what is happening across your distributed environments, and spot the needle in the haystack in no time. Build dynamic analyses and identify improvements for your software, your user experience and your business.

Loggly

Loggly

It is a SaaS solution to manage your log data. There is nothing to install and updates are automatically applied to your Loggly subdomain.

Logentries

Logentries

Logentries makes machine-generated log data easily accessible to IT operations, development, and business analysis teams of all sizes. With the broadest platform support and an open API, Logentries brings the value of log-level data to any system, to any team member, and to a community of more than 25,000 worldwide users.

Logstash

Logstash

Logstash is a tool for managing events and logs. You can use it to collect logs, parse them, and store them for later use (like, for searching). If you store them in Elasticsearch, you can view and analyze them with Kibana.

Graylog

Graylog

Centralize and aggregate all your log files for 100% visibility. Use our powerful query language to search through terabytes of log data to discover and analyze important information.

Sematext

Sematext

Sematext pulls together performance monitoring, logs, user experience and synthetic monitoring that tools organizations need to troubleshoot performance issues faster.

Fluentd

Fluentd

Fluentd collects events from various data sources and writes them to files, RDBMS, NoSQL, IaaS, SaaS, Hadoop and so on. Fluentd helps you unify your logging infrastructure.

ELK

ELK

It is the acronym for three open source projects: Elasticsearch, Logstash, and Kibana. Elasticsearch is a search and analytics engine. Logstash is a server‑side data processing pipeline that ingests data from multiple sources simultaneously, transforms it, and then sends it to a "stash" like Elasticsearch. Kibana lets users visualize data with charts and graphs in Elasticsearch.

Sumo Logic

Sumo Logic

Cloud-based machine data analytics platform that enables companies to proactively identify availability and performance issues in their infrastructure, improve their security posture and enhance application rollouts. Companies using Sumo Logic reduce their mean-time-to-resolution by 50% and can save hundreds of thousands of dollars, annually. Customers include Netflix, Medallia, Orange, and GoGo Inflight.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana