fix(cdk): grant lambda Put/DeleteProvisionedConcurrencyConfig (#409)#410
Open
isadeks wants to merge 2 commits into
Open
fix(cdk): grant lambda Put/DeleteProvisionedConcurrencyConfig (#409)#410isadeks wants to merge 2 commits into
isadeks wants to merge 2 commits into
Conversation
The Slack-events function pins provisioned concurrency on its `live` alias (AWS::Lambda::Alias with ProvisionedConcurrencyConfig), so CloudFormation issues lambda:PutProvisionedConcurrencyConfig at create. The Lambda statement in the bootstrap policy granted only lambda:GetProvisionedConcurrencyConfig, so a fresh `mise //cdk:bootstrap` + deploy of current main rolls back with: cdk-hnb659fds-cfn-exec-role is not authorized to perform lambda:PutProvisionedConcurrencyConfig Add Put/DeleteProvisionedConcurrencyConfig next to the existing Get verb (resource ARN function:backgroundagent-dev-* is already covered), regenerate bootstrap artifacts, update the DEPLOYMENT_ROLES.md golden (+ mirror), and add a regression guard. Fourth instance of bootstrap allow-list drift (after #403, #405, #408). Fixes #409
krokoko
previously approved these changes
Jun 23, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
krokoko
approved these changes
Jun 23, 2026
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
2 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
A fresh
mise //cdk:bootstrap+mise //cdk:deployof currentmainrolls back when CloudFormation configures provisioned concurrency on the Slack-events function'slivealias:Root cause:
SlackIntegrationSlackEventsFnAliasliveis anAWS::Lambda::Aliascarrying aProvisionedConcurrencyConfigproperty (confirmed via synth). Configuring it needslambda:PutProvisionedConcurrencyConfig(andDeleteon removal). TheLambdastatement incdk/src/bootstrap/policies/application.tsgranted onlylambda:GetProvisionedConcurrencyConfig. The resource ARN (function:backgroundagent-dev-*) is already covered — only the actions were missing.Same drift class as #402/#403, #404/#405, #407/#408.
Changes
lambda:PutProvisionedConcurrencyConfigandlambda:DeleteProvisionedConcurrencyConfignext to the existingGetverb in theLambdastatement.application.json,bootstrap-template.yaml).DEPLOYMENT_ROLES.mdgolden (+ Starlight mirror) for golden-baseline parity.policies.test.ts.Testing
mise //cdk:eslint— cleanmise //cdk:test— 2195 tests pass, incl. golden-baseline parity and the new guardapplication.json,bootstrap-template.yaml,DEPLOYMENT_ROLES.md, and the mirrorFixes #409