Tracks | Centralized Audit System | Fluid Attacks Help

Introduction

Tracks is the centralized audit system for the Fluid Attacks platform. It provides a unified way to track user actions, system changes, and security-related activities across all components.

Overview

Tracks serve as the backbone for:
  1. Audit logging across all platform components.
  2. Compliance reporting and security monitoring.
  3. Analytics and insights from user interactions.
  4. Event correlation and filtering capabilities.

Architecture

Tracks consist of:
  1. SDKs for multiple programming languages (Python, TypeScript, Kotlin).
  2. Lambda functions for event processing and storage.
  3. Database for event persistence and querying.
  4. API endpoints for event retrieval and analytics.

Key Documentation

Implementation Guide

  1. Audit Events - Comprehensive guide for implementing audit events.

API Documentation

  1. Swagger UI - Complete API reference and interactive testing.

SDK Documentation

  1. Python SDK - Python client library.
  2. TypeScript SDK - TypeScript client library.
  3. Kotlin SDK - Kotlin client library.

Development

Database Connection

For development purposes, you can connect directly to the Aurora database using AWS RDS authentication:

aws rds generate-db-auth-token \
  --hostname <aurora-endpoint> \
  --port 5432 \
  --username <username>

Notes
Note
Replace <aurora-endpoint> and <username> with your development environment values. The generated token is valid for 15 minutes and can be used with any PostgreSQL client.

Related: AWS Aurora Documentation - IAM Database Authentication

More about Tracks

  1. Audit events
Idea
Tip
Have an idea to simplify our architecture or noticed docs that could use some love? Don't hesitate to open an issue or submit improvements.