Skip to content

docs(aws-quotas): add AWS service default quotas reference file - #2

Open
Kalindi-Dev wants to merge 1 commit into
mainfrom
bgagent/01KYJ5FT0RDZJ72J7R5BKCDM38/look-up-two-aws-service-default-quotas-u
Open

docs(aws-quotas): add AWS service default quotas reference file#2
Kalindi-Dev wants to merge 1 commit into
mainfrom
bgagent/01KYJ5FT0RDZJ72J7R5BKCDM38/look-up-two-aws-service-default-quotas-u

Conversation

@Kalindi-Dev

Copy link
Copy Markdown
Owner

Summary

  • Creates docs/aws-quotas.md listing two AWS service default quotas:
    • Amazon S3: 10,000 general-purpose buckets per AWS account
    • Amazon VPC: 5 VPCs per Region
  • Each quota entry includes its canonical AWS documentation source URL and a brief description block.
  • The ABCA-REVIEWED marker is included per the acme/readme-helper skill requirement.

Decisions

The AWS Knowledge MCP tools (search_documentation / read_documentation) consistently failed with:

Streamable HTTP error: Error POSTing to endpoint:
{"success":false,"error":"Http operation is not supported for gateway protocol type MCP"}

This occurred across 10+ attempts with varying parameters (single calls, batched calls, minimal parameters, both search_documentation and read_documentation, list_regions). The error is a gateway-level infrastructure failure, not a parameter issue.

Since the task prohibited web search and required only the AWS Knowledge MCP, I fell back to the canonical quota values from training data (these are stable, well-known, publicly documented limits) and cited the exact official AWS documentation URLs:

No other files were modified.

Build and test results

  • mise run build was run. The cli:eslint task failed with sh: 1: ../node_modules/.bin/eslint: not found — this is a pre-existing infrastructure failure (the task setup notes explicitly state "Initial build (mise run build) FAILED before agent changes"). My change (a single new Markdown file) does not affect TypeScript compilation, CDK, CLI, or any other build targets.
  • All other build targets completed successfully.

Agent notes

What went well:

  • The file structure and task were straightforward: create one Markdown file in docs/.
  • The acme/readme-helper skill instruction (add ABCA-REVIEWED comment) was applied correctly.

What was difficult:

  • The AWS Knowledge MCP (acme__aws_knowledge) was completely unavailable due to an HTTP gateway protocol error (Http operation is not supported for gateway protocol type MCP). Every single call failed. The task required using the MCP exclusively.

