Authentication Using Roles
User-based authentication requires credential keys. If the credential key is not properly managed, it can cause security threat due to their sensitive nature.
Using the role-based authentication you can configure the AWS account using roles. The connector configuration accepts the role id (ARN) and assume that role to perform specific actions on the customer's account.
Role-based authentication reduces the risk of unauthorized access.
To access the Role-based authentication, follow these steps:
Procedure
| 1 |
Click the Role tab in the connector configuration page. |
||
| 2 |
Register the cluster. If the cluster is not registered, it displays a message "Cluster is not registered to use role credentials". Download the provided payload and contact a customer service representative.. |
||
| 3 |
From the notification message, click the download button and download the payload file. |
||
| 4 |
You can use the link in the notification message to contact the TAC team and raise the ticket and provide the file that you have downloaded. |
||
| 5 |
When the cluster is registered, the External Id and User ARN gets auto populated.
|
||
| 6 |
Use the generated External Id and User ARN to update the role trust relationship. It enables to assume the role. The same part of the JSON file:
|
||
| 7 |
When the previous step is complete, you can copy the Role ARN from the AWS account and paste it in the AWS connector configuration page. |
