docs(aws-serverless): update LMI skill for region expansion and scheduled scaling#1
Open
sbbhimji wants to merge 3 commits into
Open
docs(aws-serverless): update LMI skill for region expansion and scheduled scaling#1sbbhimji wants to merge 3 commits into
sbbhimji wants to merge 3 commits into
Conversation
…uled scaling - Region availability: now all commercial AWS Regions except Israel (Tel Aviv), Middle East (Bahrain), Middle East (UAE), and Asia Pacific (Auckland); update Unsupported Region handling. - Scheduled scaling: document EventBridge Scheduler-based scheduled scaling of Min/Max execution environments for predictable traffic (SKILL.md, configuration-guide.md, infrastructure-setup.md).
…e JSONB" (awslabs#200) * fix(dsql): reframe JSON/JSONB/array storage as a choice, not "MUST use JSONB" The native JSON/JSONB rollout left this skill prescribing a single answer. Two drift directions existed: some files said "MUST serialize arrays as JSONB" / "prefer JSONB over JSON" (over-correction), others still said "store as TEXT" / "SET -> TEXT" (stale pre-JSON framing). Bring all nine steering files in line with the already-reviewed wording in awslabs/mcp: serializing is the MUST (DSQL has no array column type); the format is a choice — PREFER JSONB for queryable values, MAY use TEXT when opaque, JSON when writes dominate or byte-exact preservation matters; keep existing JSON columns as JSON when migrating. ASK the user. Files: SKILL.md, references/development-guide.md, references/onboarding.md, references/troubleshooting.md, references/examples/{patterns,schema}.md, references/mysql-migrations/{type-mapping,full-example,ddl-type-alternatives}.md. Bump databases-on-aws to 1.3.3. * ci: exclude broken registry rule bbp-pattern-inject from semgrep The community registry rule bbp-pattern-inject fails to parse ("Invalid pattern for Python: Stdlib.Parsing.Parse_error"), making semgrep exit 2 and fail every PR regardless of findings. Exclude it the same way other unwanted registry rules already are.
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
3 participants
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
Updates the
aws-lambda-managed-instancesskill for two recent Lambda Managed Instances launches:MinExecutionEnvironments/MaxExecutionEnvironmentson a one-time or recurring schedule for predictable traffic (scale up before peak, scale down or to zero when idle).Files changed
SKILL.md: regional availability + unsupported-region scenario;scheduled scalingtrigger andscheduled-scalingtag in frontmatter; scheduled-scaling note in Step 3; two Operations best practices; reference-file pointers; Scaling docs link in Resources.references/configuration-guide.md: new "Scheduled Scaling (Predictable Traffic)" section — behavior notes (still scales on CPU/concurrency between bounds;Min=Max=0deactivates and needs explicit reactivation) and a common-patterns table.references/infrastructure-setup.md: new "Scheduled Scaling (EventBridge Scheduler)" section — scheduler IAM trust/permissions policies,create-scheduleexamples targeting thePutFunctionScalingConfiguniversal target, and a manualput-function-scaling-configoverride.Testing
dprint check— cleanmarkdownlint-cli2(incl. custom skill-length + frontmatter rules) — 0 errorslint:cross-refs— 0 errorsvalidate:refs— 0 broken linksvalidate:size— SKILL.md 225 lines / 1566 words, description 626 chars (all under limits)Documentation-only change; content verified against the LMI scaling documentation. Security scanners (gitleaks/checkov/etc.) were not run in this environment — the change adds only docs with placeholder identifiers (
<account-id>), no real secrets or IaC files.