Reading the AWS Request ID

[harmenjanssen]

Hi,

I was wondering if it's possible to get at the original Lambda Request ID within your Laravel app?

I found the Context class which has a reference to the ID, but I'm unsure if that's accessible from within my Laravel app. (tried dependency-injecting it, but that was not the answer)

Thanks a lot in advance!

[tillkruss]

Yes:

laravel-bridge/config/bref.php

Line 31 in 2bff7e6

'request_context' => false,

[harmenjanssen]

Hmm, alright, I have to be more specific I guess: at this point I am not getting the X-Request-ID header in my requests.
I turned request_context on, but that doesn't give me any information about the AWS request.

I'm logging all headers coming in to my controller via the request, but it's not there.
Is there a way to get at the current context either in a controller, or middleware, or somewhere in that chain?

[MantasVaitkunas]

I am having the same problem. @harmenjanssen can you reopen the issue as ATM it's not clear how to use this config option :/

[tillkruss]

Does your request object not have the X-Request-ID header?

[harmenjanssen]

Does your request object not have the X-Request-ID header?

Nope, it does not.

[tillkruss]

Mhhh, turns out my apps aren't actually using this anymore. @georgeboot Do we have any way to access the AWS request id?

[georgeboot]

Afk atm, but there should be a $_SERVER var called HTTP_X_REQUEST_ID I believe

[MantasVaitkunas]

As @georgeboot said, I had a look into $_SERVER and found out that $_SERVER['LAMBDA_INVOCATION_CONTEXT'] has necessary info:

$requestId = null;
if (isset($_SERVER['LAMBDA_INVOCATION_CONTEXT'])) {
    $lambdaContext = json_decode($_SERVER['LAMBDA_INVOCATION_CONTEXT']);
    $requestId = $lambdaContext?->awsRequestId;
}

[tillkruss]

I feel like we should expose the invocation context a little better, maybe even attach some of the data to the Request object.