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
I like the idea of the Lambda URL but it looks like each HTTPS request needs to be signed with "AWS Signature Version 4 (SigV4)". And as I was reading through the documentation I found the process to be a little confusing but maybe it is easy to use once we figure out?
Another option might be to invoke the granule with AWS CLI, like so:
FYI. We are very familiar with the CLI for HiTIDE Backfill Tool that gets deployed to our on-premise OPS machine and submits backfilling jobs for Forge/TIG/DMRPP to the Services OPS venue. Jim and Simon have incorporated several improvements for us in their CLI tool. That would be another option if the default AWS CLI command doesn't work.
Agree with @nikki-t that short term aws cli lambda invoke would be the preferred way to start the lambda programmatically. An ops CLI tool could be scoped out and developed as well.
I don't think we want to enable load data via URL because that gets into Authentication and Authorization concerns very quickly.
frankinspace
changed the title
Provide a way to load data via a URL
Provide a way to load data programmatically
Apr 3, 2024
Operators have requested the ability to invoke the load_data and load_granule lambda functions via an API call or curl. We may need to add support via something like this: https://docs.aws.amazon.com/lambda/latest/dg/lambda-urls.html
The text was updated successfully, but these errors were encountered: