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
{{ message }}
This repository has been archived by the owner on Jan 30, 2019. It is now read-only.
Right now we assume Soapbox is running in the same AWS account as the target deployments, but to be a pure SaaS/PaaS (to deploy into an existing customer's VPC, for example), we'll need to support a way to delegate auth to the user's AWS account.
A quick-and-dirty way would be to ask the user to supply a AWS credential key + secret pair, but AWS advises against this and recommends the use of Cognito, which appears to serve a similar function as OAuth.
The text was updated successfully, but these errors were encountered:
Right now we assume Soapbox is running in the same AWS account as the target deployments, but to be a pure SaaS/PaaS (to deploy into an existing customer's VPC, for example), we'll need to support a way to delegate auth to the user's AWS account.
A quick-and-dirty way would be to ask the user to supply a AWS credential key + secret pair, but AWS advises against this and recommends the use of Cognito, which appears to serve a similar function as OAuth.
The text was updated successfully, but these errors were encountered: