Tutorial Launch Saleable Streamlit dashboards @ AWS — part 0

M. the German Engineer
2 min readDec 9, 2021

--

Hello folk,
the combination of Streamlit is your big chance to run your start up as data scientist and sale dashboards and forecasts for small sized companys. I run a data science company at side hustle in Germany and created individual dashboards and forecasts for example for a backery — to improve their capacity planing. And the best: you will earn every month a constant amount of money without much work!

What you get after all parts?

You get here a complete step by step solution with final a professional launched dashboard, modern user authentication and data storage solution with minimal costs per month and maximal usability for our customers.

Why this tutorial series?

So you find many tutorials of the possibilites of Streamlit and launching at Heroku — but here the launched app is public which isn’t an option for sensible data of a customer! The same for Prophet: a lot of tutorials but nothing launched in the needs for customers.

As I know this is the first complete tutorial based on a streamlit app for hosting at AWS.
Overview of the tutorial parts:
- introduction of this tutorial (part 0)
- using a file in streamlit saved in AWS and upload a new one (part 1)
- make a docker container and uploading to AWS ECS (part 2)
- launching this container as a fargate service (part 3)
- connecting the service to your Route53 hosted zone (part 4)
- integrating authentication with Cognito (part 5)
- bonus session: using the streamlit upload button for saving files at AWS S3 — after 100 claps
- bonus session: integrate prophet in streamlit and host it — after 200 claps

What I want from you?

Read this tutorial, comment it, follow me and share it — everywhere!
In the moment I’m writing so follow me to miss nothing!

What’s next? — start with part 1

--

--

M. the German Engineer
M. the German Engineer

Written by M. the German Engineer

Mechanical engineer, Future worker, Data scientist, Project manager, Systems engineer

Responses (1)