AWS integration
Pulls IAM identity and access data to automatically resolve access issues, enforce compliance, and manage user lifecycle in service tickets.
What it connects
- IAM users, groups, and roles with creation dates, policies, and permission boundaries
- Group memberships and policy attachments to understand access hierarchies and permission inheritance
- Access key metadata including age and creation date for compliance auditing
- User tags and organizational metadata for cost allocation and team attribution
What it automates
- Create or delete IAM users and groups directly from onboarding and offboarding tickets
- Add and remove users from groups to adjust team access and revoke permissions at scale
- Attach and detach policies to users, groups, or roles for just-in-time access provisioning and security hardening
- Rotate or deactivate access keys on expired credentials or in response to incident containment
In practice
A contractor's access needs to be revoked. STLabs pulls their current group memberships and policy attachments, then auto-removes them from all groups and deactivates access keys within a single offboarding ticket.
A new team member's onboarding ticket triggers STLabs to create their IAM user, add them to the correct team group, and attach the appropriate policy in one workflow, with audit logs linked to the ticket.
STLabs detects that access keys haven't been rotated in 90 days, opens a compliance ticket, and provides a one-click action to generate a new key pair and update the application configuration.
During a security incident. STLabs immediately deactivates the exposed access keys while documenting the containment action in the incident ticket, preserving the account for forensic investigation.
