Skip to content

Commit e5c0545

Browse files
authored
Merge pull request #108971 from TimShererWithAquent/us1679050ae
Change SSL to TLS per 1679050
2 parents b87780c + 8441b2d commit e5c0545

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

articles/cognitive-services/Speech-Service/speech-synthesis-markup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -594,7 +594,7 @@ The speech synthesis engine speaks the following example as "Your first request
594594

595595
Any audio included in the SSML document must meet these requirements:
596596

597-
* The MP3 must be hosted on an Internet-accessible HTTPS endpoint. HTTPS is required, and the domain hosting the MP3 file must present a valid, trusted SSL certificate.
597+
* The MP3 must be hosted on an Internet-accessible HTTPS endpoint. HTTPS is required, and the domain hosting the MP3 file must present a valid, trusted TLS/SSL certificate.
598598
* The MP3 must be a valid MP3 file (MPEG v2).
599599
* The bit rate must be 48 kbps.
600600
* The sample rate must be 16,000 Hz.

articles/cognitive-services/containers/includes/cognitive-services-container-security.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The diagram below illustrates the default and **non-secure** approach:
2222

2323
![Container security](../media/container-security.svg)
2424

25-
As an alternative and *secure* approach, consumers of Cognitive Services containers could augment a container with a front-facing component, keeping the container endpoint private. Let's consider a scenario where we use [Istio][istio] as an ingress gateway. Istio supports HTTPS/SSL and client-certificate authentication. In this scenario, the Istio frontend exposes the container access, presenting the client certificate that is whitelisted beforehand with Istio.
25+
As an alternative and *secure* approach, consumers of Cognitive Services containers could augment a container with a front-facing component, keeping the container endpoint private. Let's consider a scenario where we use [Istio][istio] as an ingress gateway. Istio supports HTTPS/TLS and client-certificate authentication. In this scenario, the Istio frontend exposes the container access, presenting the client certificate that is whitelisted beforehand with Istio.
2626

2727
[Nginx][nginx] is another popular choice in the same category. Both Istio and Nginx act as a service mesh and offer additional features including things like load-balancing, routing, and rate-control.
2828

0 commit comments

Comments
 (0)