Architecture details
This section describes the components and AWS services that make up this solution and the architecture details on how these components work together.
AWS services in this solution
The following AWS services are included in this solution:
| AWS service | Description |
|---|---|
|
To distribute the frontend web UI assets. |
|
|
To store the static web assets (frontend user interface), and also uses it as a data buffer for log shipping. |
|
|
To authenticate users (in AWS Regions). |
|
|
To provide the backend GraphQL APIs. |
|
|
To store the solution related information as a backend database. |
|
|
To interact with other AWS services to process the core logic of managing log pipelines or log agents, and obtain information updated in DynamoDB tables. |
|
|
To orchestrate on-demand AWS CloudFormation deployment of a set of predefined stacks for log pipeline management. |
|
|
To provision the AWS resources for the modules of pipelines and the solution web console. |
|
|
To manage log agents for collecting logs from application servers, such as installing log agents (Fluent Bit) for application servers. |
|
|
To subscribe to logs from a CloudWatch Log Group or as a data buffer for log shipping, and then initiate the Log Processor Lambda to run. |
|
|
To subscribe the logs from CloudWatch Log Group and then put the logs into Amazon S3. |
|
|
To receive Amazon S3 Event Notifications and then initiate the Log Processor Lambda to run. |
|
|
To build the Light Engine. |
|
|
To build the Light Engine. |
