diff --git a/.changes/2.1079.0.json b/.changes/2.1079.0.json new file mode 100644 index 0000000000..deb02a045e --- /dev/null +++ b/.changes/2.1079.0.json @@ -0,0 +1,12 @@ +[ + { + "type": "feature", + "category": "AppRunner", + "description": "AWS App Runner adds a Java platform (Corretto 8, Corretto 11 runtimes) and a Node.js 14 runtime." + }, + { + "type": "feature", + "category": "Translate", + "description": "This release enables customers to use translation settings for formality customization in their synchronous translation output." + } +] \ No newline at end of file diff --git a/CHANGELOG.md b/CHANGELOG.md index e54a7e932a..5c79696ab2 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,7 +1,11 @@ # Changelog for AWS SDK for JavaScript - + +## 2.1079.0 +* feature: AppRunner: AWS App Runner adds a Java platform (Corretto 8, Corretto 11 runtimes) and a Node.js 14 runtime. +* feature: Translate: This release enables customers to use translation settings for formality customization in their synchronous translation output. + ## 2.1078.0 * feature: CustomerProfiles: This release introduces apis CreateIntegrationWorkflow, DeleteWorkflow, ListWorkflows, GetWorkflow and GetWorkflowSteps. These apis are used to manage and view integration workflows. * feature: DynamoDB: DynamoDB ExecuteStatement API now supports Limit as a request parameter to specify the maximum number of items to evaluate. If specified, the service will process up to the Limit and the results will include a LastEvaluatedKey value to continue the read in a subsequent operation. diff --git a/README.md b/README.md index ae710499ff..030fc5ca17 100644 --- a/README.md +++ b/README.md @@ -29,7 +29,7 @@ For release notes, see the [CHANGELOG](https://github.com/aws/aws-sdk-js/blob/ma To use the SDK in the browser, simply add the following script tag to your HTML pages: - + You can also build a custom browser SDK with your specified set of AWS services. This can allow you to reduce the SDK's size, specify different API versions of diff --git a/apis/apprunner-2020-05-15.normal.json b/apis/apprunner-2020-05-15.normal.json index 8ab80d1776..e431db5eb3 100644 --- a/apis/apprunner-2020-05-15.normal.json +++ b/apis/apprunner-2020-05-15.normal.json @@ -2041,7 +2041,10 @@ "type": "string", "enum": [ "PYTHON_3", - "NODEJS_12" + "NODEJS_12", + "NODEJS_14", + "CORRETTO_8", + "CORRETTO_11" ] }, "RuntimeEnvironmentVariables": { diff --git a/apis/translate-2017-07-01.min.json b/apis/translate-2017-07-01.min.json index 7ed43cbe01..cfd141180a 100644 --- a/apis/translate-2017-07-01.min.json +++ b/apis/translate-2017-07-01.min.json @@ -105,16 +105,16 @@ "type": "structure", "members": { "ParallelDataProperties": { - "shape": "S11" + "shape": "S12" }, "DataLocation": { - "shape": "S15" + "shape": "S16" }, "AuxiliaryDataLocation": { - "shape": "S15" + "shape": "S16" }, "LatestUpdateAttemptAuxiliaryDataLocation": { - "shape": "S15" + "shape": "S16" } } } @@ -134,13 +134,13 @@ "type": "structure", "members": { "TerminologyProperties": { - "shape": "S1a" + "shape": "S1b" }, "TerminologyDataLocation": { - "shape": "S1d" + "shape": "S1e" }, "AuxiliaryDataLocation": { - "shape": "S1d" + "shape": "S1e" } } } @@ -181,10 +181,10 @@ "type": "structure", "members": { "TerminologyProperties": { - "shape": "S1a" + "shape": "S1b" }, "AuxiliaryDataLocation": { - "shape": "S1d" + "shape": "S1e" } } } @@ -205,7 +205,7 @@ "ParallelDataPropertiesList": { "type": "list", "member": { - "shape": "S11" + "shape": "S12" } }, "NextToken": {} @@ -228,7 +228,7 @@ "TerminologyPropertiesList": { "type": "list", "member": { - "shape": "S1a" + "shape": "S1b" } }, "NextToken": {} @@ -529,10 +529,11 @@ "Sx": { "type": "structure", "members": { + "Formality": {}, "Profanity": {} } }, - "S11": { + "S12": { "type": "structure", "members": { "Name": {}, @@ -541,7 +542,7 @@ "Status": {}, "SourceLanguageCode": {}, "TargetLanguageCodes": { - "shape": "S13" + "shape": "S14" }, "ParallelDataConfig": { "shape": "S4" @@ -574,11 +575,11 @@ } } }, - "S13": { + "S14": { "type": "list", "member": {} }, - "S15": { + "S16": { "type": "structure", "required": [ "RepositoryType", @@ -589,7 +590,7 @@ "Location": {} } }, - "S1a": { + "S1b": { "type": "structure", "members": { "Name": {}, @@ -597,7 +598,7 @@ "Arn": {}, "SourceLanguageCode": {}, "TargetLanguageCodes": { - "shape": "S13" + "shape": "S14" }, "EncryptionKey": { "shape": "S7" @@ -622,7 +623,7 @@ "Format": {} } }, - "S1d": { + "S1e": { "type": "structure", "required": [ "RepositoryType", diff --git a/apis/translate-2017-07-01.normal.json b/apis/translate-2017-07-01.normal.json index f5dea7228c..4c36e1ad90 100644 --- a/apis/translate-2017-07-01.normal.json +++ b/apis/translate-2017-07-01.normal.json @@ -608,6 +608,13 @@ "KMS" ] }, + "Formality": { + "type": "string", + "enum": [ + "FORMAL", + "INFORMAL" + ] + }, "GetParallelDataRequest": { "type": "structure", "required": [ @@ -1486,6 +1493,9 @@ "TranslationSettings": { "type": "structure", "members": { + "Formality": { + "shape": "Formality" + }, "Profanity": { "shape": "Profanity", "documentation": "
Enable the profanity setting if you want Amazon Translate to mask profane words and phrases in your translation output.
To mask profane words and phrases, Amazon Translate replaces them with the grawlix string “?$#@$“. This 5-character sequence is used for each profane word or phrase, regardless of the length or number of words.
Amazon Translate does not detect profanity in all of its supported languages. For languages that support profanity detection, see Supported Languages and Language Codes in the Amazon Translate Developer Guide.
" diff --git a/apis/wafv2-2019-07-29.normal.json b/apis/wafv2-2019-07-29.normal.json index f447d9fca9..42cbadae4f 100644 --- a/apis/wafv2-2019-07-29.normal.json +++ b/apis/wafv2-2019-07-29.normal.json @@ -600,7 +600,7 @@ "shape": "WAFInvalidOperationException" } ], - "documentation": "Generates a presigned download URL for the specified release of the mobile SDK.
The mobile SDK is not generally available. Customers who have access to the mobile SDK can use it to establish and manage Security Token Service (STS) security tokens for use in HTTP(S) requests from a mobile device to WAF.
" + "documentation": "Generates a presigned download URL for the specified release of the mobile SDK.
The mobile SDK is not generally available. Customers who have access to the mobile SDK can use it to establish and manage Security Token Service (STS) security tokens for use in HTTP(S) requests from a mobile device to WAF. For more information, see WAF client application integration in the WAF Developer Guide.
" }, "GetIPSet": { "name": "GetIPSet", @@ -712,7 +712,7 @@ "shape": "WAFInvalidOperationException" } ], - "documentation": "Retrieves information for the specified mobile SDK release, including release notes and tags.
The mobile SDK is not generally available. Customers who have access to the mobile SDK can use it to establish and manage Security Token Service (STS) security tokens for use in HTTP(S) requests from a mobile device to WAF.
" + "documentation": "Retrieves information for the specified mobile SDK release, including release notes and tags.
The mobile SDK is not generally available. Customers who have access to the mobile SDK can use it to establish and manage Security Token Service (STS) security tokens for use in HTTP(S) requests from a mobile device to WAF. For more information, see WAF client application integration in the WAF Developer Guide.
" }, "GetPermissionPolicy": { "name": "GetPermissionPolicy", @@ -1055,7 +1055,7 @@ "shape": "WAFInvalidOperationException" } ], - "documentation": "Retrieves a list of the available releases for the mobile SDK and the specified device platform.
The mobile SDK is not generally available. Customers who have access to the mobile SDK can use it to establish and manage Security Token Service (STS) security tokens for use in HTTP(S) requests from a mobile device to WAF.
" + "documentation": "Retrieves a list of the available releases for the mobile SDK and the specified device platform.
The mobile SDK is not generally available. Customers who have access to the mobile SDK can use it to establish and manage Security Token Service (STS) security tokens for use in HTTP(S) requests from a mobile device to WAF. For more information, see WAF client application integration in the WAF Developer Guide.
" }, "ListRegexPatternSets": { "name": "ListRegexPatternSets", @@ -1232,7 +1232,7 @@ "shape": "WAFLogDestinationPermissionIssueException" } ], - "documentation": "Enables the specified LoggingConfiguration, to start logging from a web ACL, according to the configuration provided.
You can access information about all traffic that WAF inspects using the following steps:
Create your logging destination. You can use an Amazon CloudWatch Logs log group, an Amazon Simple Storage Service (Amazon S3) bucket, or an Amazon Kinesis Data Firehose. For information about configuring logging destinations and the permissions that are required for each, see Logging web ACL traffic information in the WAF Developer Guide.
Associate your logging destination to your web ACL using a PutLoggingConfiguration
request.
When you successfully enable logging using a PutLoggingConfiguration
request, WAF creates an additional role or policy that is required to write logs to the logging destination. For an Amazon CloudWatch Logs log group, WAF creates a resource policy on the log group. For an Amazon S3 bucket, WAF creates a bucket policy. For an Amazon Kinesis Data Firehose, WAF creates a service-linked role.
This operation completely replaces the mutable specifications that you already have for the logging configuration with the ones that you provide to this call. To modify the logging configuration, retrieve it by calling GetLoggingConfiguration, update the settings as needed, and then provide the complete logging configuration specification to this call.
Enables the specified LoggingConfiguration, to start logging from a web ACL, according to the configuration provided.
You can define one logging destination per web ACL.
You can access information about the traffic that WAF inspects using the following steps:
Create your logging destination. You can use an Amazon CloudWatch Logs log group, an Amazon Simple Storage Service (Amazon S3) bucket, or an Amazon Kinesis Data Firehose. For information about configuring logging destinations and the permissions that are required for each, see Logging web ACL traffic information in the WAF Developer Guide.
Associate your logging destination to your web ACL using a PutLoggingConfiguration
request.
When you successfully enable logging using a PutLoggingConfiguration
request, WAF creates an additional role or policy that is required to write logs to the logging destination. For an Amazon CloudWatch Logs log group, WAF creates a resource policy on the log group. For an Amazon S3 bucket, WAF creates a bucket policy. For an Amazon Kinesis Data Firehose, WAF creates a service-linked role.
For additional information about web ACL logging, see Logging web ACL traffic information in the WAF Developer Guide.
This operation completely replaces the mutable specifications that you already have for the logging configuration with the ones that you provide to this call. To modify the logging configuration, retrieve it by calling GetLoggingConfiguration, update the settings as needed, and then provide the complete logging configuration specification to this call.
Contains an array of strings that specify one or more IP addresses or blocks of IP addresses in Classless Inter-Domain Routing (CIDR) notation. WAF supports all IPv4 and IPv6 CIDR ranges except for /0.
Examples:
To configure WAF to allow, block, or count requests that originated from the IP address 192.0.2.44, specify 192.0.2.44/32
.
To configure WAF to allow, block, or count requests that originated from IP addresses from 192.0.2.0 to 192.0.2.255, specify 192.0.2.0/24
.
To configure WAF to allow, block, or count requests that originated from the IP address 1111:0000:0000:0000:0000:0000:0000:0111, specify 1111:0000:0000:0000:0000:0000:0000:0111/128
.
To configure WAF to allow, block, or count requests that originated from IP addresses 1111:0000:0000:0000:0000:0000:0000:0000 to 1111:0000:0000:0000:ffff:ffff:ffff:ffff, specify 1111:0000:0000:0000:0000:0000:0000:0000/64
.
For more information about CIDR notation, see the Wikipedia entry Classless Inter-Domain Routing.
" + "documentation": "Contains an array of strings that specifies zero or more IP addresses or blocks of IP addresses in Classless Inter-Domain Routing (CIDR) notation. WAF supports all IPv4 and IPv6 CIDR ranges except for /0.
Example address strings:
To configure WAF to allow, block, or count requests that originated from the IP address 192.0.2.44, specify 192.0.2.44/32
.
To configure WAF to allow, block, or count requests that originated from IP addresses from 192.0.2.0 to 192.0.2.255, specify 192.0.2.0/24
.
To configure WAF to allow, block, or count requests that originated from the IP address 1111:0000:0000:0000:0000:0000:0000:0111, specify 1111:0000:0000:0000:0000:0000:0000:0111/128
.
To configure WAF to allow, block, or count requests that originated from IP addresses 1111:0000:0000:0000:0000:0000:0000:0000 to 1111:0000:0000:0000:ffff:ffff:ffff:ffff, specify 1111:0000:0000:0000:0000:0000:0000:0000/64
.
For more information about CIDR notation, see the Wikipedia entry Classless Inter-Domain Routing.
Example JSON Addresses
specifications:
Empty array: \"Addresses\": []
Array with one address: \"Addresses\": [\"192.0.2.44/32\"]
Array with three addresses: \"Addresses\": [\"192.0.2.44/32\", \"192.0.2.0/24\", \"192.0.0.0/16\"]
INVALID specification: \"Addresses\": [\"\"]
INVALID
The URL to use in SDK integrations with Amazon Web Services managed rule groups. For example, you can use the integration SDKs with the account takeover prevention managed rule group AWSManagedRulesATPRuleSet
. This is only populated if you are using a rule group in your web ACL that integrates with your applications in this way. For more information, see WAF application integration in the WAF Developer Guide.
The URL to use in SDK integrations with Amazon Web Services managed rule groups. For example, you can use the integration SDKs with the account takeover prevention managed rule group AWSManagedRulesATPRuleSet
. This is only populated if you are using a rule group in your web ACL that integrates with your applications in this way. For more information, see WAF client application integration in the WAF Developer Guide.
Contains an array of strings that specify one or more IP addresses or blocks of IP addresses in Classless Inter-Domain Routing (CIDR) notation. WAF supports all IPv4 and IPv6 CIDR ranges except for /0.
Examples:
To configure WAF to allow, block, or count requests that originated from the IP address 192.0.2.44, specify 192.0.2.44/32
.
To configure WAF to allow, block, or count requests that originated from IP addresses from 192.0.2.0 to 192.0.2.255, specify 192.0.2.0/24
.
To configure WAF to allow, block, or count requests that originated from the IP address 1111:0000:0000:0000:0000:0000:0000:0111, specify 1111:0000:0000:0000:0000:0000:0000:0111/128
.
To configure WAF to allow, block, or count requests that originated from IP addresses 1111:0000:0000:0000:0000:0000:0000:0000 to 1111:0000:0000:0000:ffff:ffff:ffff:ffff, specify 1111:0000:0000:0000:0000:0000:0000:0000/64
.
For more information about CIDR notation, see the Wikipedia entry Classless Inter-Domain Routing.
" + "documentation": "Contains an array of strings that specifies zero or more IP addresses or blocks of IP addresses in Classless Inter-Domain Routing (CIDR) notation. WAF supports all IPv4 and IPv6 CIDR ranges except for /0.
Example address strings:
To configure WAF to allow, block, or count requests that originated from the IP address 192.0.2.44, specify 192.0.2.44/32
.
To configure WAF to allow, block, or count requests that originated from IP addresses from 192.0.2.0 to 192.0.2.255, specify 192.0.2.0/24
.
To configure WAF to allow, block, or count requests that originated from the IP address 1111:0000:0000:0000:0000:0000:0000:0111, specify 1111:0000:0000:0000:0000:0000:0000:0111/128
.
To configure WAF to allow, block, or count requests that originated from IP addresses 1111:0000:0000:0000:0000:0000:0000:0000 to 1111:0000:0000:0000:ffff:ffff:ffff:ffff, specify 1111:0000:0000:0000:0000:0000:0000:0000/64
.
For more information about CIDR notation, see the Wikipedia entry Classless Inter-Domain Routing.
Example JSON Addresses
specifications:
Empty array: \"Addresses\": []
Array with one address: \"Addresses\": [\"192.0.2.44/32\"]
Array with three addresses: \"Addresses\": [\"192.0.2.44/32\", \"192.0.2.0/24\", \"192.0.0.0/16\"]
INVALID specification: \"Addresses\": [\"\"]
INVALID
Contains one or more IP addresses or blocks of IP addresses specified in Classless Inter-Domain Routing (CIDR) notation. WAF supports all IPv4 and IPv6 CIDR ranges except for /0. For information about CIDR notation, see the Wikipedia entry Classless Inter-Domain Routing.
WAF assigns an ARN to each IPSet
that you create. To use an IP set in a rule, you provide the ARN to the Rule statement IPSetReferenceStatement.
Contains zero or more IP addresses or blocks of IP addresses specified in Classless Inter-Domain Routing (CIDR) notation. WAF supports all IPv4 and IPv6 CIDR ranges except for /0. For information about CIDR notation, see the Wikipedia entry Classless Inter-Domain Routing.
WAF assigns an ARN to each IPSet
that you create. To use an IP set in a rule, you provide the ARN to the Rule statement IPSetReferenceStatement.
The Amazon Resource Names (ARNs) of the logging destinations that you want to associate with the web ACL.
" + "documentation": "The logging destination configuration that you want to associate with the web ACL.
You can associate one logging destination to a web ACL.
Filtering that specifies which web requests are kept in the logs and which are dropped. You can filter on the rule action and on the web request labels that were applied by matching rules during web ACL evaluation.
" } }, - "documentation": "Defines an association between logging destinations and a web ACL resource, for logging from WAF. As part of the association, you can specify parts of the standard logging fields to keep out of the logs and you can specify filters so that you log only a subset of the logging records.
For information about configuring web ACL logging destinations, see Logging web ACL traffic information in the WAF Developer Guide.
" + "documentation": "Defines an association between logging destinations and a web ACL resource, for logging from WAF. As part of the association, you can specify parts of the standard logging fields to keep out of the logs and you can specify filters so that you log only a subset of the logging records.
You can define one logging destination per web ACL.
You can access information about the traffic that WAF inspects using the following steps:
Create your logging destination. You can use an Amazon CloudWatch Logs log group, an Amazon Simple Storage Service (Amazon S3) bucket, or an Amazon Kinesis Data Firehose. For information about configuring logging destinations and the permissions that are required for each, see Logging web ACL traffic information in the WAF Developer Guide.
Associate your logging destination to your web ACL using a PutLoggingConfiguration
request.
When you successfully enable logging using a PutLoggingConfiguration
request, WAF creates an additional role or policy that is required to write logs to the logging destination. For an Amazon CloudWatch Logs log group, WAF creates a resource policy on the log group. For an Amazon S3 bucket, WAF creates a bucket policy. For an Amazon Kinesis Data Firehose, WAF creates a service-linked role.
For additional information about web ACL logging, see Logging web ACL traffic information in the WAF Developer Guide.
" }, "LoggingConfigurations": { "type": "list", @@ -4066,7 +4066,7 @@ "members": { "LoginPath": { "shape": "LoginPathString", - "documentation": "The login endpoint for your application. For example https://example.com/web/login
.
The path of the login endpoint for your application. For example, for the URL https://example.com/web/login
, you would provide the path /web/login
.
Tags that are associated with the release.
" } }, - "documentation": "Information for a release of the mobile SDK, including release notes and tags.
The mobile SDK is not generally available. Customers who have access to the mobile SDK can use it to establish and manage Security Token Service (STS) security tokens for use in HTTP(S) requests from a mobile device to WAF.
" + "documentation": "Information for a release of the mobile SDK, including release notes and tags.
The mobile SDK is not generally available. Customers who have access to the mobile SDK can use it to establish and manage Security Token Service (STS) security tokens for use in HTTP(S) requests from a mobile device to WAF. For more information, see WAF client application integration in the WAF Developer Guide.
" }, "NextMarker": { "type": "string", @@ -5397,7 +5397,7 @@ }, "Addresses": { "shape": "IPAddresses", - "documentation": "Contains an array of strings that specify one or more IP addresses or blocks of IP addresses in Classless Inter-Domain Routing (CIDR) notation. WAF supports all IPv4 and IPv6 CIDR ranges except for /0.
Examples:
To configure WAF to allow, block, or count requests that originated from the IP address 192.0.2.44, specify 192.0.2.44/32
.
To configure WAF to allow, block, or count requests that originated from IP addresses from 192.0.2.0 to 192.0.2.255, specify 192.0.2.0/24
.
To configure WAF to allow, block, or count requests that originated from the IP address 1111:0000:0000:0000:0000:0000:0000:0111, specify 1111:0000:0000:0000:0000:0000:0000:0111/128
.
To configure WAF to allow, block, or count requests that originated from IP addresses 1111:0000:0000:0000:0000:0000:0000:0000 to 1111:0000:0000:0000:ffff:ffff:ffff:ffff, specify 1111:0000:0000:0000:0000:0000:0000:0000/64
.
For more information about CIDR notation, see the Wikipedia entry Classless Inter-Domain Routing.
" + "documentation": "Contains an array of strings that specifies zero or more IP addresses or blocks of IP addresses in Classless Inter-Domain Routing (CIDR) notation. WAF supports all IPv4 and IPv6 CIDR ranges except for /0.
Example address strings:
To configure WAF to allow, block, or count requests that originated from the IP address 192.0.2.44, specify 192.0.2.44/32
.
To configure WAF to allow, block, or count requests that originated from IP addresses from 192.0.2.0 to 192.0.2.255, specify 192.0.2.0/24
.
To configure WAF to allow, block, or count requests that originated from the IP address 1111:0000:0000:0000:0000:0000:0000:0111, specify 1111:0000:0000:0000:0000:0000:0000:0111/128
.
To configure WAF to allow, block, or count requests that originated from IP addresses 1111:0000:0000:0000:0000:0000:0000:0000 to 1111:0000:0000:0000:ffff:ffff:ffff:ffff, specify 1111:0000:0000:0000:0000:0000:0000:0000/64
.
For more information about CIDR notation, see the Wikipedia entry Classless Inter-Domain Routing.
Example JSON Addresses
specifications:
Empty array: \"Addresses\": []
Array with one address: \"Addresses\": [\"192.0.2.44/32\"]
Array with three addresses: \"Addresses\": [\"192.0.2.44/32\", \"192.0.2.0/24\", \"192.0.0.0/16\"]
INVALID specification: \"Addresses\": [\"\"]
INVALID