-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Web Components Config Server should be deployed to AWS using serverless #1289
Labels
Milestone
Comments
vuhuucuong
added
feature
New feature or request
web-components
front-end
Relates to front end issues
needs-triage
labels
May 19, 2020
willmcvay
added
web-components-config-server
and removed
needs-triage
web-components
labels
May 19, 2020
vuhuucuong
pushed a commit
that referenced
this issue
May 21, 2020
14 tasks
vuhuucuong
pushed a commit
that referenced
this issue
May 21, 2020
vuhuucuong
pushed a commit
that referenced
this issue
May 21, 2020
vuhuucuong
pushed a commit
that referenced
this issue
May 22, 2020
vuhuucuong
pushed a commit
that referenced
this issue
May 22, 2020
vuhuucuong
pushed a commit
that referenced
this issue
May 22, 2020
vuhuucuong
pushed a commit
that referenced
this issue
May 22, 2020
14 tasks
vuhuucuong
pushed a commit
that referenced
this issue
May 22, 2020
vuhuucuong
pushed a commit
that referenced
this issue
May 22, 2020
vuhuucuong
pushed a commit
that referenced
this issue
May 22, 2020
vuhuucuong
pushed a commit
that referenced
this issue
May 22, 2020
14 tasks
vuhuucuong
pushed a commit
that referenced
this issue
May 25, 2020
FYI, the server has been deployed at https://vwvdddbw9k.execute-api.eu-west-2.amazonaws.com/dev |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Background context or User story:
We haven't deployed the
web-components-config-server
to AWS yet.Specification or Acceptance Criteria:
web-components-config-server
should be deployed to AWS lambda using serverless.AWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
as environment variables when bundling and deploying, because we're currently relying on these two to authenticate withDynamoDB
(recommend to use those 2 keys fromGithub Secrets
because they already existed in here).serverless
to create a new API Gateway by defaultThe text was updated successfully, but these errors were encountered: