parse apiKey from url parameters from a HTTP GET request

basically I want to lock my chalice endpoints behind an api token.

right now I am thinking of using dyanmodb to create an association between a user document and its appropriate apikeys document.

then the user will be able to send https://myapi.com/apikey/fj0sd7f/analyze/asdf.com

instead of having to fire up Postman client or using cURL or wget. target audience doesnt have these.

Start by reviewing Chalice's HTTP GET endpoint handling and the AWS API Gateway context for the requested URL form. Clarify how API tokens should be associated with users and validated, including the proposed DynamoDB association, then define security and test requirements for accepting an apiKey in the path.

Written by the indexing model from the issue text.