docs: add example AWS deployment guide for split deployment on EKS - #481
Open
ottonomy wants to merge 1 commit into
Open
docs: add example AWS deployment guide for split deployment on EKS#481ottonomy wants to merge 1 commit into
ottonomy wants to merge 1 commit into
Conversation
Adds docs/example-deployment.md, a reference description of deploying OSMT on AWS/EKS with a public read-only instance and a VPN-gated staff authoring instance, written for a site reliability engineer implementing it with their own infrastructure-as-code. Covers the two-instance model and the readonly profile boundary, an EKS reference architecture sized for low traffic, per-instance configuration, OIDC on the staff domain with a PingFederate worked example and Entra ID variations, white-label brand color and logo delivery via ConfigMap, Aurora MySQL including the required sql_mode pin and the read-only grant, restoring from a database snapshot, and Elasticsearch 8.x via the ECK operator. Every environment variable, Spring profile expression, and config property in the document was verified against api/ source and the reference Terraform module. Plan: ~/.skybridge/planning/osmt/2026-07-21-example-deployment/plan.md Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Adds docs/example-deployment.md, a reference description of deploying OSMT on AWS/EKS with a public read-only instance and a VPN-gated staff authoring instance, written for a site reliability engineer implementing it with their own infrastructure-as-code.
Covers the two-instance model and the readonly profile boundary, an EKS reference architecture sized for low traffic, per-instance configuration, OIDC on the staff domain with a PingFederate worked example and Entra ID variations, white-label brand color and logo delivery via ConfigMap, Aurora MySQL including the required sql_mode pin and the read-only grant, restoring from a database snapshot, and Elasticsearch 8.x via the ECK operator.
Every environment variable, Spring profile expression, and config property in the document was verified against api/ source and the reference Terraform module.
Plan: ~/.skybridge/planning/osmt/2026-07-21-example-deployment/plan.md