docs(byoc): add billable AWS services, cost model, and service limits…#6235
Open
Blargian wants to merge 1 commit into
Open
docs(byoc): add billable AWS services, cost model, and service limits…#6235Blargian wants to merge 1 commit into
Blargian wants to merge 1 commit into
Conversation
… pages Add three new BYOC reference pages under /cloud/reference/byoc/: - billable-aws-services (DOC-759) — full inventory of mandatory and optional AWS services BYOC provisions, with billing notes - cost-model-aws (DOC-760) — how ClickHouse Cloud and AWS infrastructure charges combine, with dominant cost drivers - aws-service-limits (DOC-761) — pre-deployment quota checklist for required and optional features Content is taken from the source text supplied in each ticket, with light edits for docs voice (you/your, contractions, sentence-case headings, :::note callouts) and cross-links between the three pages plus a Related section pointing to BYOC architecture / network security / privilege. Ambiguities / inconsistencies vs. the tickets, for reviewer attention: - DOC-761: the ticket's intro paragraph promises "a pre-deployment quota checklist, instructions for requesting increases, and ongoing monitoring guidance to prevent quota exhaustion as your services scale," but the ticket body only supplies the checklist tables. The page reproduces the intro verbatim and ships only the checklist, so it currently advertises two sections it doesn't deliver. The PM should provide the increase-request and monitoring content (or the intro should be trimmed before merge). - DOC-760: the ticket's URL placeholder said /cost-model but the link text said cost-model-aws. Used cost-model-aws to match the link text and the page title. - DOC-760: the ticket's "AWS Services Used by BYOC" link was a `<#>` placeholder. Linked it to the new billable-aws-services page. - DOC-759 / 760 / 761: all three tickets suggested top-level slugs under /cloud/reference/byoc/ (hyphenated). Pre-existing reference pages in this section use /cloud/reference/byoc/reference/<name> with underscores. Followed the ticket slugs as requested rather than matching the older convention. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
@Blargian is attempting to deploy a commit to the ClickHouse Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Add three new BYOC reference pages under /cloud/reference/byoc/:
Content is taken from the source text supplied in each ticket, with light edits for docs voice (you/your, contractions, sentence-case headings, :::note callouts) and cross-links between the three pages plus a Related section pointing to BYOC architecture / network security / privilege.
Ambiguities / inconsistencies vs. the tickets, for reviewer attention:
DOC-761: the ticket's intro paragraph promises "a pre-deployment quota checklist, instructions for requesting increases, and ongoing monitoring guidance to prevent quota exhaustion as your services scale," but the ticket body only supplies the checklist tables. The page reproduces the intro verbatim and ships only the checklist, so it currently advertises two sections it doesn't deliver. The PM should provide the increase-request and monitoring content (or the intro should be trimmed before merge).
DOC-760: the ticket's URL placeholder said /cost-model but the link text said cost-model-aws. Used cost-model-aws to match the link text and the page title.
DOC-760: the ticket's "AWS Services Used by BYOC" link was a
<#>placeholder. Linked it to the new billable-aws-services page.DOC-759 / 760 / 761: all three tickets suggested top-level slugs under /cloud/reference/byoc/ (hyphenated). Pre-existing reference pages in this section use /cloud/reference/byoc/reference/ with underscores. Followed the ticket slugs as requested rather than matching the older convention.
Summary
Checklist