JIT Guard provides temporary, audited AWS console access via Slack. It integrates with AWS IAM Identity Center to create ephemeral access groups — called elevations — that are automatically revoked when a timer expires. No stale credentials, no manual cleanup, no shared passwords.
Designed for incident response and emergency scenarios, JIT Guard lets authorised team members request access to any account in your AWS Organisation with a single /jit command in Slack. Access is time-bound (1–8 hours), fully logged, and removed automatically.
/jit in Slack, selects an account, picks a duration (1h, 2h, 4h, or 8h), and provides a reason.JIT Guard is a serverless SaaS running in the JIT Guard AWS account. Each customer deploys a lightweight CloudFormation stack in their own Identity Center management account that establishes a cross-account trust.
Follow these steps to connect your AWS organisation to JIT Guard. The process takes approximately 15 minutes.
Visit the JIT Guard signup page and create your account. You'll receive a customer ID and a role ARN for the CloudFormation stack.
In your Identity Center management account, deploy the JIT Guard CloudFormation stack using the provided template. The stack creates:
Use the AWS CLI or CloudFormation console to deploy. The only parameter is your JIT Guard customer ID.
Once the stack is deployed, return to the JIT Guard dashboard and click Connect. Enter your management account ID — JIT Guard discovers the rest (Identity Center instance, organisation structure, accounts) automatically.
On the dashboard, follow the Slack app installation link. You'll be prompted to authorise the JIT Guard bot with the necessary scopes for your workspace. Once installed, the bot is ready to handle /jit commands.
Type /jit in any Slack channel or DM with the JIT Guard bot. Select an account, choose a duration, add a reason, and you're elevated. You'll receive a DM confirmation with the expiry time.
/jit [account-id]Request elevation to an AWS account. Two modes:
/jit 123456789012 elevates you to the specified account for 1 hour immediately. Useful when you know the account ID./jit (no arguments) opens an interactive modal with account auto-complete, duration selection (1h, 2h, 4h, 8h), and a reason field.The JIT Guard web dashboard at https://app.jitguard.com provides:
JIT Guard maintains a synchronised copy of your AWS Organisation's accounts and organisational units (OUs) in DynamoDB. This powers the auto-complete in the Slack modal, so users can search accounts by name or ID.
The catalogue is kept up to date via EventBridge: when accounts are created, moved, renamed, or removed in your organisation, an event is forwarded to JIT Guard and the catalogue is updated within seconds.
JIT Guard offers three tiers of service. All plans include a 3-month free trial with no credit card required.
Billing is handled monthly via Stripe. You can view and manage your subscription at any time from the dashboard. Upgrade or downgrade at any time — upgrades take effect immediately with prorated billing.
jitguard- and include a random UUID. Groups are automatically deleted when the elevation expires. This prevents accumulation of stale access.Every elevation event is recorded as an immutable audit record in DynamoDB. Each record includes:
promote (access granted), demote (access expired), or failureAudit records are retained per your plan's retention policy (30 days for Starter, 90 days for Growth, custom for Enterprise). After the retention period, records are automatically purged via DynamoDB TTL.
Audit logs can be exported upon request — contact support for a data export.
JIT Guard supports configurable policies for elevation requests. Depending on your team's configuration:
If the modal closes but you never see a confirmation, check that the JIT Guard app's Messages tab is enabled: open the app's home (click the JIT Guard app in the sidebar), open the About tab, and re-enable Messages. Direct-message confirmations require it. Your active promotions always appear on the app's Home tab regardless.
Policies are configured per-customer and stored in your configuration record. Contact support to set up custom approval workflows for your team.
If you don't subscribe before the trial expires, elevation requests are blocked with a Slack DM explaining that your free trial has ended. You can subscribe at any time from the dashboard billing page — access resumes immediately.
Yes. Cancel from the Stripe Customer Portal in the dashboard. Access continues until the end of the current billing period. Your data is retained for 30 days after cancellation, then deleted.
JIT Guard uses IAM Identity Center permission sets. You define the permission set (e.g., AdministratorAccess, PowerUserAccess, or a custom scoped set) in your Identity Center console, and JIT Guard assigns it to the ephemeral group during elevation.
Yes. Approval requests are sent as Slack DMs with approve/deny buttons. The Slack mobile app works great for this — no separate dashboard required.
Identity Center can be enabled in any region. JIT Guard automatically probes common regions to discover your SSO instance. Organisation APIs are global (us-east-1). The JIT Guard service runs in eu-west-1 (Ireland).
Pricing is per-organisation, not per-user. Every member of your Slack workspace can request elevations. There are no per-user or per-elevation fees within your plan's account limit.
Ensure the JIT Guard Slack app is installed in your workspace and that you're typing the command in a channel where the bot is present, or in a DM with the bot.
Status updates and confirmation messages arrive in the app's Messages tab. If it's not there, open the JIT Guard app in Slack (search for it in the app launcher), go to App Home, and turn on the Messages tab.
The account catalogue syncs via EventBridge from your AWS Organisation. If no accounts appear, verify that the CloudFormation stack was deployed successfully and that your organisation has accounts. The sync runs on initial connection and then via event forwarding.
Verify that the JIT Guard IAM role in your account has the necessary permissions for Identity Center (create/delete groups, assign permission sets). The CloudFormation stack template includes the required policy — check that it wasn't modified.
This means JIT Guard can no longer assume the cross-account role. This can happen if the role was deleted, its trust policy was modified, or the management account ID changed. Re-deploy the CloudFormation stack or contact support.
Email support@jitguard.com for help with any issues. Enterprise customers receive a dedicated Slack support channel.