Repository navigation
docs: add architecture diagrams and organize runbooks - #2
Merged
Merged
Conversation
Terraform plan: devJob result: success. Commit:
Replacements also count toward Add and Destroy. Counts describe managed resources; output-only changes are not included. A deferred monitoring plan requires an existing cluster. Check the workflow logs for any failure or incomplete results. |
Terraform plan: prodJob result: success. Commit:
Replacements also count toward Add and Destroy. Counts describe managed resources; output-only changes are not included. A deferred monitoring plan requires an existing cluster. Check the workflow logs for any failure or incomplete results. |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Make the repository easier to inspect and operate from its GitHub landing page. The README now shows the AWS topology and a directory tree, with full setup, pipeline, and cost details in focused runbooks.
The editable draw.io document has two pages: AWS topology and deployment/state flow. SVG previews cover public Grafana ingress, private workers and monitoring, NAT egress, IRSA, OIDC roles, and separate workspace states. The drawings distinguish logical subnet tiers from replicated monitoring.
Terraform roots, module paths, inputs, state addresses, and workflow behavior are unchanged. The cleanup guide remains the complete teardown and AWS audit procedure.
Validation
No AWS actions or Terraform applies were run for this change.