Idira AWS Console with STS Connection Component – Example Configuration

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
PAM Self-Hosted Articles
5 min read
L0 Member
No ratings
This is just a sample configuration and Idira does not provide any official recommendation on how to configure your AWS environment. In addition, the steps provided in this Knowledge Article are subject to change and for the latest steps please reference CyberArk’s Official Documentation for this integration below: In this short step by step guide, we will see how Idira STS Plugin can be used to provide secure AWS console access to different group of privilege users. The STS plugin is one of the best options customers should leverage when managing access to AWS with Idira due to following reasons:
  • No need to create multiple user identity on AWS IAM
  • No credentials involved (Idira STS plugin involves the use of logon account)
  • Provide JIT access to any of the given privilege users which will be tied to the granular roles or have specific set of permissions

Steps

We have divided the entire configuration into 4 main stages.
  1. Configure the Pre-Requisites for the Idira STS Integration noted in our Idira Documentation:
    1. Prerequisites
    2. Install Internet Explorer
    3. Configure Applocker
  2. Creation and On-Boarding of the STS logon account
    1. Log into the AWS Console, go to AWS IAM Service, and then click on to add new user
      1. eid=ka3Vy000009MBb8&feoid=00N2J000009R3kv&refid=0EM2J000002kbnY.jpg
    2. Proceed without assigning any policy or permissions.
      1. eid=ka3Vy000009MBb8&feoid=00N2J000009R3kv&refid=0EM2J000002kbnd.jpg
    3. Click on create user and note the values of the following fields:
      1. User (You will specify this field)
      2. Access key ID
      3. Secret Access Key
      4. eid=ka3Vy000009MBb8&feoid=00N2J000009R3kv&refid=0EM2J000002kbni.jpg
    4. We will create new policy where we will assign enough permission to the AWSSTSLogonAccount to verify and rotate the access keys as per the Organization security policy.
    5. Go to IAM policies and click create Policy. We are restricting the following permissions only to our “AWSSTSLogonAccount” only via the “Resource:” section below. In addition, we are providing only the following 4 permissions what we require for the sample configuration:
      1. iam:DeleteAccessKey
      2. iam:GetAccessKeyLastUsed
      3. iam:CreateAccessKey
      4. iam:ListAccessKeys
      5. eid=ka3Vy000009MBb8&feoid=00N2J000009R3kv&refid=0EM2J000002kbnn.jpg
    6. Assign a policy name. In this configuration it is named “AWSTSLogonPolicy”
      1. eid=ka3Vy000009MBb8&feoid=00N2J000009R3kv&refid=0EM2J000002kbnx.jpg
    7. Assign the policy created in previous step to “AWSSTSLogonAccount”
      1. ​​​​​​​eid=ka3Vy000009MBb8&feoid=00N2J000009R3kv&refid=0EM2J000002kbo2.jpg
    8. All steps have been completed on the AWS side and now we will on-board the “AWSSTSLogonAccount” into Cyberark. We shall be on-boarding this account manually, but it can be on-boarded using automated functionalities of CyberArk.
    9. Login into Idira PVWA using the appropriate credentials who is authorized to on-board new accounts
    10. Go to Platform Management and duplicate the “Amazon Web Services-AWS-Access keys” platform under the Cloud Service section.
    11. In this example, the duplicate of the AWS-Access Keys platform was named “AWS-STS-Access-Logon Account”. If the duplicated platform is not enabled, please enable the duplicated platform.
      1. ​​​​​​​eid=ka3Vy000009MBb8&feoid=00N2J000009R3kv&refid=0EM2J000002kboC.jpg
    12. Create a new safe to store the “AWSSTSLogonAccount.” In this example, we created a safe called “AWSCloud Console STS account” and assigned the appropriate members.
    13. Onboard the “AWSSTSLogonAccount” to the “AWSCloud Console STS account” safe and enter parameters as shown below.
      1. ​​​​​​​eid=ka3Vy000009MBb8&feoid=00N2J000009R3kv&refid=0EM2J000002kboH.jpg
    14. Once the “AWSSTSLogonAccount” has been added, we will perform a password verification and change to verify CPM functionality with the account. Once the CPM testing is completed, then we will move to the next step.
      1. ​​​​​​​eid=ka3Vy000009MBb8&feoid=00N2J000009R3kv&refid=0EM2J000002kboM.jpg
  3. Creation of roles in AWS and assigning of those roles within CyberArk
    1. Create 2 different roles for the following AWS permissions:
      1. AmazonEC2FullAccess
      1. AmazonS3FullAccess
    1. Here are the steps on how to setup the “AWSEC2fullaccessSTS” role where any entity within your account can use this role.
      1. ​​​​​​​eid=ka3Vy000009MBb8&feoid=00N2J000009R3kv&refid=0EM2J000002kboR.jpg
      2. eid=ka3Vy000009MBb8&feoid=00N2J000009R3kv&refid=0EM2J000002kbog.jpg
      3. eid=ka3Vy000009MBb8&feoid=00N2J000009R3kv&refid=0EM2J000002kbol.jpg
    2. The screenshot below shows how the “AWSS3FullAccessSTS” role should be configured:
      1. ​​​​​​​eid=ka3Vy000009MBb8&feoid=00N2J000009R3kv&refid=0EM2J000002kbpK.jpg
    3. Once the roles have been created, then we will configure the policy applied to our  “AWSSTSLogonAccount” to be able to assume these 2 roles.We will ensure the permissions to assume the new roles will be granted to our “AWSSTSLogonAccount” via the “Resource” section below and will grant the following permissions to the user to assume the roles:
      1. sts:AssumeRole
      1. sts:GetFederationToken
      2. ka3Vy000009MBb8IAG__eid=ka3Vy000009MBb8&feoid=00N2J000009R3kv&refid=0EM2J000002kbpU.png
    1. The configuration has been completed on AWS side has now been completed. Now it’s the time to setup the appropriate configuration within CyberArk.
    2. Log into the Idira PVWA again and make sure that “Amazon Web Services-AWS” platform is enabled under the Cloud Service section.
    3. Idira Best Practice recommends creating a new safe to have better role-based access control for storing the AWS Role Accounts. However, in the configuration below we shall leverage the same safe we used before to store AWS STS Logon Account.
    4. Add the “AWSEC2fullaccessSTS” role account and then enter the parameters as mentioned below:
      1. ​​​​​​​eid=ka3Vy000009MBb8&feoid=00N2J000009R3kv&refid=0EM2J000002kbpZ.jpg
    5. Similarly add the “AWSS3fullaccessSTS” role account and then enter the parameters as mentioned below:
      1. ​​​​​​​eid=ka3Vy000009MBb8&feoid=00N2J000009R3kv&refid=0EM2J000002kbpj.jpg
  4. Authorized users with access to these credentials in Idira can click on the connect button for the given configured EC2FullAccess or S3FullAccess role account.
    1. You will see that there is no password configured because it is not required for the STS access with the role accounts
      1. ​​​​​​​eid=ka3Vy000009MBb8&feoid=00N2J000009R3kv&refid=0EM2J000002kbpy.jpg
    2. Once you click on connect button, then an RDP file will be downloaded to your workstation. The user will be able to access to the AWS Console via Idira jumphost when they open the RDP file. Below is an example of how the session will appear form within the RDP file:
      1. ​​​​​​​ka3Vy000009MBb8IAG__eid=ka3Vy000009MBb8&feoid=00N2J000009R3kv&refid=0EM2J000004SHCI.png​​​​​​​​​​​​​​
Rate this article: