IAM role assumption post spawn solutions

[droctothorpe]

Our users need to be able to toggle between multiple IAM roles from within their notebook containers.

I’m wondering if there are any open source solutions or recommended workflows for this pattern.

Pre-spawn is simple of course. One can just use the options form, but that is less flexible and doesn’t meet our requirements.

We have developed a solution that I have some reservations about but I’m wondering if it makes sense generalizing / open sourcing it, assuming something better doesn’t already exist and others could benefit from it.

[manics]

This discussion is about cloud provider identities in general rather than switching IAM roles, but might be of interest to you:

[Request for Implementation] Mapping notebook user identities to cloud provider identities

Many JupyterHub installations provide direct access to cloud resources like object storage (S3, GCS), cloud databases (RDS, Google Cloud SQL, etc) or bespoke cloud-provider specific things (BigQuery, Athena, Spanner, etc). Cloud providers have their own notion of identity (AWS IAM, Google’s Service accounts, etc), and access to cloud resources is granted on the basis of cloud provider identity. So, for access control & auditing purposes, it is important to attach a cloud provider identity to the…