When I try viewing the production site, I get the following error:

I have tried using my local code that works and commited to CodeCommit and also using Github. Any ideas/suggestions?

When I try running the application locally and click the log in button, the url in the browser has the following value:

http://localhost:8080/?error=access_denied&error_description=Service%20not%20found%3A%20https%3A%2F%2Fauth0-jwt-authorizer&state=Mm5Fdi1mVjNvdldwY1p0dGNNeU5tcDlPblJqOW14Mi1fNmVDV213YlljVA%3D%3D

=======================
Debug window has this info:

asyncToGenerator.js?1da1:6 Uncaught (in promise) {error: "access_denied", error_description: "Service not found: https://auth0-jwt-authorizer", state: "MU9sfkljVUlQVElVSmR6Q05KRzVQbjhDejBfYS1yamxnSjUyQ2gwYl80TQ=="}error: "access_denied"error_description: "Service not found: https://auth0-jwt-authorizer"state: "MU9sfkljVUlQVElVSmR6Q05KRzVQbjhDejBfYS1yamxnSjUyQ2gwYl80TQ=="proto: Object
asyncGeneratorStep @ asyncToGenerator.js?1da1:6
_throw @ asyncToGenerator.js?1da1:29
Promise.then (async)
asyncGeneratorStep @ asyncToGenerator.js?1da1:13
_next @ asyncToGenerator.js?1da1:25
eval @ asyncToGenerator.js?1da1:32
eval @ asyncToGenerator.js?1da1:21
updateResults @ HomeView.vue?409a:166
navigator.geolocation.getCurrentPosition.enableHighAccuracy @ HomeView.vue?409a:150
stream.js?553e:64 WebSocket connection to 'wss://no-credentials-available/' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED

Any thoughts / suggestions?

Thanks,

Bill

After logging in questions are not getting displayed.

Description:

I would like to kindly bring attention to a potential issue with the ProcessAnswersStreamFunction, which is invoked when incoming star rating answers or geo answers enter the DynamoDB through either ProcessAnswerStarFunction or ProcessAnswerGeoFunction. In the star.updateQuestionsTable and geo.updateQuestionsTable methods, the program uses the Dynamo’s ADD UpdateExpression to change the absolute count of star rating answers or geo answers. However, this implementation is not idempotent. Suppose when the function is invoked, the star rating of a specific answer is increased by 1; if the function crashes and retries, the star rating will be increased again by 1. This is not desired, as it duplicates the user's action (starring the answer) at untimely retries.

Suggested Fix:

To address this issue, please consider adding a LastRequestId field to the record that logs the most recent lambda's request id, and use a ConditionExpression along with the original ADD UpdateExpression. Specifically, only if context.aws_request_id != item.LastRequestId, apply the star rating change and update the LastRequestId field. This approach should help ensure idempotency and improve the reliability of the ProcessAnswersStreamFunction since the request id is constant across retries.

Thank you for considering this issue. I hope my suggestion proves helpful in enhancing the reliability and idempotency of the ProcessAnswersStreamFunction. Please don't hesitate to reach out if you have any questions or concerns.

There is no API Emdpoint value in the sam deploy output

Looks to be successful

Can't see anything in the aws dashboard either

Anyone advise where to look?