- 最新
- 投票最多
- 评论最多
I am not sure why would you need the URL from within the function itself, but you can call the Lambda.get_function_url_config API to get the string you need.
The function URL domain and path are present as a part of the event object when the function is triggered from a function URL. You can see the event payload format here [1]. The function URL can be seen in full at event.requestContext.domainName, or just the UUID at event.requestContext.domainPrefix. You could also get it from event.headers.host.
[1] Invoking Lambda function URLs - Request payload format - https://docs.aws.amazon.com/lambda/latest/dg/urls-invocation.html#urls-request-payload
Yes, I know that these details are available from when triggered as a Function URL, however; that's too late for getting the domain or host details for me. I use the (same) AWS Lambda in 2 distinct ways:
- periodically triggered based on cron defined schedule as AWS Lambda. This may kick off an HTTP request to an external system to run some async background processing which will later send updates back to the AWS Lambda Function URL - thus I need to know the Function URL up front so the external system knows where to send updates to.
- triggered by incoming request as a Function URL. This will receive the external system generated update.
Yes I can hardcode the Function URL host in code but since the AWS Lambda can be "configured" with a Function URL, I would have expected that this configuration is available through some sort of generic "event" object or at least as part of the system environment.
In that case you would just need to use the API to retrieve it. You can grab the function ARN from the context object or the function name from environment variables and use that to call the GetFunctionUrlConfig API which will return all of the information related to your function URL. In Boto3 for example: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/lambda/client/get_function_url_config.html
相关内容
AWS 官方已更新 3 年前
As I mentioned in the above comment, the AWS Lambda is used with 2 events (periodic scheduled and Function URL request) and the periodic event need to send the Function URL endpoint to the external system, so the external system can send updates to the Function URL.
I'm accepting this as the answer since it allows me to gather the necessary details of a given AWS Lambda resource
I would probably create two functions. The first function is the one that is triggered on a schedule. The second function is the one withe function URL. The first function receives the function URL of the other function as an environment variable. You can create both functions in a single SAM template and there you can reference the URL in the env variables using something like 'Fn::GetAtt: HelloWorldFunctionUrl.FunctionUrl'.