Skip to content

1. Configure Single Tenant

Important

If you chose false for CreateDnsEntries while creating the root stack, please create DNS entries manually or by means of your own Cloudformation stack before setting up single tenant

There are two options for installing the single tenant stack

  • Install the complete service - mlflow tracking, mlflow projects, mlflow models and the model registry
  • Install the service without compute capabilities, i.e. no mlflow projects

1.1. Single Tenant with Compute

In this step, an InfinStor account named 'root' will be created. Data Scientist users can be created and managed by this root user.

  • In your AWS Console, go to CloudFormation and choose create stack
  • Use Amazon S3 URL for template source. The URL is:
https://s3.amazonaws.com/infinstorcft/2.3.103/single-tenant.yaml

While specifying stack details, choose the following:

  • stack name - single-tenant in the example below
  • Parameter MlflowArtifactsBucketParameter: this bucket will be created and used for storage of all artifacts for all users
  • Parameter RootUserEmail: This is the email address of the root user

Be sure to tick the 'IAM Resources with Custom Names' checkbox while clicking through the Stack Options page.

1.2. Single Tenant without Compute

If you do not want to use the MLflow projects capability, i.e. the ability to run MLflow projects remotely, then you can perform the installation shown below. This setup results in the creation of an IAM role for the InfinStor service that does not have EC2 permissions

  • In your AWS Console, go to CloudFormation and choose create stack
  • Use Amazon S3 URL for template source. The URL is:
https://s3.amazonaws.com/infinstorcft/2.3.103/single-tenant-no-compute.yaml

While specifying stack details, choose the following:

  • stack name - single-tenant in the example below
  • Parameter RootUserEmail: This is the email address of the root user
  • Parameter MlflowArtifactsBucketParameter: this bucket will be created and used for storage of all artifacts for all users

General Options

  • MlflowArtifactsBucketParameter: Specify the default location where MLflow artifacts will be stored. Usually a s3 location. The destination for artifacts can be overridden at the time of experiment creation

  • Should the stack created by this CFT support the concept of Projects: The concept of Projects is a way to classify experiments and models into projects

  • EnableAuthorization: Should the MLflow implementation support authorization for experiments and models

Admin User Options

  • CreateRootUserInCognito: This CFT can optionally create a user named root in the Cognito's local database. This user is the administrator for this instance of the InfinStor service

  • RootUserEmail: If CreateRootUserInCongito is true, then this parameter should contain the email address of the root user

  • UseThisUserAsAdmin: As an alternative to creating a root user in Cognito, InfinStor can treat the specified user as admin. The account specified in this is usually a Non Person Account or a Service Account

Permissions Boundary Options

If your enterprise requires a permissions boundary to be applied to every IAM role created, you may specify that permissions boundary in this step. Choose false and enter the BoundaryPolicyARN

Be sure to tick the 'IAM Resources with Custom Names' checkbox while clicking through the Stack Options page.

1.2.1. Download Single SPA MLFlow UI Microfrontend

To access and locally install the Microfrontend (MFE) for MLFlow UI, based on Single SPA, follow the steps below

  • download https://<mlflowui subdomain>.<infinstor platform domain>/mlflowui-ss/static-files/mlflowui-ss.tar.gz
    • for example: https://mlflowui.infinstor.com/mlflowui-ss/static-files/mlflowui-ss.tar.gz
  • download https://<mlflowui subdomain>.<infinstor platform domain>/mlflowui-ss/static-files/serviceconfig.js
    • for example: https://mlflowui.infinstor.com/mlflowui-ss/static-files/serviceconfig.js
  • mkdir <document root of target web server>/static-files
    • under the document root of the target webserver, where the single spa build will be installed, create a directory static-files
  • cd <document root of target web server>/static-files
    • cd to the static-files directory created above
  • tar xvzf <path to downloaded mlflowui-ss.tar.gz>
    • extract the tar file contents inside <document root of target web server>/static-files directory
  • cp <path to downloaded serviceconfig.js> .
    • copy serviceconfig.js to <document root of target web server>/static-files directory
  • integrate MLFlow UI MFE with your Single SPA root application using bundle.js located in <document root of target web server>/static-files directory.