This document explains how to onboard AWS applications to Britive.
Once you have configured the Britive Identity Provider and an IAM role for the AWS account, you can add the AWS application in Britive and proceed with the onboarding steps.
After onboarding, you can scan the required AWS organization or environments from Britive to get the details (such as permissions, groups, or accounts) associated with them. You can also check out and check in profiles from the onboarded AWS applications.
Onboarding an AWS Application: Steps and Functionality
The following diagram shows the basic steps in onboarding an AWS application to Britive and the functionality available to you after the onboarding process.
In Step 3 (in the preceding figure), you can choose to onboard an AWS application or an AWS standalone application depending on your requirement.
- An AWS application is onboarded when your AWS organization has the management AWS account(s) as well as member AWS accounts.
- If you want to onboard independent AWS accounts (standalone accounts) to Britive, you need to onboard an AWS standalone application. In other words, you should onboard an AWS standalone application when your AWS organization does not have a management AWS account and has only individual AWS accounts.
When you onboard an AWS standalone application, only scan environments functionality is applicable. Scanning organizations is not applicable as there is no concept of AWS organizations in AWS standalone applications.
The basic steps involved in onboarding an AWS application include:
- Onboarding Prerequisites (in AWS)
- Onboarding an AWS application (in Britive)
- Scanning Organizations and Environments (in Britive)
- Managing Britive Profiles for AWS