cnuss
Joined 5 years ago
Karma
77
Submissions
53
Member since
Apr 15
Recent submissions
Comment · 2 months ago
this is awesome. I have a ton of nostalgia towards making what is old new again, but still the unadulterated original. I hope you find Tim, Kieran, or Stoyanvoy!
Comment · 2 years ago
It's not publicly accessible, per-se..., there's a reverse proxy I've written
1. There's a Function URL that then creates a Lambda HTTP Event
2. There's a reverse proxy in the container that converts the Lambda HTTP Event back into a HTTP Request
3. Then the HTTP Respose is transformed back into a Lambda HTTP Event Response
@billconan if you'd like, join my Discord and I'd be happy dive into details and/or provide more docs: https://scaffoldly.dev/community
Comment · 2 years ago
Yup! Change the `handler` and `start` command:
``` handler = "localhost:5000" ... start = "poetry run flask --app flask_poetry run -p 12345" ```
Comment · 2 years ago
thanks don! here's the GH discussion on this topic: https://github.com/scaffoldly/scaffoldly/discussions/17
Comment · 4 years ago
thanks for the question!
this completely eliminates the need to juggle ~/.aws/* files, or downloading or generation of one or more web identity token files, or complicated trust to a single root account
using a single GitHub token identifying the user, the saml.to backend exchanges that token for the desired account and credentials simply based on providing the desired role name as input
zero knowledge on how to authenticate the aws cli is necessary, which I've found as a high friction point for administrators and developers to get right
let me know if you have any more questions or feedback!