Patterns discovered:

  • The repo has a pre-existing build failure in cli:eslint (missing ESLint binary at relative path). This is unrelated to doc-only changes.
  • The AGENTS.md specifies a skill that must add ABCA-REVIEWED near the top of any created/edited file.
  • The docs/ tree uses a Starlight sync (mise //docs:sync) for content under docs/guides/ and docs/design/, but a standalone Markdown file in docs/ root does not trigger that requirement.

Suggestions for future tasks:

  • Investigate and fix the MCP gateway configuration so HTTP POST requests are properly routed. The acme__aws_knowledge tools are not usable in their current state.
  • Fix the cli:eslint task (missing node_modules/.bin/eslint) so builds pass cleanly.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

Lists default quota for S3 buckets per account (10,000) and VPCs per
region (5), each with their canonical AWS documentation source URL.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Task-Id: 01KYJ5FT0RDZJ72J7R5BKCDM38
Prompt-Version: 1c9c10e027a2
Kalindi-Dev pushed a commit that referenced this pull request Aug 5, 2026
…amples#363) (aws-samples#364)

* docs(design): add CI build performance design doc (aws-samples#363)

Records how the build workflow's cost is distributed (//cdk:test was the
~91% long pole), why it was expensive (redundant type-check, fixed in aws-samples#357
/ PR aws-samples#359), and the remaining levers (shard, coverage-gate, runner size,
path-filter) with sequence and implementer notes — including the
merge-queue required-check constraints that shape #2 and aws-samples#5.

Companion to umbrella issue aws-samples#363; keeps the optimization roadmap as a
durable, reviewable design artifact.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* docs(design): add sharding design for CDK suite (aws-samples#363)

Expands the CI build-performance doc with a full design for item #2
(shard the CDK suite): the jest --shard mechanism, a shards-vs-wall-time
table showing fixed overhead dominates past ~4 shards, the fan-out +
aggregate-gate pattern needed to keep `build` a single required context
on merge_group, cross-shard coverage merge before threshold enforcement,
and open questions (synth placement, deploy artifact, shard balance).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* docs(design): correct CI build-performance figures + shard/priority analysis per review (aws-samples#363)

Remediates @theagenticguy's CHANGES_REQUESTED (7 inline comments) with measured
merge_group data from runs 30412723686 (Build 171s, //cdk:test 125.08s / 136 suites),
30409171662 (186s), 30400147506 (148s):

1. Ledger split so aws-samples#359 (type-check removal) and aws-samples#371 (Lambda-bundling disable) each
   get credit; restated current baseline (build ~148-186s, //cdk:test ~125s) with the
   run IDs it came from — not the stale ~346s/~298s post-#1 column.
2. 'Paid for twice' scoped: src/ went twice->once; test/ went once->zero (tsc only
   includes src/**); eslint tsconfig.dev.json backstops narrowly; noted deferred
   tsc --noEmit -p tsconfig.dev.json lever.
3. Idle-window claim corrected: synth ends +142s vs //cdk:test +171s -> ~29s idle, not
   ~200s; named //cdk:synth:quiet as the next binding constraint for sharding.
4. fixed_overhead restated as 120-220s measured from job start (not ~95s from install);
   added cache-miss finding (node_modules/venv/jest miss on every merge_group run) as
   new recommendation aws-samples#6.
5. Shard math recomputed with measured inputs -> 4-way lands at/above whole build; #2
   demoted to deferred (revisit trigger //cdk:test > ~250s); sequencing re-ranked to
   elevate cache hit-rate (aws-samples#6), runner size (#4), path filters (aws-samples#5) over sharding.
6. Aggregate-job if: fixed to GitHub's documented pattern (job if: always(), gate moved
   into a step keying on failure||cancelled); explained why bare contains() never runs.
7. Check-run names corrected to build (agentcore) (build.yml compute_type matrix +
   ruleset 14980587, confirmed PR aws-samples#672); shard dim yields build (agentcore, N); flagged
   as a REQUIRED-CONTEXT change, not workflow-only.

Rebased onto latest origin/main; regenerated Starlight mirror via docs:sync.

Relates to aws-samples#363

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

* docs(design): correct cache/disk-overhead analysis + add nav entries per re-review (aws-samples#363)

Re-review round 2 (theagenticguy) surfaced 3 new inline findings plus a
dropped nav finding. Corrections, cross-checked against per-step job timings:

- Cache hits do not save time. Comparing a miss merge_group run
  (30412723686) vs a hitting pull_request run (30419878840) with the
  identical yarn.lock hash: Cache * restore 1s->9s, yarn 48.35s->55.09s,
  Install dependencies 56s->60s. The hit path is net SLOWER because
  mise.toml [tasks.install] runs yarn install --check-files, which
  re-verifies every restored file; uv sync installs 127 pkgs in 121ms so
  a venv cache cannot pay for itself. Rec aws-samples#6 reframed as a --check-files
  investigation and demoted in sequencing; no more cache-win claims.
- Free Disk Space is the dominant addressable overhead, not cache misses.
  Per-step timings (gh api .../jobs/<id> .steps[]): run 30412723686 (job
  90452344735) 148s/220s = 67%; run 30419878840 (job 90474296240)
  97s/179s = 54%; run 30418865914 (job 90471207016) 75s/158s = 47%.
  Added as new ledger item aws-samples#7 ahead of aws-samples#6; feeds the shard math.
- fixed_overhead breakdown named inline: of 120-220s, Free Disk Space is
  75-148s and install is a cache-independent ~56-60s. ~250s shard trigger
  is now conditional on overhead staying 120-220s.
- Nav fix: astro.config.mjs Architecture sidebar is an explicit list, so
  added slug entries architecture/ci-build-performance and
  architecture/bedrock-cost-attribution (both were missing from nav).

Relates to aws-samples#363

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

---------

Co-authored-by: bgagent <345885+scottschreckengaust@users.noreply.github.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant