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
@torimcd With the changes from #26 and #31 the entire hydrocron package (which includes the load data script) is now being built into a lambda container image. This should help take care a lot of the deployment concerns so that this ticket should become much easier to implement.
What needs to happen is:
Create an entrypoint for lambda. Most examples use lambda_handler as the function name but it can be whatever. This function takes the lambda event as input (JSON). The function needs to parse the lambda event to extract the parameters (instead of relying on CLI argparse). All the other code you have should be ok.
Define a new lambda function in terraform. You can use the timeseries lambda as an example, but make sure to use the dynamo-write-policy I prepared instead of the dynamo-read-policy (which means you'll also probably want to define a new execution role specifically for the load data lambda too). You'll also have to update the command part to point to the new lambda handler function.
Update the documentation for operations so they know how to invoke the lambda. It's probably best to just assume access to the AWS console and invoking the lambda that way. If you want to get fancy you could come up with an example using a AWS CLI command to execute the lambda
In order to run the database load script in AWS environment, it should be wrapped in a lambda instead of a command line tool.
The text was updated successfully, but these errors were encountered: