Use Cases

Scenario 1: Streamlined log centralization and analysis


Maintaining log visibility is challenging in a distributed system with numerous services and environments. Logs are scattered across different nodes, making troubleshooting, performance monitoring, and security analysis complex tasks.


Logging Service offers a streamlined approach to centralizing logs. Easily configure agents on your log sources to collect and forward logs to a central repository. These logs are securely transferred, efficiently stored, and indexed for analysis. You can create custom dashboards for real-time log visualization and analysis, helping you quickly detect and address issues, maintain security standards, and optimize your application's performance.

Scenario 2: Flexible log retention and storage


Effectively managing log retention and storage is a critical operational challenge. Storing logs for an extended period can be costly and cumbersome, while inadequate retention policies may lead to losing valuable historical data needed for compliance, auditing, and troubleshooting.


Logging Service offers flexibility in log retention and storage. Configure retention policies to remove logs based on your organization's requirements automatically. It ensures you retain logs for as long as necessary without incurring high storage costs. Additionally, you can use the service to search and retrieve older logs when needed, simplifying compliance audits and historical analysis.

Scenario 3: Real-time log monitoring during development and deployment


DevOps teams rely on real-time visibility into application logs during the development and deployment phases. Timely and continuous access to logs is essential for debugging, identifying issues, and ensuring smooth deployments.


Logging Service provides DevOps teams with near-real-time log monitoring capabilities. Integrate the service seamlessly into your development and deployment pipelines to capture and analyze logs as applications are built and deployed. As your application components interact and generate logs, Logging Service immediately ingests and makes them available for analysis. DevOps teams can set up alerts and notifications based on specific log events, ensuring rapid response to critical issues. This near-real-time log monitoring helps streamline development and deployment processes, reduces downtime, and ensures the successful release of reliable applications.

Scenario 4: Secure log access control across large teams


Managing access controls for logging data becomes exponentially complex for large, distributed teams. Trying to maintain security while enabling broad log access leads to increased risk, compliance issues, and operational bottlenecks.


Logging Service provides a robust sub-user management system to simplify access control across large teams. The primary account owner can create sub-users and selectively grant access to certain pipelines, sources, and log data views.

Note: A sub-user is a user who has access to the Logging Service but is not an administrator or an owner.

Sub-users can only view the log data they have been explicitly granted permission to access. This compartmentalized access control delivers several advantages:

  • Primary account owners maintain complete ownership and oversight of the total logging pipeline management.

  • Sub-users are granted appropriate access without undesired privileges or access to sensitive information.

  • Compliance and auditing functions have clear boundaries around access.

  • Organizational changes can be accommodated by adjusting sub-user permissions.

Last updated