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
set stage in conf/dev.env to a new string. convention dev-
npm install
npm run sls:deploy-dev
4
set values in conf/dev.env for
COGNITO_POOL_ID=us-east-1_V2o1PH7j9
from the cognito deploy output
if not output in sls:deploy-dev output, then log in to AWS, go to cognito -> user pools to find it.
from this output, save requestLogin endpoint for nuxt env
from the cognito deploy output
if not output in sls:deploy-dev output, then log in to AWS, go to cognito -> user pools to find it.
set stage to same string as in cognito dev.env
npm install
npm run sls:deploy-dev
Two problems we ran into here.
(A) computer time. if your computer time isn't synced, it can cause errors when deploying
An error occurred: GraphQlApiKeyDefault - API key can be valid for a maximum of 365 days. (Service: AWSAppSync; Status Code: 400; Error Code: ApiKeyValidityOutOfBoundsException; Request ID: 567b9233-2619-4803-abc7-6c950a194644).
Somehow if your computer is in the future, then subsequent request happens outside the valid time window so the deploy fails.
(B) stage name gets prepended to function names. there's at least one function name that is 61 characters long, so we can only add 3 characters in the stage, otherwise we break the function name max length limit of 64 characters. #419
take this to the nuxt app
In conf/local.env, update the following:
AWS_REGION (probably the same)
APPSYNC_API_KEY
APPSYNC_ENDPOINT
(these 2 come from the output of sls:deploy-dev on appsync)
REQUEST_LOGIN_ENDPOINT
(this comes from the output of sls:deploy-dev on cognito (in back/users))
COGNITO_POOL_ID
COGNITO_IDENTITY_POOL_ID
COGNITO_POOL_WEB_CLIENT_ID
(these 3 are the same as the ones used in front/appsync/conf/dev.env)
No description provided.
The text was updated successfully, but these errors were encountered: