AWS
Brainboard allows you to connect to your AWS environments, whether you want to provision resources, import existing infrastructure or simply manage your architecture on a daily basis.
It supports 2 authentication methods described below:
- Assume role (recommended) 
Configure access
To connect Brainboard to your AWS account:
- Go to the Cloud providers integration settings page. 
- Click on - Amazon Web Services
- Click on - New connection 
- This will open the new connection page where you have 2 options:  
Assume role
N.B: This is the recommended way to connect to your AWS accounts as it doesn't require any secret sharing.
When you click on the option Assume role Brainboard guides you in the connection process:
- In this page, click on - Create rolebutton, it will open your AWS account with pre-filled information 
- In your AWS portal, review the configuration and click next  
- Select the right permission to grant for this connection  
- Give the role a name, review and click on create role at the bottom  
- Copy the ARN of the role  
- Add the ARN in Brainboard credentials creation page  
- Brainboard checks if the connection can be established: - If the connection is successful, you will have this message  
- If it fails, you get an information about it  
 
- Name the connection in Brainboard  - This name is used only within Brainboard, so it's a best practice to give an explicit name that allows you to identify which account is referring to. 
Access key and secret
Brainboard allows you to add your access key, secret and session token if this is your preferred way to connect to your AWS environments:

You need to generate the the access key and secret from your AWS account first.
Set the scope
Once your credentials are added you can specify where exactly they will be used

This allows you to specify whether you want:
- Make the credentials the default to use within your organization: which means any architecture created in Brainboard will use these credentials if it doesn't have its own ones. 
- Use in a specific project 
- Use in a specific environment 
- Use in a specific architecture 

Last updated
Was this helpful?
