You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if someone would be willing to share a docker-compose.yml example of authenticating the container endpoint service with AWS SSO (e.g. the creds that result from running the AWS CLI command, aws sso login). Based on other issues/PRs I've browsed in this repository (namely #51 and #52) it seems there are folks who have this working with the above but I couldn't find any examples.
I have it working temporarily by grabbing creds from the SSO start page and feeding those into the docker-compose.yml via a .env file (which sort of defeats half of this tool's purpose, and why I'm making this request). Since the latest image is over a year old, I was wondering if perhaps the latest AWS SSO features for the Go SDK have outpaced this project's support. Either way, thanks for your hard work on this tool--works great once authenticated.
The text was updated successfully, but these errors were encountered:
Hello all,
I was wondering if someone would be willing to share a docker-compose.yml example of authenticating the container endpoint service with AWS SSO (e.g. the creds that result from running the AWS CLI command,
aws sso login
). Based on other issues/PRs I've browsed in this repository (namely #51 and #52) it seems there are folks who have this working with the above but I couldn't find any examples.I have it working temporarily by grabbing creds from the SSO start page and feeding those into the docker-compose.yml via a .env file (which sort of defeats half of this tool's purpose, and why I'm making this request). Since the latest image is over a year old, I was wondering if perhaps the latest AWS SSO features for the Go SDK have outpaced this project's support. Either way, thanks for your hard work on this tool--works great once authenticated.
The text was updated successfully, but these errors were encountered: