https://kiro.dev/docs/getting-started/authentication/#aws-iam-identity-center
When opening new terminal (Ctrl + ñ), Kiro uses the default profile. For changing it:
Ctrl + , (or File > Preferences > Settings)
terminal.integrated.defaultProfile.windows
Default Profile: Ubuntu (WSL)
Workaround if the options does not appear to be configured:
Click F1 and write: Preferences: Open User Settings (JSON)
Search section "terminal.integrated.profiles.windows"
Ensure to have this code inside the main keys:
{
"terminal.integrated.profiles.windows": {
"Ubuntu (WSL)": {
"path": "C:\\Windows\\System32\\wsl.exe",
"args": [],
"icon": "terminal-linux"
}
},
"terminal.integrated.defaultProfile.windows": "Ubuntu (WSL)"
}
-
TBD
.gitignore
/.kiro/settings/
Creating the steering files using the Workspace Chat Panel (Recommended)
Open the Kiro Chat panel (Ctrl+Alt+I).
Copy and paste this exact prompt into the chat:
@Workspace Scan my current project and generate the complete contents for my Kiro steering files. Please provide the output broken down into three distinct markdown blocks so I can save them directly:
For product.md: Summarize what this application does, its core domain, and business context based on the repositories/code you see.
For structure.md: Map out our architectural layout, directory rules, and code style conventions found in this project.
For tech.md: Identify our technical stack, programming languages, framework versions, and any third-party infrastructure configurations (like AWS or database engines).
1. Direct Inline Changes
Since they are just standard Markdown files, the fastest way to keep them accurate is to edit them yourself during your normal development workflow.
If you change a database constraint or add a rule about how your io.awspring.cloud.sqs consumers should be structured, open tech.md and drop a new bullet point inside it.
2. The On-Demand Audit (Recommended)
Every few weeks, or after a major architectural shift (like upgrading a framework version or adding a new microservice module), you can explicitly ask Kiro to re-evaluate the repo and give you an update diff.
Prompt Example:
@Workspace Audit our codebase against the existing steering files in .kiro/steering/. Identify any new technologies, folder structures, or domain rules that have been introduced since these files were written, and provide the updated markdown blocks.
If after login from Kiro IDE, the "Accounts - Signed in with AWS Identity Center" shows error 'profileArn is required but could not be resolved', configure in the IDE the profileArn manually.
> How to find out the Profile ARN (by the AWS adminsitrator only)
IAM Identity Center > Applications > KiroProfile-eu-central-1
Application ARN (sample): arn:aws:sso::274374682827:application/ssoins-2704b50838cf3727/apl-270422d853ecee27
> In Kiro IDE, edit the file settings.json
Click F1 (or Ctrl + Shift + P) and write: Preferences: Open User Settings (JSON).
Locate line aws.amazonq.profileArn. If it does not exist, add it to the end (put a comma in the previous line). Should be like this:
{
...
"aws.amazonq.profileArn": "arn:aws:sso::274374682827:application/ssoins-2704b50838cf3727/apl-270422d853ecee27"
}
Save the file (Ctrl + S).
Restart the Kiro IDE. The "profileArn is required" should have disappeared.