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

Make the AWS key not public (get a new key!) and use aws on the backend instead of in the client. #10

Open
trusktr opened this issue Aug 24, 2023 · 0 comments

Comments

@trusktr
Copy link
Contributor

trusktr commented Aug 24, 2023

We currently use AWS APIs on the client side, exposing our key on the client which means anyone can take it.

We need to

  • move AWS API usage to the backend
  • then make a new key that is not visible on the client (tedious process that involves multiple steps to wire up multiple AWS services before finally being able to get an Identity key for the setup)

First we want to complete

so that we're in control of dependencies and all of the code (instead of relying on AWS APIs being embedded into a client-side bundle).

@trusktr trusktr moved this to 🆕 New in General Board Sep 14, 2023
@trusktr trusktr moved this from 🆕 New to 📋 Backlog in General Board Sep 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant