Spawns JupyterHub single user notebook servers in Docker containers running in AWS Fargate
pip install fargatespawner
To configure JupyterHub to use FargateSpawner, you can add the following to your jupyterhub_config.py
.
from fargatespawner import FargateSpawner
c.JupyterHub.spawner_class = FargateSpawner
You must also set the following settings on c.FargateSpawner
in your jupyterhub_config.py
. None of them are optional.
Setting | Description | Example |
---|---|---|
aws_region |
The AWS region in which the tasks are launched. | 'eu-west-1' |
aws_ecs_host |
The hostname of the AWS ECS API. Typically, this is of the form ecs.<aws-region>.amazonaws.com . |
'ecs.eu-west-1.amazonaws.com' |
task_role_arn |
The role the notebook tasks can assume. For example, in order for them to make requests to AWS, such as to use Jupyter S3 with role-based authentication. | 'arn:aws:iam::123456789012:role/notebook-task' |
task_cluster_name |
The name of the ECS cluster in which the tasks are launched. | 'jupyerhub-notebooks' |
task_container_name |
The name of the container in the task definition. | 'jupyerhub-notebook' |
task_definition_arn |
The family and revision (family:revision) or full ARN of the task definition that runs the notebooks. Typically, this task definition would specify a docker image that builds on one of those from https://github.com/jupyter/docker-stacks. | 'jupyterhub-notebook:7' |
task_security_groups |
The security group(s) associated with the Fargate tasks. These must allow communication to and from the hub/proxy. More information, such as the ports used, is at https://jupyterhub.readthedocs.io/en/stable/getting-started/networking-basics.html. | ['sg-00026fc201a4e374b'] |
task_subnets |
The subnets associated with the Fargate tasks. | ['subnet-01fc5f15ac710c012'] |
notebook_port |
The port the notebook servers listen on. | 8888 |
notebook_scheme |
The scheme used by the hub and proxy to connect to the notebook servers. At the time of writing 'https' will not work out of the box. However, users do not connect to the the notebook server directly, and does not, typically, allow incoming connections from the public internet. Instead, users connect to the proxy, which can be configured to listen on HTTPS independently of this setting. There is more information on setting up HTTPS for connections to the proxy at https://jupyterhub.readthedocs.io/en/stable/getting-started/security-basics.html. |
'http' |
notebook_args |
Additional arguments to be passed to jupyterhub-singleuser that starts each notebook server. This can be the empty list. |
['--config=notebook_config.py'] |
Following settings are optional:
Setting | Description | Example |
---|---|---|
task_assign_public_ip |
Whether the task's elastic network interface receives a public IP address. | defaults to DISABLED |
task_platform_version |
The platform version the task should run. | defaults to LATEST |
You must also, either, authenticate using a secret key, in which case you must have the following configuration
from fargatespawner import FargateSpawnerSecretAccessKeyAuthentication
c.FargateSpawner.authentication_class = FargateSpawnerSecretAccessKeyAuthentication
and the following settings on c.FargateSpawnerSecretAccessKeyAuthentication
Setting | Description | Example |
---|---|---|
aws_access_key_id |
The ID of the AWS access key used to sign the requests to the AWS ECS API. | ommitted |
aws_secret_access_key |
The secret part of the AWS access key used to sign the requests to the AWS ECS API . | ommitted |
or authenticate using a role in an ECS container, in which case you must have the following configuration
from fargatespawner import FargateSpawnerECSRoleAuthentication
c.FargateSpawner.authentication_class = FargateSpawnerECSRoleAuthentication
where FargateSpawnerECSRoleAuthentication does not have configurable options.
or authenticate using a IAM profile attached to EC2 instance, in which case you must have the following configuration:
from fargatespawner import FargateSpawnerEC2InstanceProfileAuthentication
c.FargateSpawner.authentication_class = FargateSpawnerEC2InstanceProfileAuthentication
It's possible to override Task Definition based on the user input using spawner options form. This feature can be for example used to customize resources allocated to the task as you can see in the example jupyterhub_config.py
below.
from fargatespawner import FargateSpawner
class CustomFargateSpawner(FargateSpawner):
def _options_form_default(self):
return """
<div class="form-group">
<label for="resources">Choose suitable configuration for Notebook instance</label>
<select name="resources" size="4" class="form-control">
<option value="512_1024" selected>0.5 CPU & 1GB RAM</option>
<option value="1024_4096">1 CPU & 4GB RAM</option>
<option value="2048_16384">2 CPU & 16GB RAM</option>
<option value="4096_30720">4 CPU & 30GB RAM</option>
</select>
</div>
"""
def options_from_form(self, formdata):
options = {}
if formdata['resources']:
options['cpu'] = formdata['resources'][0].split("_")[0]
options['memory'] = formdata['resources'][0].split("_")[1]
return options
c.JupyterHub.spawner_class = CustomFargateSpawner
The spawner is deliberately written to not have any additional dependencies, beyond those that are required for JupyterHub.
In order for the user to be able to start, monitor, and stop the tasks, they should have the below permissions.
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "",
"Effect": "Allow",
"Action": "ecs:RunTask",
"Resource": "arn:aws:ecs:<aws_region>:<aws_account_id>:task-definition/<task_family>:*",
"Condition": {
"ArnEquals": {
"ecs:cluster": "arn:aws:ecs:<aws_region>:<aws_account_id>:cluster/<cluster_name>"
}
}
},
{
"Sid": "",
"Effect": "Allow",
"Action": "ecs:StopTask",
"Resource": "arn:aws:ecs:<aws_region>:<aws_account_id>:task/*",
"Condition": {
"ArnEquals": {
"ecs:cluster": "arn:aws:ecs:<aws_region>:<aws_account_id>:cluster/<cluster_name>"
}
}
},
{
"Sid": "",
"Effect": "Allow",
"Action": "ecs:DescribeTasks",
"Resource": "arn:aws:ecs:<aws_region>:<aws_account_id>:task/*",
"Condition": {
"ArnEquals": {
"ecs:cluster": "arn:aws:ecs:<aws_region>:<aws_account_id>:cluster/<cluster_name>"
}
}
},
{
"Sid": "",
"Effect": "Allow",
"Action": "iam:PassRole",
"Resource": [
"arn:aws:iam::<aws_account_id>:role/<task-execution-role>",
"arn:aws:iam::<aws_account_id>:role/<task-role>"
]
}
]
}