Estimated time: 20-30 minutes for initial setup, then about 5 minutes per additional user.
Prerequisites
Before you begin, confirm you have:
Approval email from Kiro Startup Credits (check your inbox)
AWS Console access using the same email associated with the AWS Account
ID you provided in your application (you must be the account owner or have
admin access). It is important that you use the email and Account ID from
your original application to avoid any issues with credit activation or
access.
Active AWS account with no billing or MFA issues (verify you can sign into
the console without errors)
Active email addresses for all team members who will use Kiro
Your AWS account must be fully active and in good standing. If you have
unresolved MFA issues or your account shows as “suspended,” resolve those first
via AWS Support before proceeding.
Step 1: Enable IAM Identity Center
Loading image...
You must enable IAM Identity Center before doing anything else. This is the service that manages your team’s access to Kiro. The Kiro subscription cannot be activated without it.
Sign into the AWS Console using the email associated with your approved application.
In the search bar at the top, type “IAM Identity Center” and select it.
Click “Enable” to activate the service. Confirm by clicking “Enable” again.
When prompted, choose a region — a supported region where your workloads reside (e.g., us-east-1). Write this region down — you will need it later when signing into Kiro.
Save your region. You will need to select this exact region when signing into Kiro IDE later. If you choose the wrong region at sign-in, authentication will fail silently.
About AWS Organizations: IAM Identity Center may prompt you to enable AWS Organizations if it is not already active. This is normal. AWS Organizations is a prerequisite for IAM Identity Center to function. Accept the prompt and proceed. You do not need to configure Organizations further for Kiro setup.
Already using Okta or Microsoft Entra ID? If your startup already uses Okta or Microsoft Entra ID as an identity provider, you can connect it to Kiro directly instead of using IAM Identity Center’s built-in directory. This means you can skip Steps 2, 3, and 4 and manage users through your existing IdP. See the Kiro docs on connecting your identity provider for setup instructions.
Step 2: Create a group
Groups make it easy to manage Kiro access for multiple developers at once. In the IAM Identity Center sidebar, navigate to “Groups”:
Click “Create group”
Give your group a descriptive name (e.g., “Developers” or “Kiro Users”)
Click “Create group”
Step 3: Create users
Create a user for each team member who will use Kiro.
In the IAM Identity Center sidebar, navigate to “Users” and click “Add user”
Fill in: Username, Email address (must be active and accessible), First/Last name
Password options: Generate a one-time password OR send an email invitation
Add the user to your group from Step 2
Review and confirm. Repeat for each team member.
Step 4: Create your Kiro profile and subscribe users
This step happens in the AWS Console (browser), not in the Kiro IDE application.
Loading image...
In the AWS Console, search for “Kiro” and select it to open the Kiro console
Make sure you are in the same AWS Region where you set up IAM Identity Center in Step 1
Click “Sign up for Kiro,” then review the dialog and click “Enable.” This creates your Kiro profile, which connects your team’s identities to their Kiro subscriptions
(Optional) Edit your profile name or description in the Settings page
Navigate to the Users & Groups page
Choose the “Groups” tab and click “Add group”
Select a subscription tier. For Kiro Startup Credits, select Pro+ (2,000 credits per user per month)
Click “Continue,” then search for the group you created in Step 2 and click “Assign”
All members of that group are now subscribed.
Finding your sign-in URL: To find your sign-in URL for the next step, go back to IAM Identity Center in the AWS Console. On the dashboard or Settings page, look for the AWS access portal URL (it looks like https://d-xxxxxxxxxx.awsapps.com/start). Copy this URL and share it with your team — everyone will need it to sign into Kiro IDE.
About the “Pending” state: After subscribing, your subscription may briefly show as “Pending.” This usually resolves within a few minutes. If it persists for more than 15 minutes, try refreshing the page or signing out and back in.
Different views for different users: The Kiro console may display differently depending on your account role. The account owner or admin sees the subscription management view; other users may see a limited view. If you don’t see subscription options, confirm you are signed in as the account owner.
Step 5: Download Kiro IDE and sign in
Go to kiro.dev/downloads and download the Kiro IDE desktop app for your operating system (not the CLI or Kiro Crew).
Install and open the application
Complete the initial onboarding prompts
When asked how to sign in, select “Sign in with your organizational identity” (Do NOT use personal sign-in or “Create an account.”)
Paste the sign-in URL you copied in Step 4
Select the correct region (the same region you chose when enabling IAM Identity Center in Step 1)
Enter your username (the one your admin created in Step 3)
Enter the one-time password from Step 3 (if applicable), then set your permanent password
If prompted, set up MFA using an authenticator app (Google Authenticator, Microsoft Authenticator, Authy, or similar). Scan the QR code and enter the verification code to confirm
When asked to allow Kiro access, click “Allow”
Loading image...
After signing in, you should see your active plan and credit balance in the Kiro IDE. If you see “Free tier” or an individual plan, sign out and re-sign in using “organizational identity.”
Loading image...
Step 6: Verify your setup
Confirm everything is working:
In Kiro IDE: Check that you see your organization’s plan name and credit amount (not “Free tier” or an individual plan)
In the AWS Console: Go to Billing and Cost Management to verify Kiro charges appear under your service charges. Your credits will automatically offset Kiro usage.
Loading image...
Adding additional team members
When adding new developers to your Kiro subscription:
Cancel any existing individual Kiro accounts they may have. Otherwise, they will continue to be billed individually instead of using your startup credits.
Sign out completely from Kiro on all devices
Sign back in with organizational identity using the AWS access portal URL from Step 4 and the region from Step 1
Verify they see the organization’s plan and credits, not an individual account
Before you finish
Troubleshooting
Symptom
Fix
Sign-in fails silently
Wrong region selected. Re-enter the sign-in URL and select the region you chose in Step 1.
Subscription stuck on “Pending”
Wait 15 minutes, then refresh. If still pending, sign out and back in.
Console shows a different view
Confirm you’re signed in with the account owner email from your application.
“Failed to establish Kiro subscription”
Check AWS account status; resolve any billing or MFA issues.
One-time password not working
Use the temporary password generated in Step 3, not your AWS console password.
Free tier showing instead of credits
Sign out, then sign in using the “organizational identity” option.
After your Kiro Startup Credits application is approved, you need to:
Estimated time: 20-30 minutes for initial setup, then about 5 minutes per additional user.
Prerequisites
Before you begin, confirm you have:
AWS Console access using the same email associated with the AWS Account ID you provided in your application (you must be the account owner or have admin access). It is important that you use the email and Account ID from your original application to avoid any issues with credit activation or access.
Active AWS account with no billing or MFA issues (verify you can sign into the console without errors)
Your AWS account must be fully active and in good standing. If you have unresolved MFA issues or your account shows as “suspended,” resolve those first via AWS Support before proceeding.
Step 1: Enable IAM Identity Center
You must enable IAM Identity Center before doing anything else. This is the service that manages your team’s access to Kiro. The Kiro subscription cannot be activated without it.
us-east-1). Write this region down — you will need it later when signing into Kiro.About AWS Organizations: IAM Identity Center may prompt you to enable AWS Organizations if it is not already active. This is normal. AWS Organizations is a prerequisite for IAM Identity Center to function. Accept the prompt and proceed. You do not need to configure Organizations further for Kiro setup.
Already using Okta or Microsoft Entra ID? If your startup already uses Okta or Microsoft Entra ID as an identity provider, you can connect it to Kiro directly instead of using IAM Identity Center’s built-in directory. This means you can skip Steps 2, 3, and 4 and manage users through your existing IdP. See the Kiro docs on connecting your identity provider for setup instructions.
Step 2: Create a group
Groups make it easy to manage Kiro access for multiple developers at once. In the IAM Identity Center sidebar, navigate to “Groups”:
Step 3: Create users
Create a user for each team member who will use Kiro.
Step 4: Create your Kiro profile and subscribe users
This step happens in the AWS Console (browser), not in the Kiro IDE application.
Loading image...All members of that group are now subscribed.
Finding your sign-in URL: To find your sign-in URL for the next step, go back to IAM Identity Center in the AWS Console. On the dashboard or Settings page, look for the AWS access portal URL (it looks like
https://d-xxxxxxxxxx.awsapps.com/start). Copy this URL and share it with your team — everyone will need it to sign into Kiro IDE.About the “Pending” state: After subscribing, your subscription may briefly show as “Pending.” This usually resolves within a few minutes. If it persists for more than 15 minutes, try refreshing the page or signing out and back in.
Different views for different users: The Kiro console may display differently depending on your account role. The account owner or admin sees the subscription management view; other users may see a limited view. If you don’t see subscription options, confirm you are signed in as the account owner.
Step 5: Download Kiro IDE and sign in
Go to kiro.dev/downloads and download the Kiro IDE desktop app for your operating system (not the CLI or Kiro Crew).
- Install and open the application
- Complete the initial onboarding prompts
- When asked how to sign in, select “Sign in with your organizational identity” (Do NOT use personal sign-in or “Create an account.”)
- Paste the sign-in URL you copied in Step 4
- Select the correct region (the same region you chose when enabling IAM Identity Center in Step 1)
- Enter your username (the one your admin created in Step 3)
- Enter the one-time password from Step 3 (if applicable), then set your permanent password
- If prompted, set up MFA using an authenticator app (Google Authenticator, Microsoft Authenticator, Authy, or similar). Scan the QR code and enter the verification code to confirm
- When asked to allow Kiro access, click “Allow”
Loading image...After signing in, you should see your active plan and credit balance in the Kiro IDE. If you see “Free tier” or an individual plan, sign out and re-sign in using “organizational identity.”
Loading image...Step 6: Verify your setup
Confirm everything is working:
- In Kiro IDE: Check that you see your organization’s plan name and credit amount (not “Free tier” or an individual plan)
- In the AWS Console: Go to Billing and Cost Management to verify Kiro charges appear under your service charges. Your credits will automatically offset Kiro usage.
Loading image...Adding additional team members
When adding new developers to your Kiro subscription:
Before you finish
Troubleshooting
Quick reference
Other helpful links