Add a LocalStack Power#145
Open
remotesynth wants to merge 10 commits into
Open
Conversation
1. It was using the wrong check to see if awslocal was installed 2. It was looking for the environment variable in bash when it is set in the config
The instructions were being misinterpreted by Kiro.
The env var is not the recommended method.
This isn't needed if the user uses the auth token options listed in the main power.md
This aims to solve a couple problems: 1. Kiro consistently tried to confirm the auth token via an env var set in bash 2. The existing Power didn't really utilize the MCP server, which could help simplify overall the usage
This commit includes the suggested changes sent to us from Brian Beach at AWS.
Kiro was ignoring the instructions to not attempt to validate the auth token via the terminal. This attempts to make that instruction more clear.
|
Hi @remotesynth, thank you for your contribution! Please note that if you haven't already, you would also need to submit your power officially at kiro.dev/powers/submit so it can be reviewed for listing in the Kiro powers registry. |
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
1 participant
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.
Description of changes:
This PR adds local testing with LocalStack support via a Kiro Power. It wires in the LocalStack MCP server which includes features for managing the LocalStack runtime, deploying infrastructure, running AWS API calls against the local endpoint, analyzing logs, enforcing IAM policies, injecting chaos faults, managing state and deploying ephemeral instances via structured tools.
The Power ships with a guided onboarding flow that validates prerequisites (Docker, LocalStack CLI, Node.js, awslocal), confirms auth token configuration for both MCP and the CLI, verifies MCP connectivity, and starts LocalStack. It also includes focused steering files for day-to-day development, IaC deployment, state management, MCP tool reference, and troubleshooting, so agents load only the context they need for a given task. The aim is to give Kiro users a safe, opinionated path from “set up LocalStack” to “deploy my stack, debug failures, and snapshot state".
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.