You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This moves the LocalStack in job sam of .github/workflows/main.yml from a Docker container on the runner to a hosted LocalStack sandbox, managed by the LocalStack platform project lambda-sam-authorizer. Everything else in the job runs as before and still reaches LocalStack on localhost:4566.
What changes in .github/workflows/main.yml
Removes the LocalStack start command and its step
Starts LocalStack in a platform sandbox (every run)
Reads the sandbox's LocalStack log with lstk-project logs
Reports the run and releases the sandbox (if: always())
Nothing outside job sam changes. The steps between the # >>> localstack-platform and # <<< localstack-platform comments belong to the platform: "Update steps" on the project page refreshes them.
What you get
A fresh sandbox for every run (push, pull request, schedule)
On pull requests: an agent review with checks, IAM findings and the infrastructure diff, posted on the PR
On the default branch: the project's Cloud Pod and the baseline future PRs are diffed against
Before merging
LOCALSTACK_PLATFORM_AUTH_TOKEN repository secret: already in place. Pull requests from forks get no secrets, so the job fails on them.
LocalStack settings imported into the project: none
Not carried over:
LOCALSTACK_AUTH_TOKEN: the platform passes the project's token
The sandbox runs the platform's current LocalStack Pro.
To undo this later, use "Revert adoption" on the project page; it opens a PR that restores the job's own LocalStack startup and keeps your other edits.
Critical or High security findings on changed resources: 2
Tested the SAM application deployed in the LocalStack sandbox after updating the GitHub workflow to use platform sandboxes. Verified the API Gateway REST API and its custom Lambda authorizer by invoking endpoints with valid and invalid authorization tokens. Directly invoked both the backend Lambda and custom authorizer Lambda functions, and verified S3 bucket operations on the SAM CLI managed deployment bucket.
✅ passed · Run #9 · localstack/adopt-proj_b1e4056f → main @ 983acbc · vs latest main run
✨ This CI run indicates a redeployment of your SAM application. We see the old API Gateway bgczd7iun8, Lambda functions sam-app-MyFunction-5c8edc42 and sam-app-MyAuthFunction-be4c85c8, and their associated IAM roles sam-app-MyAuthFunctionRole-0c638d99 and sam-app-MyFunctionRole-bc7f603f have been removed. New versions of these resources, including API Gateway xrerdbgif5, Lambda functions sam-app-MyFunction-d72eb6b1 and sam-app-MyAuthFunction-c9b1c643, and IAM roles sam-app-MyAuthFunctionRole-6aabc72d and sam-app-MyFunctionRole-d0c033b1, have been created, along with a new S3 source bucket aws-sam-cli-managed-default-samclisourcebucket-ef4d9be1. This suggests a full update or recreation of the SAM application stack, likely due to code changes or configuration updates.
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
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.
This moves the LocalStack in job
samof.github/workflows/main.ymlfrom a Docker container on the runner to a hosted LocalStack sandbox, managed by the LocalStack platform project lambda-sam-authorizer. Everything else in the job runs as before and still reaches LocalStack onlocalhost:4566.What changes in
.github/workflows/main.ymllstk-project logsif: always())Nothing outside job
samchanges. The steps between the# >>> localstack-platformand# <<< localstack-platformcomments belong to the platform: "Update steps" on the project page refreshes them.What you get
Before merging
LOCALSTACK_PLATFORM_AUTH_TOKENrepository secret: already in place. Pull requests from forks get no secrets, so the job fails on them.LOCALSTACK_AUTH_TOKEN: the platform passes the project's tokenTo undo this later, use "Revert adoption" on the project page; it opens a PR that restores the job's own LocalStack startup and keeps your other edits.