Skip to content

fix(skill): reject reserved Lambda concurrency, which new accounts refuse - #20

Merged
jhermesn merged 1 commit into
mainfrom
fix/reserved-lambda-concurrency
Nov 5, 2026
Merged

jhermesn merged 1 commit into
mainfrom
fix/reserved-lambda-concurrency

Conversation

@jhermesn

@jhermesn jhermesn commented Nov 5, 2026

Copy link
Copy Markdown
Owner

A new account's Lambda concurrency limit is 10, and Lambda keeps that much unreserved, so any reserved concurrency fails there. Four labs failed in real-account self-tests for this reason: three at deployment (template) and one in the reference solution.

  • New guard rule QUOTA_LAMBDA_NO_RESERVED_CONCURRENCY: no ReservedConcurrentExecutions on AWS::Lambda::Function.
  • validate_lab.sh rejects aws lambda put-function-concurrency in the lab scripts.
  • The authoring guide points to an SQS trigger with ScalingConfig.MaximumConcurrency, or a documentation-only note when the question is about reserved concurrency itself.

Tests: 4 rule cases and a validator case.

@jhermesn jhermesn self-assigned this Nov 5, 2026
…fuse

A new account's Lambda limit is 10 and must stay unreserved, so labs that
reserved concurrency failed at deployment or in the reference solution.
@jhermesn
jhermesn force-pushed the fix/reserved-lambda-concurrency branch from 5216c59 to acb76d7 Compare November 5, 2026 18:45
@jhermesn
jhermesn merged commit d801159 into main Nov 5, 2026
1 check passed
@jhermesn
jhermesn deleted the fix/reserved-lambda-concurrency branch November 5, 2026 18:49
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