@@ -269,9 +269,7 @@ Trait value
269
269
- Description
270
270
* - endpointPatternType
271
271
- ``string ``
272
- - **Required ** The pattern type to use for the partition endpoint. This value can be set to ``service_dnsSuffix `` to
273
- use the ``https://{service}.{dnsSuffix} `` pattern or ``service_region_dnsSuffix `` to use
274
- ``https://{service}.{region}.{dnsSuffix} ``.
272
+ - **Required ** The pattern type to use for the partition endpoint. This value should be set to ``aws_recommended `` in almost all cases.
275
273
* - partitionEndpointSpecialCases
276
274
- ``map `` of partition to `PartitionEndpointSpecialCase object `_
277
275
- A map of partition to partition endpoint special cases - partitions that do not follow the
@@ -282,13 +280,9 @@ Conflicts with
282
280
:ref: `aws.endpoints#standardRegionalEndpoints-trait `
283
281
284
282
Partitional services (also known as "global" services) resolve a single endpoint per partition.
285
- That single endpoint is located in the partition's ``defaultGlobalRegion ``. Partitional
286
- services should follow one of two standard patterns:
283
+ That single endpoint is located in the partition's ``defaultGlobalRegion ``.
287
284
288
- - ``service_dnsSuffix ``: ``https://{service}.{dnsSuffix} ``
289
- - ``service_region_dnsSuffix ``: ``https://{service}.{region}.{dnsSuffix} ``
290
-
291
- The following example defines a partitional service that uses ``{service}.{dnsSuffix} ``:
285
+ The following example defines a partitional service that uses AWS recommended patterns for each partition:
292
286
293
287
.. code-block :: smithy
294
288
@@ -298,19 +292,19 @@ The following example defines a partitional service that uses ``{service}.{dnsSu
298
292
299
293
use aws.endpoints#standardPartitionalEndpoints
300
294
301
- @standardPartitionalEndpoints(endpointPatternType: "service_dnsSuffix ")
295
+ @standardPartitionalEndpoints(endpointPatternType: "aws_recommended ")
302
296
service MyService {
303
297
version: "2020-04-02"
304
298
}
305
299
306
- Services should follow the standard patterns; however, occasionally there are special cases.
300
+ Services should follow the standard patterns set by the DNS naming guidelines ; however, occasionally there are special cases.
307
301
The following example defines a partitional service that uses a special case pattern in
308
302
the ``aws `` partition and uses a non-standard global region in the ``aws-cn `` partition:
309
303
310
304
.. code-block :: smithy
311
305
312
306
@standardPartitionalEndpoints(
313
- endpointPatternType: "service_dnsSuffix ",
307
+ endpointPatternType: "aws_recommended ",
314
308
partitionEndpointSpecialCases: {
315
309
aws: [{endpoint: "https://myservice.global.amazonaws.com"}],
316
310
aws-cn: [{region: "cn-north-1"}]
0 commit comments