Add per-team permission sets for team ABAC#28
Merged
Conversation
When a team is provisioned, the Lambda now creates a permission set
(javabin-team-{name}) with:
- The developer permission boundary attached (guardrails)
- An inline policy allowing broad access scoped to team-tagged resources
- Assignment to the team's Identity Center group
Users sign in → see their team(s) in the portal → click one → get
ABAC-scoped access. The boundary controls what actions are allowed,
the inline policy controls which resources (by team tag).
Terraform PlanChanges detected — review required. Plan output |
LLM Plan ReviewRisk: 🟢 LOW Routine update to team provisioner Lambda function with expanded IAM permissions for SSO permission set management.
|
Alexanderamiri
added a commit
that referenced
this pull request
May 9, 2026
## Summary
Team provisioner now creates a `javabin-team-{name}` permission set per
team:
- Attaches `javabin-developer-boundary` (guardrails)
- Inline policy: `Allow *` scoped to `aws:ResourceTag/team =
{team_name}`
- Plus untagged read access for shared resources (list clusters, list
services, etc.)
- Assigned to the team's Identity Center group
## How it works
1. Team YAML merged → provisioner runs
2. Creates Identity Center group + syncs members (from YAML, matched
against SCIM users)
3. Creates `javabin-team-{name}` permission set with boundary + ABAC
policy
4. Assigns permission set to the group
5. User signs in at start URL → sees their team(s) → picks one → scoped
access
## IAM changes
Added `sso:CreatePermissionSet`, `sso:PutInlinePolicyToPermissionSet`,
`sso:AttachCustomerManagedPolicyReferenceToPermissionSet` to
team-provisioner Lambda role.
## Test plan
- [ ] CI passes
- [ ] After merge+apply, run team provisioner for platform-test-team
- [ ] Verify permission set created in Identity Center
- [ ] Sign in at start URL → see team entry → access is scoped
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.
Summary
Team provisioner now creates a
javabin-team-{name}permission set per team:javabin-developer-boundary(guardrails)Allow *scoped toaws:ResourceTag/team = {team_name}How it works
javabin-team-{name}permission set with boundary + ABAC policyIAM changes
Added
sso:CreatePermissionSet,sso:PutInlinePolicyToPermissionSet,sso:AttachCustomerManagedPolicyReferenceToPermissionSetto team-provisioner Lambda role.Test plan