Skip to content

Update the Cloudwatch Logs proposal #46

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ryanjjung merged 2 commits into from
Mar 16, 2026
+4 −3
Merged

Update the Cloudwatch Logs proposal #46

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a95b522
Update log stream naming scheme to be more terse
ryanjjung Mar 11, 2026
b4729c5
Update proposal for log streams
ryanjjung Mar 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions docs/rfc/application_logging/logging_to_cloudwatch_logs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,9 +42,10 @@ It should define the following resources:
- A [CloudWatch LogGroup](https://www.pulumi.com/registry/packages/aws/api-docs/cloudwatch/loggroup/) for the
environment. In implementation, keeping with AWS's log group naming conventions, this might be called something like
`/tb/mailstrom/stage` for the Mailstrom/Stalwart staging environment.
- A [CloudWatch LogStream](https://www.pulumi.com/registry/packages/aws/api-docs/cloudwatch/logstream/) for each
application. This is somewhat arbitrary and can be broken up however it makes sense. (i.e.
`/tb/mailstrom/stage/stalwart/mail` vs `/tb/mailstrom/stage/stalwart/management-api`)
- An optional [CloudWatch LogStream](https://www.pulumi.com/registry/packages/aws/api-docs/cloudwatch/logstream/) for
any applications which can't be configured (or we don't want to configure) to create a log stream on their own. This
is somewhat arbitrary and can be broken up however it makes sense. For example, by service: `stalwart/mail` vs
`stalwart/management-api`. Or one log stream per server node: `stalwart/node-001` vs `stalwart/node-050`.
- A set of [IAM Policies](https://www.pulumi.com/registry/packages/aws/api-docs/iam/policy/) allowing various levels of
access to these streams. Applications will need a write access policy. Users will need read access policies. There
should be a level of customization here, allowing the engineers to design access in ways that make sense for their
Expand Down
Loading