Skip to content
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

Closed
vuhuucuong opened this issue May 19, 2020 · 1 comment · Fixed by #1308, #1315 or #1322
Closed

Web Components Config Server should be deployed to AWS using serverless #1289

vuhuucuong opened this issue May 19, 2020 · 1 comment · Fixed by #1308, #1315 or #1322
Assignees
Labels
feature New feature or request front-end Relates to front end issues web-components-config-server

Comments

@vuhuucuong
Copy link
Contributor

vuhuucuong commented May 19, 2020

Background context or User story:
We haven't deployed the web-components-config-server to AWS yet.

Specification or Acceptance Criteria:

  • The web-components-config-server should be deployed to AWS lambda using serverless.
  • Must set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY as environment variables when bundling and deploying, because we're currently relying on these two to authenticate with DynamoDB (recommend to use those 2 keys from Github Secrets because they already existed in here).
  • The server will need to live behind another API Gateway later, but for now, just let serverless to create a new API Gateway by default
@vuhuucuong vuhuucuong added feature New feature or request web-components front-end Relates to front end issues needs-triage labels May 19, 2020
@vuhuucuong vuhuucuong self-assigned this May 20, 2020
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
@vuhuucuong
Copy link
Contributor Author

vuhuucuong commented May 26, 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment