wu-sheng commented on code in PR #10416:
URL: https://github.com/apache/skywalking/pull/10416#discussion_r1111945149


##########
docs/en/setup/backend/aws-firehose-receiver.md:
##########
@@ -23,4 +23,4 @@ CloudWatch metrics with S3 -->  CloudWatch Metric Stream 
(OpenTelemetry formart)
 ## Notice
 
 1. Only OpenTelemetry format is supported (refer to [Metric streams output 
formats](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-metric-streams-formats.html))
-2. Only HTTPS could be accepted, you could directly enable TLS and set the 
receiver to listen 443, or put the receiver behind a gateway with HTTPS (refer 
to [Amazon Kinesis Data Firehose Delivery Stream HTTP Endpoint Delivery 
Specifications](https://docs.aws.amazon.com/firehose/latest/dev/httpdeliveryrequestresponse.html))
+2. It's required to put AWS Firehose receiver behind a proxy server(e.g. 
nginx, envoy, etc) to accept HTTPS requests from AWS Firehose through port 
`443` (refer to [Amazon Kinesis Data Firehose Delivery Stream HTTP Endpoint 
Delivery 
Specifications](https://docs.aws.amazon.com/firehose/latest/dev/httpdeliveryrequestresponse.html),
 [Why firehose receiver doesn't support 
TSL](https://github.com/apache/skywalking/pull/10409))

Review Comment:
   ```suggestion
   2. A proxy(e.g. Nginx, Envoy) is required in front of OAP's Firehose 
receiver to accept HTTPS requests from AWS Firehose through port `443` (refer 
to [Amazon Kinesis Data Firehose Delivery Stream HTTP Endpoint Delivery 
Specifications](https://docs.aws.amazon.com/firehose/latest/dev/httpdeliveryrequestresponse.html)。
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to