Skip to main content
All CollectionsTemplatesIntermediate
Request AWS Credentials Based on Jira Assignment (Britive) - Workflow Template
Request AWS Credentials Based on Jira Assignment (Britive) - Workflow Template

Receive a mention via Slack for Jira-Access with a Jira issue key. Provide access to the AWS account ID listed in the Jira issue via Slack.

Updated over a week ago

This workflow template enables automated access to AWS credentials through a request in Slack that references a Jira issue. Upon receiving a Slack mention for Jira access, the workflow verifies the Slack user's email against the Jira assignee, finds relevant Britive Profiles for the mentioned AWS account, and prompts the user for the required access profile. Access is granted through a temporary AWS console link provided in Slack, and credentials are monitored until the Jira issue is marked "Done", ensuring secure and efficient access management.

Trigger

Microsoft Teams Bot

Optional Triggers

"Microsoft Teams"

Use Cases

Identity and Access Management

Workflow Breakdown

  1. Receive a mention from Slack for Jira-Access

  2. Verify the Slack user email and Jira assignee matches

  3. Look for AWS account ID in the Jira issue and pull all Britive Profiles that match

  4. Ask user what profile is needed to resolve the issue

  5. Provide access to AWS via a console link via Slack

  6. Poll the Jira issue for up to 8 hours or until the Jira issue is marked "Done" then check the credentials back in.

Vendors

Slack, Utils, HTTP, Jira Cloud, Britive

Workflow Output

Access to AWS console via Slack or message on why checkout was unsuccessful

Tips

Use the nested workflow \"IAM - Nested Check-Out of AWS credentials via Britive (Britive)\" from the Torq Template Library

Did this answer your question?