Telemetry Api: add required header Lambda-Extension-Identifier

doc_source/runtimes-extensions-api.md

@@ -4,7 +4,7 @@ Lambda function authors use extensions to integrate Lambda with their preferred
 
 ![\[\]](http://docs.aws.amazon.com/lambda/latest/dg/images/telemetry-api-concept-diagram.png)
 
-As an extension author, you can use the Lambda Extensions API to integrate deeply into the Lambda [execution environment](lambda-runtime-environment.md)\. Your extension can register for function and execution environment lifecycle events\. In response to these events, you can start new processes, run logic, and control and participate in all phases of the Lambda lifecycle: initialization, invocation, and shutdown\. In addition, you can use the [Runtime Logs API](runtimes-logs-api.md) to receive a stream of logs\.
+As an extension author, you can use the Lambda Extensions API to integrate deeply into the Lambda [execution environment](lambda-runtime-environment.md)\. Your extension can register for function and execution environment lifecycle events\. In response to these events, you can start new processes, run logic, and control and participate in all phases of the Lambda lifecycle: initialization, invocation, and shutdown\. In addition, you can use the [Runtime Telemetry API](telemetry-api.md) to receive a stream of logs\.
 
 An extension runs as an independent process in the execution environment and can continue to run after the function invocation is fully processed\. Because extensions run as processes, you can write them in a different language than the function\. We recommend that you implement extensions using a compiled language\. In this case, the extension is a self\-contained binary that is compatible with supported runtimes\. All [Lambda runtimes](lambda-runtimes.md) support extensions\. If you use a non\-compiled language, ensure that you include a compatible runtime in the extension\. 
 
@@ -377,4 +377,4 @@ The following example shows a Lambda function error message in which the functio
 + 403 – Forbidden
 + 500 – Container error\. Non\-recoverable state\. Extension should exit promptly\.
 
-
+

doc_source/telemetry-api-reference.md

@@ -19,6 +19,7 @@ To subscribe to a telemetry stream, a Lambda extension can send a Subscribe API
 + **Method** – `PUT`
 + **Headers**
   + `Content-Type`: `application/json`
+  + `Lambda-Extension-Identifier`: the `Lambda-Extension-Identifier` value received upon registering your extension\.
 + **Request body parameters**
   + **schemaVersion**
     + Required: Yes
@@ -123,4 +124,4 @@ Here are some additional response codes that the extension can receive:
 + 200 – Request completed successfully
 + 202 – Request accepted\. Subscription request response in local testing environment
 + 400 – Bad request
-+ 500 – Service error
++ 500 – Service error