Skip to content

AWS IAM Role Chaining#

Introduction#

Using an EC2 instance profile enables your Hopsworks cluster to access AWS resources. This forces all Hopsworks users to share the instance profile role and the resource access policies attached to that role. To allow for per project access policies you could have your users use AWS credentials directly in their programs which is not recommended so you should instead use Role chaining. To use Role chaining, you need to first setup IAM roles in AWS:

Prerequisites#

Before you begin this guide you'll need the following:

  • A Hopsworks cluster running on EC2.
  • Administrator account on a Hopsworks cluster.

Step 1: Create an instance profile role#

Create an instance profile role with policies that will allow it to assume all resource roles that we can assume from the Hopsworks cluster.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AssumeDataRoles",
            "Effect": "Allow",
            "Action": "sts:AssumeRole",
            "Resource": [
                "arn:aws:iam::123456789011:role/test-role",
                "arn:aws:iam::xxxxxxxxxxxx:role/s3-role",
                "arn:aws:iam::xxxxxxxxxxxx:role/dev-s3-role",
                "arn:aws:iam::xxxxxxxxxxxx:role/redshift"
            ]
        }
    ]
}
Example policy for assuming four roles.

Step 2: Create the resource roles#

Create the resource roles and edit trust relationship and add policy document that will allow the instance profile to assume this role.

{
    "Version": "2012-10-17",
    "Statement": [
        {
        "Effect": "Allow",
        "Principal": {
            "AWS": "arn:aws:iam::xxxxxxxxxxxx:role/instance-profile"
        },
        "Action": "sts:AssumeRole"
        }
    ]
}
Example policy document.

Step 3: Create mappings#

Role chaining allows the instance profile to assume any role in the policy attached in step 1. To limit access to iam roles we can create a per-project mapping from the admin page in Hopsworks.

Role Chaining
Role Chaining

Click on your name in the top right corner of the navigation bar and choose Cluster Settings from the dropdown menu. In the Cluster Settings' IAM Role Chaining tab you can configure the mappings between projects and IAM roles. You can add mappings by entering the project name, which roles in that project can access the cloud role and the role ARN. Optionally you can set a role mapping as default by marking the default checkbox. The default roles can be changed from the project setting by a Data owner in that project.

Create Role Chaining
Create Role Chaining

Any member of a project can then go to the Project Settings -> Assuming IAM Roles page to see which roles they can assume.

Conclusion#

In this guide you learned how to map AWS IAM roles to project roles in Hopsworks.