Warming endpoints considers dynamo setup now #379
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
From this discussion it appears that the first connection to other services is slow due to ssl setup. For this reason I've added code that pings all of the dynamodb tables. This way, when we need something meaningful from the dynamodb, the connection will be ready to go.
Testing
For testing, I updated the warming endpoints cloudwatch rule with one of my past tokens. This way our connection to verify tokens is setup. In addition, I looked at the live logs to make sure the warming endpoint wasn't causing any errors. In addition to that, I uploaded to my dev lambda and ran the input from the cloudwatch event and I got a success result.