You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: codegen/sdk/aws-models/ec2.json
+60-4Lines changed: 60 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -13158,6 +13158,36 @@
13158
13158
"smithy.api#documentation": "<p>Current state of options for customizable text banner that will be displayed on\n\t\t\tAmazon Web Services provided clients when a VPN session is established.</p>"
"smithy.api#documentation": "<p>Enable or disable the client route enforcement feature.</p>\n <p>Valid values: <code>true | false</code>\n </p>\n <p>Default value: <code>false</code>\n </p>"
13168
+
}
13169
+
}
13170
+
},
13171
+
"traits": {
13172
+
"smithy.api#documentation": "<p>Client route enforcement is a feature of the Client VPN service that helps enforce administrator defined routes on devices connected through the VPN. T\n\t\this feature helps improve your security posture by ensuring that network traffic originating from a connected client is not inadvertently sent outside the VPN tunnel.</p>\n <p>Client route enforcement works by monitoring the route table of a connected device for routing policy changes to the VPN connection. If the feature detects any VPN routing policy modifications, it will automatically force an update to the route table, \n\t\t\treverting it back to the expected route configurations.</p>"
"smithy.api#documentation": "<p>Status of the client route enforcement feature.</p>\n <p>Valid values: <code>true | false</code>\n </p>\n <p>Default value: <code>false</code>\n </p>",
13183
+
"smithy.api#xmlName": "enforced"
13184
+
}
13185
+
}
13186
+
},
13187
+
"traits": {
13188
+
"smithy.api#documentation": "<p>The current status of client route enforcement. The state will either be <code>true</code> (enabled) or <code>false</code> (disabled).</p>"
"smithy.api#documentation": "<p>Client route enforcement is a feature of the Client VPN service that helps enforce administrator defined routes on devices connected through the VPN. T\n\t\this feature helps improve your security posture by ensuring that network traffic originating from a connected client is not inadvertently sent outside the VPN tunnel.</p>\n <p>Client route enforcement works by monitoring the route table of a connected device for routing policy changes to the VPN connection. If the feature detects any VPN routing policy modifications, it will automatically force an update to the route table, \n\t\t\treverting it back to the expected route configurations.</p>",
"smithy.api#documentation": "<p>Options for enabling a customizable text banner that will be displayed on\n\t\t\tAmazon Web Services provided clients when a VPN session is established.</p>"
"smithy.api#documentation": "<p>Client route enforcement is a feature of the Client VPN service that helps enforce administrator defined routes on devices connected through the VPN. T\n\t\this feature helps improve your security posture by ensuring that network traffic originating from a connected client is not inadvertently sent outside the VPN tunnel.</p>\n <p>Client route enforcement works by monitoring the route table of a connected device for routing policy changes to the VPN connection. If the feature detects any VPN routing policy modifications, it will automatically force an update to the route table, \n\t\t\treverting it back to the expected route configurations.</p>"
"smithy.api#documentation": "<p>Describes the principals (service consumers) that are permitted to discover your VPC\n endpoint service.</p>",
45084
+
"smithy.api#documentation": "<p>Describes the principals (service consumers) that are permitted to discover your VPC\n endpoint service. Principal ARNs with path components aren't supported.</p>",
45041
45085
"smithy.api#paginated": {
45042
45086
"inputToken": "NextToken",
45043
45087
"outputToken": "NextToken",
@@ -80658,6 +80702,12 @@
80658
80702
"smithy.api#documentation": "<p>Options for enabling a customizable text banner that will be displayed on\n\t\t\tAmazon Web Services provided clients when a VPN session is established.</p>"
"smithy.api#documentation": "<p>Client route enforcement is a feature of the Client VPN service that helps enforce administrator defined routes on devices connected through the VPN. T\n\t\this feature helps improve your security posture by ensuring that network traffic originating from a connected client is not inadvertently sent outside the VPN tunnel.</p>\n <p>Client route enforcement works by monitoring the route table of a connected device for routing policy changes to the VPN connection. If the feature detects any VPN routing policy modifications, it will automatically force an update to the route table, \n\t\t\treverting it back to the expected route configurations.</p>"
"smithy.api#documentation": "<p>Modifies the permissions for your VPC endpoint service. You can add or remove permissions\n for service consumers (Amazon Web Services accounts, users, and IAM roles) to connect to\n your endpoint service.</p>\n <p>If you grant permissions to all principals, the service is public. Any users who know the name of a\n\t public service can send a request to attach an endpoint. If the service does not require manual approval,\n\t attachments are automatically approved.</p>"
85734
+
"smithy.api#documentation": "<p>Modifies the permissions for your VPC endpoint service. You can add or remove permissions\n for service consumers (Amazon Web Services accounts, users, and IAM roles) to connect to\n your endpoint service. Principal ARNs with path components aren't supported.</p>\n <p>If you grant permissions to all principals, the service is public. Any users who know the name of a\n\t public service can send a request to attach an endpoint. If the service does not require manual approval,\n\t attachments are automatically approved.</p>"
"smithy.api#documentation": "<p>Indicates whether resource attachments are automatically associated with the defaultassociation route table.</p>",
109908
+
"smithy.api#documentation": "<p>Indicates whether resource attachments are automatically associated with the default\n association route table. Enabled by default. If <code>defaultRouteTableAssociation</code>\n is set to <code>enable</code>,\n Amazon Web Services Transit Gateway will create the default transit gateway route\n table.</p>",
"smithy.api#documentation": "<p>Indicates whether resource attachments automatically propagate routes to the defaultpropagation route table.</p>",
109924
+
"smithy.api#documentation": "<p>Indicates whether resource attachments automatically propagate routes to the default\n propagation route table. Enabled by default. If <code>defaultRouteTablePropagation</code>\n is set to <code>enable</code>,\n Amazon Web Services Transit Gateway will create the default transit gateway route\n table.</p>",
Copy file name to clipboardExpand all lines: codegen/sdk/aws-models/entityresolution.json
+23-5Lines changed: 23 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -2569,7 +2569,7 @@
2569
2569
}
2570
2570
],
2571
2571
"traits": {
2572
-
"smithy.api#documentation": "<p>Returns the corresponding Match ID of a customer record if the record has been\nprocessed in a\nrule-based matching workflow or ML matching workflow.</p>\n <p>You can call this API as a dry run of an incremental load on the rule-based\n matching\n workflow.</p>",
2572
+
"smithy.api#documentation": "<p>Returns the corresponding Match ID of a customer record if the record has been processed\n in arule-based matching workflow or ML matching workflow.</p>\n <p>You can call this API as a dry run of an incremental load on the rule-based matching\n workflow.</p>",
"smithy.api#documentation": "<p>The type of the attribute, selected from a list of values.</p>\n <note>\n <p>Normalization is only supported for <code>NAME</code>, <code>ADDRESS</code>,\n <code>PHONE</code>, and <code>EMAIL_ADDRESS</code>. </p>\n <p>If you want to normalize <code>NAME_FIRST</code>, <code>NAME_MIDDLE</code>, and\n <code>NAME_LAST</code>, you must group them by assigning them to the\n <code>NAME</code>\n <code>groupName</code>. </p>\n <p>If you want to normalize <code>ADDRESS_STREET1</code>, <code>ADDRESS_STREET2</code>,\n <code>ADDRESS_STREET3</code>, <code>ADDRESS_CITY</code>, <code>ADDRESS_STATE</code>,\n <code>ADDRESS_COUNTRY</code>, and <code>ADDRESS_POSTALCODE</code>, you must group\n them by assigning them to the <code>ADDRESS</code>\n <code>groupName</code>. </p>\n <p>If you want to normalize <code>PHONE_NUMBER</code> and\n <code>PHONE_COUNTRYCODE</code>, you must group them by assigning them to the\n <code>PHONE</code>\n <code>groupName</code>. </p>\n </note>",
5607
+
"smithy.api#documentation": "<p>The type of the attribute, selected from a list of values.</p>\n <p>LiveRamp supports: <code>NAME</code> | <code>NAME_FIRST</code> |\n <code>NAME_MIDDLE</code> | <code>NAME_LAST</code> | <code>ADDRESS</code> |\n <code>ADDRESS_STREET1</code> | <code>ADDRESS_STREET2</code> |\n <code>ADDRESS_STREET3</code> | <code>ADDRESS_CITY</code> | <code>ADDRESS_STATE</code> |\n <code>ADDRESS_COUNTRY</code> | <code>ADDRESS_POSTALCODE</code> | <code>PHONE</code> |\n <code>PHONE_NUMBER</code> | <code>EMAIL_ADDRESS</code> | <code>UNIQUE_ID</code> |\n <code>PROVIDER_ID</code>\n </p>\n <p>TransUnion supports: <code>NAME</code> | <code>NAME_FIRST</code> |\n <code>NAME_LAST</code> | <code>ADDRESS</code> | <code>ADDRESS_CITY</code> |\n <code>ADDRESS_STATE</code> | <code>ADDRESS_COUNTRY</code> |\n <code>ADDRESS_POSTALCODE</code> | <code>PHONE_NUMBER</code> | <code>EMAIL_ADDRESS</code>\n | <code>UNIQUE_ID</code> | <code>IPV4</code> | <code>IPV6</code> | <code>MAID</code>\n </p>\n <p>Unified ID 2.0 supports: <code>PHONE_NUMBER</code> | <code>EMAIL_ADDRESS</code> |\n <code>UNIQUE_ID</code>\n </p>\n <note>\n <p>Normalization is only supported for <code>NAME</code>, <code>ADDRESS</code>,\n <code>PHONE</code>, and <code>EMAIL_ADDRESS</code>. </p>\n <p>If you want to normalize <code>NAME_FIRST</code>, <code>NAME_MIDDLE</code>, and\n <code>NAME_LAST</code>, you must group them by assigning them to the\n <code>NAME</code>\n <code>groupName</code>. </p>\n <p>If you want to normalize <code>ADDRESS_STREET1</code>, <code>ADDRESS_STREET2</code>,\n <code>ADDRESS_STREET3</code>, <code>ADDRESS_CITY</code>, <code>ADDRESS_STATE</code>,\n <code>ADDRESS_COUNTRY</code>, and <code>ADDRESS_POSTALCODE</code>, you must group\n them by assigning them to the <code>ADDRESS</code>\n <code>groupName</code>. </p>\n <p>If you want to normalize <code>PHONE_NUMBER</code> and\n <code>PHONE_COUNTRYCODE</code>, you must group them by assigning them to the\n <code>PHONE</code>\n <code>groupName</code>. </p>\n </note>",
"smithy.api#documentation": "<p>A string that instructs Entity Resolution to combine several columns into a unified\n column with the identical attribute type. </p>\n <p>For example, when working with columns such as\n<code>NAME_FIRST</code>,\n <code>NAME_MIDDLE</code>,\nand\n<code>NAME_LAST</code>,\nassigning them a common <code>groupName</code> will prompt Entity Resolution to concatenate\nthem into a single value.</p>"
5614
+
"smithy.api#documentation": "<p>A string that instructs Entity Resolution to combine several columns into a unified\n column with the identical attribute type. </p>\n <p>For example, when working with columns such as<code>NAME_FIRST</code>,\n <code>NAME_MIDDLE</code>,and<code>NAME_LAST</code>, assigning them a common\n<code>groupName</code> will prompt Entity Resolution to concatenate them into a single\n value.</p>"
5597
5615
}
5598
5616
},
5599
5617
"matchKey": {
@@ -5616,7 +5634,7 @@
5616
5634
}
5617
5635
},
5618
5636
"traits": {
5619
-
"smithy.api#documentation": "<p>A\nconfiguration object for defining input data fields in Entity Resolution. The\n SchemaInputAttribute specifies how individual fields in your input data should be processed\n and matched.</p>"
5637
+
"smithy.api#documentation": "<p>Aconfiguration object for defining input data fields in Entity Resolution. The\n <code>SchemaInputAttribute</code> specifies how individual fields in your input data\nshould be processed and matched.</p>"
0 commit comments