+ * Resets all authorizer cache entries on a stage. Supported only for HTTP APIs. + *
+ * + * @param resetAuthorizersCacheRequest + * @return Result of the ResetAuthorizersCache operation returned by the service. + * @throws NotFoundException + * The resource specified in the request was not found. + * @throws TooManyRequestsException + * The client is sending more than the allowed number of requests per unit of time. + * @sample AmazonApiGatewayV2.ResetAuthorizersCache + */ + ResetAuthorizersCacheResult resetAuthorizersCache(ResetAuthorizersCacheRequest resetAuthorizersCacheRequest); + /** *
* Creates a new Tag resource to represent a tag.
diff --git a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/AmazonApiGatewayV2Async.java b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/AmazonApiGatewayV2Async.java
index ebdb8f45e695..6cbf4f616416 100644
--- a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/AmazonApiGatewayV2Async.java
+++ b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/AmazonApiGatewayV2Async.java
@@ -1593,6 +1593,33 @@ java.util.concurrent.Future
+ * Resets all authorizer cache entries on a stage. Supported only for HTTP APIs.
+ *
+ * Resets all authorizer cache entries on a stage. Supported only for HTTP APIs.
+ *
* Creates a new Tag resource to represent a tag.
diff --git a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/AmazonApiGatewayV2AsyncClient.java b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/AmazonApiGatewayV2AsyncClient.java
index a2c561c8d76d..4d3ca9f43636 100644
--- a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/AmazonApiGatewayV2AsyncClient.java
+++ b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/AmazonApiGatewayV2AsyncClient.java
@@ -1956,6 +1956,39 @@ public ReimportApiResult call() throws Exception {
});
}
+ @Override
+ public java.util.concurrent.Future
+ * Resets all authorizer cache entries on a stage. Supported only for HTTP APIs.
+ *
* Creates a new Tag resource to represent a tag.
diff --git a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/AuthorizationType.java b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/AuthorizationType.java
index 4962e7f1146e..50dc9045f4ca 100644
--- a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/AuthorizationType.java
+++ b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/AuthorizationType.java
@@ -17,8 +17,8 @@
/**
*
* The authorization type. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM
- * permissions, and CUSTOM for using a Lambda authorizer. For HTTP APIs, valid values are NONE for open access, or JWT
- * for using JSON Web Tokens.
+ * permissions, and CUSTOM for using a Lambda authorizer. For HTTP APIs, valid values are NONE for open access, JWT for
+ * using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer.
*
* Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM
* role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on
- * the Lambda function, specify null. Supported only for REQUEST authorizers.
+ * the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers.
*
- * Authorizer caching is not currently supported. Don't specify this value for authorizers.
+ * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda
+ * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with
+ * AWS Lambda authorizers for HTTP APIs.
+ *
+ * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is
+ * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour.
+ * Supported only for HTTP API Lambda authorizers.
*
- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters.
- * For HTTP APIs, specify JWT to use JSON Web Tokens.
+ * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use
+ * JSON Web Tokens (supported only for HTTP APIs).
*
- * The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda
+ * The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda
* function URI, for example,
* arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2:
*
+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer
+ * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with
+ * AWS Lambda authorizers for HTTP APIs
+ *
* The identity source for which authorization is requested.
*
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the
- * specified request parameters. Currently, the identity source can be headers, query string parameters, stage
- * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined
- * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters
- * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related
- * request parameters are present in the request, not null, and non-empty. Only when this is true does the
- * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without
- * calling the Lambda function.
+ * specified request parameters. The identity source can be headers, query string parameters, stage variables, and
+ * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity
+ * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP
+ * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name.
+ * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the
+ * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true
+ * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response
+ * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching
+ * is enabled. To learn more, see Working with
+ * AWS Lambda authorizers for HTTP APIs.
*
* For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently
- * only header-based and query parameter-based selections are supported, for example
- * "$request.header.Authorization".
+ * only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
*
* Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM
* role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on
- * the Lambda function, specify null. Supported only for REQUEST authorizers.
+ * the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers.
*
* Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM
* role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on
- * the Lambda function, specify null. Supported only for REQUEST authorizers.
+ * the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers.
*
* Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM
* role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on
- * the Lambda function, specify null. Supported only for REQUEST authorizers.
+ * the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers.
*
- * Authorizer caching is not currently supported. Don't specify this value for authorizers.
+ * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda
+ * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with
+ * AWS Lambda authorizers for HTTP APIs.
+ *
+ * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda
+ * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with
+ * AWS Lambda authorizers for HTTP APIs.
+ *
+ * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda
+ * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with
+ * AWS Lambda authorizers for HTTP APIs.
+ *
+ * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is
+ * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour.
+ * Supported only for HTTP API Lambda authorizers.
*
- * Authorizer caching is not currently supported. Don't specify this value for authorizers.
+ * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is
+ * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour.
+ * Supported only for HTTP API Lambda authorizers.
*
- * Authorizer caching is not currently supported. Don't specify this value for authorizers.
+ * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is
+ * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour.
+ * Supported only for HTTP API Lambda authorizers.
*
- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters.
- * For HTTP APIs, specify JWT to use JSON Web Tokens.
+ * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use
+ * JSON Web Tokens (supported only for HTTP APIs).
*
- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters.
- * For HTTP APIs, specify JWT to use JSON Web Tokens.
+ * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use
+ * JSON Web Tokens (supported only for HTTP APIs).
*
- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters.
- * For HTTP APIs, specify JWT to use JSON Web Tokens.
+ * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use
+ * JSON Web Tokens (supported only for HTTP APIs).
*
- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters.
- * For HTTP APIs, specify JWT to use JSON Web Tokens.
+ * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use
+ * JSON Web Tokens (supported only for HTTP APIs).
*
- * The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda
+ * The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda
* function URI, for example,
* arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2:
*
- * The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda
+ * The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda
* function URI, for example,
* arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2:
*
- * The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda
+ * The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda
* function URI, for example,
* arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2:
*
+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer
+ * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with
+ * AWS Lambda authorizers for HTTP APIs
+ *
+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer
+ * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with
+ * AWS Lambda authorizers for HTTP APIs
+ *
+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer
+ * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with
+ * AWS Lambda authorizers for HTTP APIs
+ *
+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer
+ * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with
+ * AWS Lambda authorizers for HTTP APIs
+ *
* The identity source for which authorization is requested.
*
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the
- * specified request parameters. Currently, the identity source can be headers, query string parameters, stage
- * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined
- * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters
- * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related
- * request parameters are present in the request, not null, and non-empty. Only when this is true does the
- * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without
- * calling the Lambda function.
+ * specified request parameters. The identity source can be headers, query string parameters, stage variables, and
+ * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity
+ * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP
+ * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name.
+ * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the
+ * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true
+ * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response
+ * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching
+ * is enabled. To learn more, see Working with
+ * AWS Lambda authorizers for HTTP APIs.
*
* For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently
- * only header-based and query parameter-based selections are supported, for example
- * "$request.header.Authorization".
+ * only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
*
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the
- * specified request parameters. Currently, the identity source can be headers, query string parameters,
- * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter
- * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name.
- * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all
- * of the identity-related request parameters are present in the request, not null, and non-empty. Only when
- * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401
- * Unauthorized response without calling the Lambda function.
+ * specified request parameters. The identity source can be headers, query string parameters, stage
+ * variables, and context parameters. For example, if an Auth header and a Name query string parameter are
+ * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for
+ * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example,
+ * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation
+ * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in
+ * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer
+ * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
+ * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more,
+ * see Working with AWS Lambda authorizers for HTTP APIs.
*
* For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests.
* Currently only header-based and query parameter-based selections are supported, for example
- * "$request.header.Authorization".
+ * $request.header.Authorization.
*/
public java.util.List
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the
- * specified request parameters. Currently, the identity source can be headers, query string parameters, stage
- * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined
- * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters
- * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related
- * request parameters are present in the request, not null, and non-empty. Only when this is true does the
- * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without
- * calling the Lambda function.
+ * specified request parameters. The identity source can be headers, query string parameters, stage variables, and
+ * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity
+ * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP
+ * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name.
+ * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the
+ * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true
+ * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response
+ * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching
+ * is enabled. To learn more, see Working with
+ * AWS Lambda authorizers for HTTP APIs.
*
* For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently
- * only header-based and query parameter-based selections are supported, for example
- * "$request.header.Authorization".
+ * only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
*
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see + * + * Working with AWS Lambda authorizers for HTTP APIs. *
*
* For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests.
* Currently only header-based and query parameter-based selections are supported, for example
- * "$request.header.Authorization".
+ * $request.header.Authorization.
*/
public void setIdentitySource(java.util.Collection
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
*
* NOTE: This method appends the values to the existing list (if any). Use
@@ -521,18 +712,22 @@ public void setIdentitySource(java.util.Collection
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see + * + * Working with AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. * Currently only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * $request.header.Authorization. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -552,36 +747,43 @@ public Authorizer withIdentitySource(String... identitySource) { *
** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
* * @param identitySource * The identity source for which authorization is requested. ** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see + * + * Working with AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. * Currently only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * $request.header.Authorization. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -732,12 +934,16 @@ public String toString() { sb.append("AuthorizerCredentialsArn: ").append(getAuthorizerCredentialsArn()).append(","); if (getAuthorizerId() != null) sb.append("AuthorizerId: ").append(getAuthorizerId()).append(","); + if (getAuthorizerPayloadFormatVersion() != null) + sb.append("AuthorizerPayloadFormatVersion: ").append(getAuthorizerPayloadFormatVersion()).append(","); if (getAuthorizerResultTtlInSeconds() != null) sb.append("AuthorizerResultTtlInSeconds: ").append(getAuthorizerResultTtlInSeconds()).append(","); if (getAuthorizerType() != null) sb.append("AuthorizerType: ").append(getAuthorizerType()).append(","); if (getAuthorizerUri() != null) sb.append("AuthorizerUri: ").append(getAuthorizerUri()).append(","); + if (getEnableSimpleResponses() != null) + sb.append("EnableSimpleResponses: ").append(getEnableSimpleResponses()).append(","); if (getIdentitySource() != null) sb.append("IdentitySource: ").append(getIdentitySource()).append(","); if (getIdentityValidationExpression() != null) @@ -768,6 +974,11 @@ public boolean equals(Object obj) { return false; if (other.getAuthorizerId() != null && other.getAuthorizerId().equals(this.getAuthorizerId()) == false) return false; + if (other.getAuthorizerPayloadFormatVersion() == null ^ this.getAuthorizerPayloadFormatVersion() == null) + return false; + if (other.getAuthorizerPayloadFormatVersion() != null + && other.getAuthorizerPayloadFormatVersion().equals(this.getAuthorizerPayloadFormatVersion()) == false) + return false; if (other.getAuthorizerResultTtlInSeconds() == null ^ this.getAuthorizerResultTtlInSeconds() == null) return false; if (other.getAuthorizerResultTtlInSeconds() != null && other.getAuthorizerResultTtlInSeconds().equals(this.getAuthorizerResultTtlInSeconds()) == false) @@ -780,6 +991,10 @@ public boolean equals(Object obj) { return false; if (other.getAuthorizerUri() != null && other.getAuthorizerUri().equals(this.getAuthorizerUri()) == false) return false; + if (other.getEnableSimpleResponses() == null ^ this.getEnableSimpleResponses() == null) + return false; + if (other.getEnableSimpleResponses() != null && other.getEnableSimpleResponses().equals(this.getEnableSimpleResponses()) == false) + return false; if (other.getIdentitySource() == null ^ this.getIdentitySource() == null) return false; if (other.getIdentitySource() != null && other.getIdentitySource().equals(this.getIdentitySource()) == false) @@ -806,9 +1021,11 @@ public int hashCode() { hashCode = prime * hashCode + ((getAuthorizerCredentialsArn() == null) ? 0 : getAuthorizerCredentialsArn().hashCode()); hashCode = prime * hashCode + ((getAuthorizerId() == null) ? 0 : getAuthorizerId().hashCode()); + hashCode = prime * hashCode + ((getAuthorizerPayloadFormatVersion() == null) ? 0 : getAuthorizerPayloadFormatVersion().hashCode()); hashCode = prime * hashCode + ((getAuthorizerResultTtlInSeconds() == null) ? 0 : getAuthorizerResultTtlInSeconds().hashCode()); hashCode = prime * hashCode + ((getAuthorizerType() == null) ? 0 : getAuthorizerType().hashCode()); hashCode = prime * hashCode + ((getAuthorizerUri() == null) ? 0 : getAuthorizerUri().hashCode()); + hashCode = prime * hashCode + ((getEnableSimpleResponses() == null) ? 0 : getEnableSimpleResponses().hashCode()); hashCode = prime * hashCode + ((getIdentitySource() == null) ? 0 : getIdentitySource().hashCode()); hashCode = prime * hashCode + ((getIdentityValidationExpression() == null) ? 0 : getIdentityValidationExpression().hashCode()); hashCode = prime * hashCode + ((getJwtConfiguration() == null) ? 0 : getJwtConfiguration().hashCode()); diff --git a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/AuthorizerType.java b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/AuthorizerType.java index 6a3395ef9c4b..43e2ed01c884 100644 --- a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/AuthorizerType.java +++ b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/AuthorizerType.java @@ -16,8 +16,8 @@ /** *
- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For - * HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON + * Web Tokens (supported only for HTTP APIs). *
*/ @Generated("com.amazonaws:aws-java-sdk-code-generator") diff --git a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/CreateAuthorizerRequest.java b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/CreateAuthorizerRequest.java index bb1bacab2d4b..bbcf30921c1b 100644 --- a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/CreateAuthorizerRequest.java +++ b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/CreateAuthorizerRequest.java @@ -35,20 +35,31 @@ public class CreateAuthorizerRequest extends com.amazonaws.AmazonWebServiceReque ** Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM * role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on - * the Lambda function, specify null. Supported only for REQUEST authorizers. + * the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. *
*/ private String authorizerCredentialsArn; /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ */ + private String authorizerPayloadFormatVersion; + /** + *+ * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
*/ private Integer authorizerResultTtlInSeconds; /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
*/ private String authorizerType; @@ -67,24 +78,37 @@ public class CreateAuthorizerRequest extends com.amazonaws.AmazonWebServiceReque * */ private String authorizerUri; + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must + * return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. + * Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ */ + private Boolean enableSimpleResponses; /** ** The identity source for which authorization is requested. *
** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
*- * For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
*/ private java.util.List* Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM * role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on - * the Lambda function, specify null. Supported only for REQUEST authorizers. + * the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. *
* * @param authorizerCredentialsArn * Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an * IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based - * permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. + * permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. */ public void setAuthorizerCredentialsArn(String authorizerCredentialsArn) { @@ -169,12 +193,12 @@ public void setAuthorizerCredentialsArn(String authorizerCredentialsArn) { ** Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM * role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on - * the Lambda function, specify null. Supported only for REQUEST authorizers. + * the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. *
* * @return Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an * IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based - * permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. + * permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. */ public String getAuthorizerCredentialsArn() { @@ -185,13 +209,13 @@ public String getAuthorizerCredentialsArn() { ** Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM * role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on - * the Lambda function, specify null. Supported only for REQUEST authorizers. + * the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. *
* * @param authorizerCredentialsArn * Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an * IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based - * permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. + * permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -202,11 +226,73 @@ public CreateAuthorizerRequest withAuthorizerCredentialsArn(String authorizerCre /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ * + * @param authorizerPayloadFormatVersion + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. + */ + + public void setAuthorizerPayloadFormatVersion(String authorizerPayloadFormatVersion) { + this.authorizerPayloadFormatVersion = authorizerPayloadFormatVersion; + } + + /** + *+ * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ * + * @return Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. + */ + + public String getAuthorizerPayloadFormatVersion() { + return this.authorizerPayloadFormatVersion; + } + + /** + *+ * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ * + * @param authorizerPayloadFormatVersion + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. + * @return Returns a reference to this object so that method calls can be chained together. + */ + + public CreateAuthorizerRequest withAuthorizerPayloadFormatVersion(String authorizerPayloadFormatVersion) { + setAuthorizerPayloadFormatVersion(authorizerPayloadFormatVersion); + return this; + } + + /** + *+ * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
* * @param authorizerResultTtlInSeconds - * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or + * 1 hour. Supported only for HTTP API Lambda authorizers. */ public void setAuthorizerResultTtlInSeconds(Integer authorizerResultTtlInSeconds) { @@ -215,10 +301,14 @@ public void setAuthorizerResultTtlInSeconds(Integer authorizerResultTtlInSeconds /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
* - * @return Authorizer caching is not currently supported. Don't specify this value for authorizers. + * @return The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching + * is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, + * or 1 hour. Supported only for HTTP API Lambda authorizers. */ public Integer getAuthorizerResultTtlInSeconds() { @@ -227,11 +317,15 @@ public Integer getAuthorizerResultTtlInSeconds() { /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
* * @param authorizerResultTtlInSeconds - * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or + * 1 hour. Supported only for HTTP API Lambda authorizers. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -242,13 +336,13 @@ public CreateAuthorizerRequest withAuthorizerResultTtlInSeconds(Integer authoriz /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* * @param authorizerType - * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @see AuthorizerType */ @@ -258,12 +352,12 @@ public void setAuthorizerType(String authorizerType) { /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* - * @return The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * @return The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @see AuthorizerType */ @@ -273,13 +367,13 @@ public String getAuthorizerType() { /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* * @param authorizerType - * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizerType */ @@ -291,13 +385,13 @@ public CreateAuthorizerRequest withAuthorizerType(String authorizerType) { /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* * @param authorizerType - * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizerType */ @@ -404,41 +498,133 @@ public CreateAuthorizerRequest withAuthorizerUri(String authorizerUri) { return this; } + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must + * return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. + * Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @param enableSimpleResponses + * Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda + * authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead + * of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs + */ + + public void setEnableSimpleResponses(Boolean enableSimpleResponses) { + this.enableSimpleResponses = enableSimpleResponses; + } + + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must + * return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. + * Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @return Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda + * authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value + * instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs + */ + + public Boolean getEnableSimpleResponses() { + return this.enableSimpleResponses; + } + + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must + * return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. + * Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @param enableSimpleResponses + * Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda + * authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead + * of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs + * @return Returns a reference to this object so that method calls can be chained together. + */ + + public CreateAuthorizerRequest withEnableSimpleResponses(Boolean enableSimpleResponses) { + setEnableSimpleResponses(enableSimpleResponses); + return this; + } + + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must + * return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. + * Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @return Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda + * authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value + * instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs + */ + + public Boolean isEnableSimpleResponses() { + return this.enableSimpleResponses; + } + /** ** The identity source for which authorization is requested. *
** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
*- * For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
* * @return The identity source for which authorization is requested. ** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, + * see Working with AWS Lambda authorizers for HTTP APIs. *
*
- * For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests.
+ * For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests.
* Currently only header-based and query parameter-based selections are supported, for example
- * "$request.header.Authorization".
+ * $request.header.Authorization.
*/
public java.util.List
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
*- * For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
* * @param identitySource * The identity source for which authorization is requested. ** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see + * + * Working with AWS Lambda authorizers for HTTP APIs. *
*
- * For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests.
+ * For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests.
* Currently only header-based and query parameter-based selections are supported, for example
- * "$request.header.Authorization".
+ * $request.header.Authorization.
*/
public void setIdentitySource(java.util.Collection
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
*- * For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
*
* NOTE: This method appends the values to the existing list (if any). Use
@@ -521,18 +717,22 @@ public void setIdentitySource(java.util.Collection
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see + * + * Working with AWS Lambda authorizers for HTTP APIs. *
*- * For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. + * For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. * Currently only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * $request.header.Authorization. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -552,36 +752,43 @@ public CreateAuthorizerRequest withIdentitySource(String... identitySource) { *
** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
*- * For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
* * @param identitySource * The identity source for which authorization is requested. ** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see + * + * Working with AWS Lambda authorizers for HTTP APIs. *
*- * For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. + * For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. * Currently only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * $request.header.Authorization. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -732,12 +939,16 @@ public String toString() { sb.append("ApiId: ").append(getApiId()).append(","); if (getAuthorizerCredentialsArn() != null) sb.append("AuthorizerCredentialsArn: ").append(getAuthorizerCredentialsArn()).append(","); + if (getAuthorizerPayloadFormatVersion() != null) + sb.append("AuthorizerPayloadFormatVersion: ").append(getAuthorizerPayloadFormatVersion()).append(","); if (getAuthorizerResultTtlInSeconds() != null) sb.append("AuthorizerResultTtlInSeconds: ").append(getAuthorizerResultTtlInSeconds()).append(","); if (getAuthorizerType() != null) sb.append("AuthorizerType: ").append(getAuthorizerType()).append(","); if (getAuthorizerUri() != null) sb.append("AuthorizerUri: ").append(getAuthorizerUri()).append(","); + if (getEnableSimpleResponses() != null) + sb.append("EnableSimpleResponses: ").append(getEnableSimpleResponses()).append(","); if (getIdentitySource() != null) sb.append("IdentitySource: ").append(getIdentitySource()).append(","); if (getIdentityValidationExpression() != null) @@ -768,6 +979,11 @@ public boolean equals(Object obj) { return false; if (other.getAuthorizerCredentialsArn() != null && other.getAuthorizerCredentialsArn().equals(this.getAuthorizerCredentialsArn()) == false) return false; + if (other.getAuthorizerPayloadFormatVersion() == null ^ this.getAuthorizerPayloadFormatVersion() == null) + return false; + if (other.getAuthorizerPayloadFormatVersion() != null + && other.getAuthorizerPayloadFormatVersion().equals(this.getAuthorizerPayloadFormatVersion()) == false) + return false; if (other.getAuthorizerResultTtlInSeconds() == null ^ this.getAuthorizerResultTtlInSeconds() == null) return false; if (other.getAuthorizerResultTtlInSeconds() != null && other.getAuthorizerResultTtlInSeconds().equals(this.getAuthorizerResultTtlInSeconds()) == false) @@ -780,6 +996,10 @@ public boolean equals(Object obj) { return false; if (other.getAuthorizerUri() != null && other.getAuthorizerUri().equals(this.getAuthorizerUri()) == false) return false; + if (other.getEnableSimpleResponses() == null ^ this.getEnableSimpleResponses() == null) + return false; + if (other.getEnableSimpleResponses() != null && other.getEnableSimpleResponses().equals(this.getEnableSimpleResponses()) == false) + return false; if (other.getIdentitySource() == null ^ this.getIdentitySource() == null) return false; if (other.getIdentitySource() != null && other.getIdentitySource().equals(this.getIdentitySource()) == false) @@ -806,9 +1026,11 @@ public int hashCode() { hashCode = prime * hashCode + ((getApiId() == null) ? 0 : getApiId().hashCode()); hashCode = prime * hashCode + ((getAuthorizerCredentialsArn() == null) ? 0 : getAuthorizerCredentialsArn().hashCode()); + hashCode = prime * hashCode + ((getAuthorizerPayloadFormatVersion() == null) ? 0 : getAuthorizerPayloadFormatVersion().hashCode()); hashCode = prime * hashCode + ((getAuthorizerResultTtlInSeconds() == null) ? 0 : getAuthorizerResultTtlInSeconds().hashCode()); hashCode = prime * hashCode + ((getAuthorizerType() == null) ? 0 : getAuthorizerType().hashCode()); hashCode = prime * hashCode + ((getAuthorizerUri() == null) ? 0 : getAuthorizerUri().hashCode()); + hashCode = prime * hashCode + ((getEnableSimpleResponses() == null) ? 0 : getEnableSimpleResponses().hashCode()); hashCode = prime * hashCode + ((getIdentitySource() == null) ? 0 : getIdentitySource().hashCode()); hashCode = prime * hashCode + ((getIdentityValidationExpression() == null) ? 0 : getIdentityValidationExpression().hashCode()); hashCode = prime * hashCode + ((getJwtConfiguration() == null) ? 0 : getJwtConfiguration().hashCode()); diff --git a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/CreateAuthorizerResult.java b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/CreateAuthorizerResult.java index ae52071b3af7..34873161f592 100644 --- a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/CreateAuthorizerResult.java +++ b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/CreateAuthorizerResult.java @@ -22,7 +22,7 @@ public class CreateAuthorizerResult extends com.amazonaws.AmazonWebServiceResult *
* Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM * role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on - * the Lambda function, specify null. Supported only for REQUEST authorizers. + * the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. *
*/ private String authorizerCredentialsArn; @@ -34,20 +34,31 @@ public class CreateAuthorizerResult extends com.amazonaws.AmazonWebServiceResult private String authorizerId; /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ */ + private String authorizerPayloadFormatVersion; + /** + *+ * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
*/ private Integer authorizerResultTtlInSeconds; /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
*/ private String authorizerType; /** *
- * The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda
+ * The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda
* function URI, for example,
* arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2:
*
+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer + * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ */ + private Boolean enableSimpleResponses; /** ** The identity source for which authorization is requested. *
** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
*/ private java.util.List* Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM * role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on - * the Lambda function, specify null. Supported only for REQUEST authorizers. + * the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. *
* * @param authorizerCredentialsArn * Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an * IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based - * permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. + * permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. */ public void setAuthorizerCredentialsArn(String authorizerCredentialsArn) { @@ -122,12 +145,12 @@ public void setAuthorizerCredentialsArn(String authorizerCredentialsArn) { ** Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM * role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on - * the Lambda function, specify null. Supported only for REQUEST authorizers. + * the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. *
* * @return Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an * IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based - * permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. + * permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. */ public String getAuthorizerCredentialsArn() { @@ -138,13 +161,13 @@ public String getAuthorizerCredentialsArn() { ** Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM * role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on - * the Lambda function, specify null. Supported only for REQUEST authorizers. + * the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. *
* * @param authorizerCredentialsArn * Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an * IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based - * permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. + * permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -195,11 +218,73 @@ public CreateAuthorizerResult withAuthorizerId(String authorizerId) { /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ * + * @param authorizerPayloadFormatVersion + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. + */ + + public void setAuthorizerPayloadFormatVersion(String authorizerPayloadFormatVersion) { + this.authorizerPayloadFormatVersion = authorizerPayloadFormatVersion; + } + + /** + *+ * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ * + * @return Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. + */ + + public String getAuthorizerPayloadFormatVersion() { + return this.authorizerPayloadFormatVersion; + } + + /** + *+ * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ * + * @param authorizerPayloadFormatVersion + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. + * @return Returns a reference to this object so that method calls can be chained together. + */ + + public CreateAuthorizerResult withAuthorizerPayloadFormatVersion(String authorizerPayloadFormatVersion) { + setAuthorizerPayloadFormatVersion(authorizerPayloadFormatVersion); + return this; + } + + /** + *+ * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
* * @param authorizerResultTtlInSeconds - * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or + * 1 hour. Supported only for HTTP API Lambda authorizers. */ public void setAuthorizerResultTtlInSeconds(Integer authorizerResultTtlInSeconds) { @@ -208,10 +293,14 @@ public void setAuthorizerResultTtlInSeconds(Integer authorizerResultTtlInSeconds /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
* - * @return Authorizer caching is not currently supported. Don't specify this value for authorizers. + * @return The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching + * is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, + * or 1 hour. Supported only for HTTP API Lambda authorizers. */ public Integer getAuthorizerResultTtlInSeconds() { @@ -220,11 +309,15 @@ public Integer getAuthorizerResultTtlInSeconds() { /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
* * @param authorizerResultTtlInSeconds - * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or + * 1 hour. Supported only for HTTP API Lambda authorizers. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -235,13 +328,13 @@ public CreateAuthorizerResult withAuthorizerResultTtlInSeconds(Integer authorize /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* * @param authorizerType - * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @see AuthorizerType */ @@ -251,12 +344,12 @@ public void setAuthorizerType(String authorizerType) { /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* - * @return The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * @return The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @see AuthorizerType */ @@ -266,13 +359,13 @@ public String getAuthorizerType() { /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* * @param authorizerType - * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizerType */ @@ -284,13 +377,13 @@ public CreateAuthorizerResult withAuthorizerType(String authorizerType) { /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* * @param authorizerType - * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizerType */ @@ -302,7 +395,7 @@ public CreateAuthorizerResult withAuthorizerType(AuthorizerType authorizerType) /** *
- * The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda
+ * The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda
* function URI, for example,
* arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2:
*
- * The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda
+ * The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda
* function URI, for example,
* arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2:
*
- * The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda
+ * The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda
* function URI, for example,
* arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2:
*
+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer + * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @param enableSimpleResponses + * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda + * authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn + * more, see Working with AWS Lambda authorizers for HTTP APIs + */ + + public void setEnableSimpleResponses(Boolean enableSimpleResponses) { + this.enableSimpleResponses = enableSimpleResponses; + } + + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer + * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @return Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda + * authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn + * more, see Working with AWS Lambda authorizers for HTTP APIs + */ + + public Boolean getEnableSimpleResponses() { + return this.enableSimpleResponses; + } + + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer + * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @param enableSimpleResponses + * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda + * authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn + * more, see Working with AWS Lambda authorizers for HTTP APIs + * @return Returns a reference to this object so that method calls can be chained together. + */ + + public CreateAuthorizerResult withEnableSimpleResponses(Boolean enableSimpleResponses) { + setEnableSimpleResponses(enableSimpleResponses); + return this; + } + + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer + * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @return Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda + * authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn + * more, see Working with AWS Lambda authorizers for HTTP APIs + */ + + public Boolean isEnableSimpleResponses() { + return this.enableSimpleResponses; + } + /** ** The identity source for which authorization is requested. *
** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
* * @return The identity source for which authorization is requested. ** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, + * see Working with AWS Lambda authorizers for HTTP APIs. *
*
* For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests.
* Currently only header-based and query parameter-based selections are supported, for example
- * "$request.header.Authorization".
+ * $request.header.Authorization.
*/
public java.util.List
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
* * @param identitySource * The identity source for which authorization is requested. ** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see + * + * Working with AWS Lambda authorizers for HTTP APIs. *
*
* For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests.
* Currently only header-based and query parameter-based selections are supported, for example
- * "$request.header.Authorization".
+ * $request.header.Authorization.
*/
public void setIdentitySource(java.util.Collection
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
*
* NOTE: This method appends the values to the existing list (if any). Use
@@ -514,18 +705,22 @@ public void setIdentitySource(java.util.Collection
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see + * + * Working with AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. * Currently only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * $request.header.Authorization. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -545,36 +740,43 @@ public CreateAuthorizerResult withIdentitySource(String... identitySource) { *
** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
* * @param identitySource * The identity source for which authorization is requested. ** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see + * + * Working with AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. * Currently only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * $request.header.Authorization. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -725,12 +927,16 @@ public String toString() { sb.append("AuthorizerCredentialsArn: ").append(getAuthorizerCredentialsArn()).append(","); if (getAuthorizerId() != null) sb.append("AuthorizerId: ").append(getAuthorizerId()).append(","); + if (getAuthorizerPayloadFormatVersion() != null) + sb.append("AuthorizerPayloadFormatVersion: ").append(getAuthorizerPayloadFormatVersion()).append(","); if (getAuthorizerResultTtlInSeconds() != null) sb.append("AuthorizerResultTtlInSeconds: ").append(getAuthorizerResultTtlInSeconds()).append(","); if (getAuthorizerType() != null) sb.append("AuthorizerType: ").append(getAuthorizerType()).append(","); if (getAuthorizerUri() != null) sb.append("AuthorizerUri: ").append(getAuthorizerUri()).append(","); + if (getEnableSimpleResponses() != null) + sb.append("EnableSimpleResponses: ").append(getEnableSimpleResponses()).append(","); if (getIdentitySource() != null) sb.append("IdentitySource: ").append(getIdentitySource()).append(","); if (getIdentityValidationExpression() != null) @@ -761,6 +967,11 @@ public boolean equals(Object obj) { return false; if (other.getAuthorizerId() != null && other.getAuthorizerId().equals(this.getAuthorizerId()) == false) return false; + if (other.getAuthorizerPayloadFormatVersion() == null ^ this.getAuthorizerPayloadFormatVersion() == null) + return false; + if (other.getAuthorizerPayloadFormatVersion() != null + && other.getAuthorizerPayloadFormatVersion().equals(this.getAuthorizerPayloadFormatVersion()) == false) + return false; if (other.getAuthorizerResultTtlInSeconds() == null ^ this.getAuthorizerResultTtlInSeconds() == null) return false; if (other.getAuthorizerResultTtlInSeconds() != null && other.getAuthorizerResultTtlInSeconds().equals(this.getAuthorizerResultTtlInSeconds()) == false) @@ -773,6 +984,10 @@ public boolean equals(Object obj) { return false; if (other.getAuthorizerUri() != null && other.getAuthorizerUri().equals(this.getAuthorizerUri()) == false) return false; + if (other.getEnableSimpleResponses() == null ^ this.getEnableSimpleResponses() == null) + return false; + if (other.getEnableSimpleResponses() != null && other.getEnableSimpleResponses().equals(this.getEnableSimpleResponses()) == false) + return false; if (other.getIdentitySource() == null ^ this.getIdentitySource() == null) return false; if (other.getIdentitySource() != null && other.getIdentitySource().equals(this.getIdentitySource()) == false) @@ -799,9 +1014,11 @@ public int hashCode() { hashCode = prime * hashCode + ((getAuthorizerCredentialsArn() == null) ? 0 : getAuthorizerCredentialsArn().hashCode()); hashCode = prime * hashCode + ((getAuthorizerId() == null) ? 0 : getAuthorizerId().hashCode()); + hashCode = prime * hashCode + ((getAuthorizerPayloadFormatVersion() == null) ? 0 : getAuthorizerPayloadFormatVersion().hashCode()); hashCode = prime * hashCode + ((getAuthorizerResultTtlInSeconds() == null) ? 0 : getAuthorizerResultTtlInSeconds().hashCode()); hashCode = prime * hashCode + ((getAuthorizerType() == null) ? 0 : getAuthorizerType().hashCode()); hashCode = prime * hashCode + ((getAuthorizerUri() == null) ? 0 : getAuthorizerUri().hashCode()); + hashCode = prime * hashCode + ((getEnableSimpleResponses() == null) ? 0 : getEnableSimpleResponses().hashCode()); hashCode = prime * hashCode + ((getIdentitySource() == null) ? 0 : getIdentitySource().hashCode()); hashCode = prime * hashCode + ((getIdentityValidationExpression() == null) ? 0 : getIdentityValidationExpression().hashCode()); hashCode = prime * hashCode + ((getJwtConfiguration() == null) ? 0 : getJwtConfiguration().hashCode()); diff --git a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/CreateRouteRequest.java b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/CreateRouteRequest.java index 0f7708c515c3..98fe64bd020d 100644 --- a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/CreateRouteRequest.java +++ b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/CreateRouteRequest.java @@ -47,7 +47,8 @@ public class CreateRouteRequest extends com.amazonaws.AmazonWebServiceRequest im *
* The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
*/ private String authorizationType; @@ -267,13 +268,15 @@ public CreateRouteRequest withAuthorizationScopes(java.util.Collection* The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @param authorizationType * The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for + * using a Lambda authorizer. * @see AuthorizationType */ @@ -285,12 +288,14 @@ public void setAuthorizationType(String authorizationType) { ** The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @return The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM + * for using a Lambda authorizer. * @see AuthorizationType */ @@ -302,13 +307,15 @@ public String getAuthorizationType() { ** The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @param authorizationType * The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for + * using a Lambda authorizer. * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizationType */ @@ -322,13 +329,15 @@ public CreateRouteRequest withAuthorizationType(String authorizationType) { ** The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @param authorizationType * The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for + * using a Lambda authorizer. * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizationType */ diff --git a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/CreateRouteResult.java b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/CreateRouteResult.java index 2c911b909ab1..039696f51285 100644 --- a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/CreateRouteResult.java +++ b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/CreateRouteResult.java @@ -45,7 +45,8 @@ public class CreateRouteResult extends com.amazonaws.AmazonWebServiceResult* The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @param authorizationType * The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for + * using a Lambda authorizer. * @see AuthorizationType */ @@ -345,12 +348,14 @@ public void setAuthorizationType(String authorizationType) { ** The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @return The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM + * for using a Lambda authorizer. * @see AuthorizationType */ @@ -362,13 +367,15 @@ public String getAuthorizationType() { ** The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @param authorizationType * The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for + * using a Lambda authorizer. * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizationType */ @@ -382,13 +389,15 @@ public CreateRouteResult withAuthorizationType(String authorizationType) { ** The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @param authorizationType * The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for + * using a Lambda authorizer. * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizationType */ diff --git a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/GetAuthorizerResult.java b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/GetAuthorizerResult.java index 9b8d3bb8e58d..47680013f1c9 100644 --- a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/GetAuthorizerResult.java +++ b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/GetAuthorizerResult.java @@ -22,7 +22,7 @@ public class GetAuthorizerResult extends com.amazonaws.AmazonWebServiceResult+ * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
*/ private Integer authorizerResultTtlInSeconds; /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
*/ private String authorizerType; /** *
- * The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda
+ * The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda
* function URI, for example,
* arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2:
*
+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer
+ * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with
+ * AWS Lambda authorizers for HTTP APIs
+ *
* The identity source for which authorization is requested.
*
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the
- * specified request parameters. Currently, the identity source can be headers, query string parameters, stage
- * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined
- * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters
- * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related
- * request parameters are present in the request, not null, and non-empty. Only when this is true does the
- * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without
- * calling the Lambda function.
+ * specified request parameters. The identity source can be headers, query string parameters, stage variables, and
+ * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity
+ * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP
+ * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name.
+ * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the
+ * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true
+ * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response
+ * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching
+ * is enabled. To learn more, see Working with
+ * AWS Lambda authorizers for HTTP APIs.
*
* For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently
- * only header-based and query parameter-based selections are supported, for example
- * "$request.header.Authorization".
+ * only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
*
* Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM * role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on - * the Lambda function, specify null. Supported only for REQUEST authorizers. + * the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. *
* * @return Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an * IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based - * permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. + * permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. */ public String getAuthorizerCredentialsArn() { @@ -138,13 +161,13 @@ public String getAuthorizerCredentialsArn() { ** Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM * role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on - * the Lambda function, specify null. Supported only for REQUEST authorizers. + * the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. *
* * @param authorizerCredentialsArn * Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an * IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based - * permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. + * permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -195,11 +218,73 @@ public GetAuthorizerResult withAuthorizerId(String authorizerId) { /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ * + * @param authorizerPayloadFormatVersion + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. + */ + + public void setAuthorizerPayloadFormatVersion(String authorizerPayloadFormatVersion) { + this.authorizerPayloadFormatVersion = authorizerPayloadFormatVersion; + } + + /** + *+ * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ * + * @return Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. + */ + + public String getAuthorizerPayloadFormatVersion() { + return this.authorizerPayloadFormatVersion; + } + + /** + *+ * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ * + * @param authorizerPayloadFormatVersion + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. + * @return Returns a reference to this object so that method calls can be chained together. + */ + + public GetAuthorizerResult withAuthorizerPayloadFormatVersion(String authorizerPayloadFormatVersion) { + setAuthorizerPayloadFormatVersion(authorizerPayloadFormatVersion); + return this; + } + + /** + *+ * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
* * @param authorizerResultTtlInSeconds - * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or + * 1 hour. Supported only for HTTP API Lambda authorizers. */ public void setAuthorizerResultTtlInSeconds(Integer authorizerResultTtlInSeconds) { @@ -208,10 +293,14 @@ public void setAuthorizerResultTtlInSeconds(Integer authorizerResultTtlInSeconds /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
* - * @return Authorizer caching is not currently supported. Don't specify this value for authorizers. + * @return The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching + * is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, + * or 1 hour. Supported only for HTTP API Lambda authorizers. */ public Integer getAuthorizerResultTtlInSeconds() { @@ -220,11 +309,15 @@ public Integer getAuthorizerResultTtlInSeconds() { /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
* * @param authorizerResultTtlInSeconds - * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or + * 1 hour. Supported only for HTTP API Lambda authorizers. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -235,13 +328,13 @@ public GetAuthorizerResult withAuthorizerResultTtlInSeconds(Integer authorizerRe /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* * @param authorizerType - * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @see AuthorizerType */ @@ -251,12 +344,12 @@ public void setAuthorizerType(String authorizerType) { /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* - * @return The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * @return The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @see AuthorizerType */ @@ -266,13 +359,13 @@ public String getAuthorizerType() { /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* * @param authorizerType - * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizerType */ @@ -284,13 +377,13 @@ public GetAuthorizerResult withAuthorizerType(String authorizerType) { /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* * @param authorizerType - * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizerType */ @@ -302,7 +395,7 @@ public GetAuthorizerResult withAuthorizerType(AuthorizerType authorizerType) { /** *
- * The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda
+ * The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda
* function URI, for example,
* arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2:
*
- * The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda
+ * The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda
* function URI, for example,
* arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2:
*
- * The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda
+ * The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda
* function URI, for example,
* arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2:
*
+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer + * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @param enableSimpleResponses + * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda + * authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn + * more, see Working with AWS Lambda authorizers for HTTP APIs + */ + + public void setEnableSimpleResponses(Boolean enableSimpleResponses) { + this.enableSimpleResponses = enableSimpleResponses; + } + + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer + * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @return Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda + * authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn + * more, see Working with AWS Lambda authorizers for HTTP APIs + */ + + public Boolean getEnableSimpleResponses() { + return this.enableSimpleResponses; + } + + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer + * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @param enableSimpleResponses + * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda + * authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn + * more, see Working with AWS Lambda authorizers for HTTP APIs + * @return Returns a reference to this object so that method calls can be chained together. + */ + + public GetAuthorizerResult withEnableSimpleResponses(Boolean enableSimpleResponses) { + setEnableSimpleResponses(enableSimpleResponses); + return this; + } + + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer + * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @return Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda + * authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn + * more, see Working with AWS Lambda authorizers for HTTP APIs + */ + + public Boolean isEnableSimpleResponses() { + return this.enableSimpleResponses; + } + /** ** The identity source for which authorization is requested. *
** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
* * @return The identity source for which authorization is requested. ** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, + * see Working with AWS Lambda authorizers for HTTP APIs. *
*
* For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests.
* Currently only header-based and query parameter-based selections are supported, for example
- * "$request.header.Authorization".
+ * $request.header.Authorization.
*/
public java.util.List
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
* * @param identitySource * The identity source for which authorization is requested. ** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see + * + * Working with AWS Lambda authorizers for HTTP APIs. *
*
* For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests.
* Currently only header-based and query parameter-based selections are supported, for example
- * "$request.header.Authorization".
+ * $request.header.Authorization.
*/
public void setIdentitySource(java.util.Collection
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
*
* NOTE: This method appends the values to the existing list (if any). Use
@@ -514,18 +705,22 @@ public void setIdentitySource(java.util.Collection
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see + * + * Working with AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. * Currently only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * $request.header.Authorization. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -545,36 +740,43 @@ public GetAuthorizerResult withIdentitySource(String... identitySource) { *
** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
* * @param identitySource * The identity source for which authorization is requested. ** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see + * + * Working with AWS Lambda authorizers for HTTP APIs. *
*
* For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests.
* Currently only header-based and query parameter-based selections are supported, for example
- * "$request.header.Authorization".
+ * $request.header.Authorization.
* @return Returns a reference to this object so that method calls can be chained together.
*/
@@ -725,12 +927,16 @@ public String toString() {
sb.append("AuthorizerCredentialsArn: ").append(getAuthorizerCredentialsArn()).append(",");
if (getAuthorizerId() != null)
sb.append("AuthorizerId: ").append(getAuthorizerId()).append(",");
+ if (getAuthorizerPayloadFormatVersion() != null)
+ sb.append("AuthorizerPayloadFormatVersion: ").append(getAuthorizerPayloadFormatVersion()).append(",");
if (getAuthorizerResultTtlInSeconds() != null)
sb.append("AuthorizerResultTtlInSeconds: ").append(getAuthorizerResultTtlInSeconds()).append(",");
if (getAuthorizerType() != null)
sb.append("AuthorizerType: ").append(getAuthorizerType()).append(",");
if (getAuthorizerUri() != null)
sb.append("AuthorizerUri: ").append(getAuthorizerUri()).append(",");
+ if (getEnableSimpleResponses() != null)
+ sb.append("EnableSimpleResponses: ").append(getEnableSimpleResponses()).append(",");
if (getIdentitySource() != null)
sb.append("IdentitySource: ").append(getIdentitySource()).append(",");
if (getIdentityValidationExpression() != null)
@@ -761,6 +967,11 @@ public boolean equals(Object obj) {
return false;
if (other.getAuthorizerId() != null && other.getAuthorizerId().equals(this.getAuthorizerId()) == false)
return false;
+ if (other.getAuthorizerPayloadFormatVersion() == null ^ this.getAuthorizerPayloadFormatVersion() == null)
+ return false;
+ if (other.getAuthorizerPayloadFormatVersion() != null
+ && other.getAuthorizerPayloadFormatVersion().equals(this.getAuthorizerPayloadFormatVersion()) == false)
+ return false;
if (other.getAuthorizerResultTtlInSeconds() == null ^ this.getAuthorizerResultTtlInSeconds() == null)
return false;
if (other.getAuthorizerResultTtlInSeconds() != null && other.getAuthorizerResultTtlInSeconds().equals(this.getAuthorizerResultTtlInSeconds()) == false)
@@ -773,6 +984,10 @@ public boolean equals(Object obj) {
return false;
if (other.getAuthorizerUri() != null && other.getAuthorizerUri().equals(this.getAuthorizerUri()) == false)
return false;
+ if (other.getEnableSimpleResponses() == null ^ this.getEnableSimpleResponses() == null)
+ return false;
+ if (other.getEnableSimpleResponses() != null && other.getEnableSimpleResponses().equals(this.getEnableSimpleResponses()) == false)
+ return false;
if (other.getIdentitySource() == null ^ this.getIdentitySource() == null)
return false;
if (other.getIdentitySource() != null && other.getIdentitySource().equals(this.getIdentitySource()) == false)
@@ -799,9 +1014,11 @@ public int hashCode() {
hashCode = prime * hashCode + ((getAuthorizerCredentialsArn() == null) ? 0 : getAuthorizerCredentialsArn().hashCode());
hashCode = prime * hashCode + ((getAuthorizerId() == null) ? 0 : getAuthorizerId().hashCode());
+ hashCode = prime * hashCode + ((getAuthorizerPayloadFormatVersion() == null) ? 0 : getAuthorizerPayloadFormatVersion().hashCode());
hashCode = prime * hashCode + ((getAuthorizerResultTtlInSeconds() == null) ? 0 : getAuthorizerResultTtlInSeconds().hashCode());
hashCode = prime * hashCode + ((getAuthorizerType() == null) ? 0 : getAuthorizerType().hashCode());
hashCode = prime * hashCode + ((getAuthorizerUri() == null) ? 0 : getAuthorizerUri().hashCode());
+ hashCode = prime * hashCode + ((getEnableSimpleResponses() == null) ? 0 : getEnableSimpleResponses().hashCode());
hashCode = prime * hashCode + ((getIdentitySource() == null) ? 0 : getIdentitySource().hashCode());
hashCode = prime * hashCode + ((getIdentityValidationExpression() == null) ? 0 : getIdentityValidationExpression().hashCode());
hashCode = prime * hashCode + ((getJwtConfiguration() == null) ? 0 : getJwtConfiguration().hashCode());
diff --git a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/GetRouteResult.java b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/GetRouteResult.java
index 92f2a958b6da..e326bfbfd3a7 100644
--- a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/GetRouteResult.java
+++ b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/GetRouteResult.java
@@ -45,7 +45,8 @@ public class GetRouteResult extends com.amazonaws.AmazonWebServiceResult
* The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @param authorizationType * The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for + * using a Lambda authorizer. * @see AuthorizationType */ @@ -345,12 +348,14 @@ public void setAuthorizationType(String authorizationType) { ** The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @return The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM + * for using a Lambda authorizer. * @see AuthorizationType */ @@ -362,13 +367,15 @@ public String getAuthorizationType() { ** The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @param authorizationType * The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for + * using a Lambda authorizer. * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizationType */ @@ -382,13 +389,15 @@ public GetRouteResult withAuthorizationType(String authorizationType) { ** The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @param authorizationType * The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for + * using a Lambda authorizer. * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizationType */ diff --git a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/ResetAuthorizersCacheRequest.java b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/ResetAuthorizersCacheRequest.java new file mode 100644 index 000000000000..1f7b316c7b53 --- /dev/null +++ b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/ResetAuthorizersCacheRequest.java @@ -0,0 +1,179 @@ +/* + * Copyright 2015-2020 Amazon.com, Inc. or its affiliates. All Rights Reserved. + * + * Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance with + * the License. A copy of the License is located at + * + * http://aws.amazon.com/apache2.0 + * + * or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR + * CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions + * and limitations under the License. + */ +package com.amazonaws.services.apigatewayv2.model; + +import java.io.Serializable; +import javax.annotation.Generated; + +import com.amazonaws.AmazonWebServiceRequest; + +@Generated("com.amazonaws:aws-java-sdk-code-generator") +public class ResetAuthorizersCacheRequest extends com.amazonaws.AmazonWebServiceRequest implements Serializable, Cloneable { + + /** + *+ * The API identifier. + *
+ */ + private String apiId; + /** + *+ * The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be $default. + * Maximum length is 128 characters. + *
+ */ + private String stageName; + + /** + *+ * The API identifier. + *
+ * + * @param apiId + * The API identifier. + */ + + public void setApiId(String apiId) { + this.apiId = apiId; + } + + /** + *+ * The API identifier. + *
+ * + * @return The API identifier. + */ + + public String getApiId() { + return this.apiId; + } + + /** + *+ * The API identifier. + *
+ * + * @param apiId + * The API identifier. + * @return Returns a reference to this object so that method calls can be chained together. + */ + + public ResetAuthorizersCacheRequest withApiId(String apiId) { + setApiId(apiId); + return this; + } + + /** + *+ * The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be $default. + * Maximum length is 128 characters. + *
+ * + * @param stageName + * The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be + * $default. Maximum length is 128 characters. + */ + + public void setStageName(String stageName) { + this.stageName = stageName; + } + + /** + *+ * The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be $default. + * Maximum length is 128 characters. + *
+ * + * @return The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be + * $default. Maximum length is 128 characters. + */ + + public String getStageName() { + return this.stageName; + } + + /** + *+ * The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be $default. + * Maximum length is 128 characters. + *
+ * + * @param stageName + * The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be + * $default. Maximum length is 128 characters. + * @return Returns a reference to this object so that method calls can be chained together. + */ + + public ResetAuthorizersCacheRequest withStageName(String stageName) { + setStageName(stageName); + return this; + } + + /** + * Returns a string representation of this object. This is useful for testing and debugging. Sensitive data will be + * redacted from this string using a placeholder value. + * + * @return A string representation of this object. + * + * @see java.lang.Object#toString() + */ + @Override + public String toString() { + StringBuilder sb = new StringBuilder(); + sb.append("{"); + if (getApiId() != null) + sb.append("ApiId: ").append(getApiId()).append(","); + if (getStageName() != null) + sb.append("StageName: ").append(getStageName()); + sb.append("}"); + return sb.toString(); + } + + @Override + public boolean equals(Object obj) { + if (this == obj) + return true; + if (obj == null) + return false; + + if (obj instanceof ResetAuthorizersCacheRequest == false) + return false; + ResetAuthorizersCacheRequest other = (ResetAuthorizersCacheRequest) obj; + if (other.getApiId() == null ^ this.getApiId() == null) + return false; + if (other.getApiId() != null && other.getApiId().equals(this.getApiId()) == false) + return false; + if (other.getStageName() == null ^ this.getStageName() == null) + return false; + if (other.getStageName() != null && other.getStageName().equals(this.getStageName()) == false) + return false; + return true; + } + + @Override + public int hashCode() { + final int prime = 31; + int hashCode = 1; + + hashCode = prime * hashCode + ((getApiId() == null) ? 0 : getApiId().hashCode()); + hashCode = prime * hashCode + ((getStageName() == null) ? 0 : getStageName().hashCode()); + return hashCode; + } + + @Override + public ResetAuthorizersCacheRequest clone() { + return (ResetAuthorizersCacheRequest) super.clone(); + } + +} diff --git a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/ResetAuthorizersCacheResult.java b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/ResetAuthorizersCacheResult.java new file mode 100644 index 000000000000..383171380f3e --- /dev/null +++ b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/ResetAuthorizersCacheResult.java @@ -0,0 +1,67 @@ +/* + * Copyright 2015-2020 Amazon.com, Inc. or its affiliates. All Rights Reserved. + * + * Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance with + * the License. A copy of the License is located at + * + * http://aws.amazon.com/apache2.0 + * + * or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR + * CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions + * and limitations under the License. + */ +package com.amazonaws.services.apigatewayv2.model; + +import java.io.Serializable; +import javax.annotation.Generated; + +@Generated("com.amazonaws:aws-java-sdk-code-generator") +public class ResetAuthorizersCacheResult extends com.amazonaws.AmazonWebServiceResult* The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
*/ private String authorizationType; @@ -334,13 +335,15 @@ public Route withAuthorizationScopes(java.util.Collection* The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @param authorizationType * The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for + * using a Lambda authorizer. * @see AuthorizationType */ @@ -352,12 +355,14 @@ public void setAuthorizationType(String authorizationType) { ** The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @return The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM + * for using a Lambda authorizer. * @see AuthorizationType */ @@ -369,13 +374,15 @@ public String getAuthorizationType() { ** The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @param authorizationType * The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for + * using a Lambda authorizer. * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizationType */ @@ -389,13 +396,15 @@ public Route withAuthorizationType(String authorizationType) { ** The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @param authorizationType * The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for + * using a Lambda authorizer. * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizationType */ diff --git a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/UpdateAuthorizerRequest.java b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/UpdateAuthorizerRequest.java index f61eb9bfceb7..ed5e589a4c26 100644 --- a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/UpdateAuthorizerRequest.java +++ b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/UpdateAuthorizerRequest.java @@ -35,7 +35,7 @@ public class UpdateAuthorizerRequest extends com.amazonaws.AmazonWebServiceReque ** Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM * role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on - * the Lambda function, specify null. + * the Lambda function, don't specify this parameter. *
*/ private String authorizerCredentialsArn; @@ -47,14 +47,25 @@ public class UpdateAuthorizerRequest extends com.amazonaws.AmazonWebServiceReque private String authorizerId; /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ */ + private String authorizerPayloadFormatVersion; + /** + *+ * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
*/ private Integer authorizerResultTtlInSeconds; /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
*/ private String authorizerType; @@ -73,24 +84,37 @@ public class UpdateAuthorizerRequest extends com.amazonaws.AmazonWebServiceReque * */ private String authorizerUri; + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must + * return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. + * Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ */ + private Boolean enableSimpleResponses; /** ** The identity source for which authorization is requested. *
** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
*/ private java.util.List* Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM * role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on - * the Lambda function, specify null. + * the Lambda function, don't specify this parameter. *
* * @param authorizerCredentialsArn * Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an * IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based - * permissions on the Lambda function, specify null. + * permissions on the Lambda function, don't specify this parameter. */ public void setAuthorizerCredentialsArn(String authorizerCredentialsArn) { @@ -175,12 +199,12 @@ public void setAuthorizerCredentialsArn(String authorizerCredentialsArn) { ** Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM * role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on - * the Lambda function, specify null. + * the Lambda function, don't specify this parameter. *
* * @return Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an * IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based - * permissions on the Lambda function, specify null. + * permissions on the Lambda function, don't specify this parameter. */ public String getAuthorizerCredentialsArn() { @@ -191,13 +215,13 @@ public String getAuthorizerCredentialsArn() { ** Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM * role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on - * the Lambda function, specify null. + * the Lambda function, don't specify this parameter. *
* * @param authorizerCredentialsArn * Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an * IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based - * permissions on the Lambda function, specify null. + * permissions on the Lambda function, don't specify this parameter. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -248,11 +272,73 @@ public UpdateAuthorizerRequest withAuthorizerId(String authorizerId) { /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ * + * @param authorizerPayloadFormatVersion + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. + */ + + public void setAuthorizerPayloadFormatVersion(String authorizerPayloadFormatVersion) { + this.authorizerPayloadFormatVersion = authorizerPayloadFormatVersion; + } + + /** + *+ * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ * + * @return Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. + */ + + public String getAuthorizerPayloadFormatVersion() { + return this.authorizerPayloadFormatVersion; + } + + /** + *+ * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ * + * @param authorizerPayloadFormatVersion + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. + * @return Returns a reference to this object so that method calls can be chained together. + */ + + public UpdateAuthorizerRequest withAuthorizerPayloadFormatVersion(String authorizerPayloadFormatVersion) { + setAuthorizerPayloadFormatVersion(authorizerPayloadFormatVersion); + return this; + } + + /** + *+ * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
* * @param authorizerResultTtlInSeconds - * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or + * 1 hour. Supported only for HTTP API Lambda authorizers. */ public void setAuthorizerResultTtlInSeconds(Integer authorizerResultTtlInSeconds) { @@ -261,10 +347,14 @@ public void setAuthorizerResultTtlInSeconds(Integer authorizerResultTtlInSeconds /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
* - * @return Authorizer caching is not currently supported. Don't specify this value for authorizers. + * @return The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching + * is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, + * or 1 hour. Supported only for HTTP API Lambda authorizers. */ public Integer getAuthorizerResultTtlInSeconds() { @@ -273,11 +363,15 @@ public Integer getAuthorizerResultTtlInSeconds() { /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
* * @param authorizerResultTtlInSeconds - * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or + * 1 hour. Supported only for HTTP API Lambda authorizers. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -288,13 +382,13 @@ public UpdateAuthorizerRequest withAuthorizerResultTtlInSeconds(Integer authoriz /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* * @param authorizerType - * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @see AuthorizerType */ @@ -304,12 +398,12 @@ public void setAuthorizerType(String authorizerType) { /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* - * @return The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * @return The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @see AuthorizerType */ @@ -319,13 +413,13 @@ public String getAuthorizerType() { /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* * @param authorizerType - * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizerType */ @@ -337,13 +431,13 @@ public UpdateAuthorizerRequest withAuthorizerType(String authorizerType) { /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* * @param authorizerType - * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizerType */ @@ -450,41 +544,133 @@ public UpdateAuthorizerRequest withAuthorizerUri(String authorizerUri) { return this; } + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must + * return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. + * Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @param enableSimpleResponses + * Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda + * authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead + * of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs + */ + + public void setEnableSimpleResponses(Boolean enableSimpleResponses) { + this.enableSimpleResponses = enableSimpleResponses; + } + + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must + * return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. + * Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @return Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda + * authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value + * instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs + */ + + public Boolean getEnableSimpleResponses() { + return this.enableSimpleResponses; + } + + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must + * return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. + * Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @param enableSimpleResponses + * Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda + * authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead + * of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs + * @return Returns a reference to this object so that method calls can be chained together. + */ + + public UpdateAuthorizerRequest withEnableSimpleResponses(Boolean enableSimpleResponses) { + setEnableSimpleResponses(enableSimpleResponses); + return this; + } + + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must + * return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. + * Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @return Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda + * authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value + * instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs + */ + + public Boolean isEnableSimpleResponses() { + return this.enableSimpleResponses; + } + /** ** The identity source for which authorization is requested. *
** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
* * @return The identity source for which authorization is requested. ** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, + * see Working with AWS Lambda authorizers for HTTP APIs. *
*
* For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests.
* Currently only header-based and query parameter-based selections are supported, for example
- * "$request.header.Authorization".
+ * $request.header.Authorization.
*/
public java.util.List
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
* * @param identitySource * The identity source for which authorization is requested. ** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see + * + * Working with AWS Lambda authorizers for HTTP APIs. *
*
* For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests.
* Currently only header-based and query parameter-based selections are supported, for example
- * "$request.header.Authorization".
+ * $request.header.Authorization.
*/
public void setIdentitySource(java.util.Collection
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
*
* NOTE: This method appends the values to the existing list (if any). Use
@@ -567,18 +763,22 @@ public void setIdentitySource(java.util.Collection
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see + * + * Working with AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. * Currently only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * $request.header.Authorization. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -598,36 +798,43 @@ public UpdateAuthorizerRequest withIdentitySource(String... identitySource) { *
** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
* * @param identitySource * The identity source for which authorization is requested. ** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see + * + * Working with AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. * Currently only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * $request.header.Authorization. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -780,12 +987,16 @@ public String toString() { sb.append("AuthorizerCredentialsArn: ").append(getAuthorizerCredentialsArn()).append(","); if (getAuthorizerId() != null) sb.append("AuthorizerId: ").append(getAuthorizerId()).append(","); + if (getAuthorizerPayloadFormatVersion() != null) + sb.append("AuthorizerPayloadFormatVersion: ").append(getAuthorizerPayloadFormatVersion()).append(","); if (getAuthorizerResultTtlInSeconds() != null) sb.append("AuthorizerResultTtlInSeconds: ").append(getAuthorizerResultTtlInSeconds()).append(","); if (getAuthorizerType() != null) sb.append("AuthorizerType: ").append(getAuthorizerType()).append(","); if (getAuthorizerUri() != null) sb.append("AuthorizerUri: ").append(getAuthorizerUri()).append(","); + if (getEnableSimpleResponses() != null) + sb.append("EnableSimpleResponses: ").append(getEnableSimpleResponses()).append(","); if (getIdentitySource() != null) sb.append("IdentitySource: ").append(getIdentitySource()).append(","); if (getIdentityValidationExpression() != null) @@ -820,6 +1031,11 @@ public boolean equals(Object obj) { return false; if (other.getAuthorizerId() != null && other.getAuthorizerId().equals(this.getAuthorizerId()) == false) return false; + if (other.getAuthorizerPayloadFormatVersion() == null ^ this.getAuthorizerPayloadFormatVersion() == null) + return false; + if (other.getAuthorizerPayloadFormatVersion() != null + && other.getAuthorizerPayloadFormatVersion().equals(this.getAuthorizerPayloadFormatVersion()) == false) + return false; if (other.getAuthorizerResultTtlInSeconds() == null ^ this.getAuthorizerResultTtlInSeconds() == null) return false; if (other.getAuthorizerResultTtlInSeconds() != null && other.getAuthorizerResultTtlInSeconds().equals(this.getAuthorizerResultTtlInSeconds()) == false) @@ -832,6 +1048,10 @@ public boolean equals(Object obj) { return false; if (other.getAuthorizerUri() != null && other.getAuthorizerUri().equals(this.getAuthorizerUri()) == false) return false; + if (other.getEnableSimpleResponses() == null ^ this.getEnableSimpleResponses() == null) + return false; + if (other.getEnableSimpleResponses() != null && other.getEnableSimpleResponses().equals(this.getEnableSimpleResponses()) == false) + return false; if (other.getIdentitySource() == null ^ this.getIdentitySource() == null) return false; if (other.getIdentitySource() != null && other.getIdentitySource().equals(this.getIdentitySource()) == false) @@ -859,9 +1079,11 @@ public int hashCode() { hashCode = prime * hashCode + ((getApiId() == null) ? 0 : getApiId().hashCode()); hashCode = prime * hashCode + ((getAuthorizerCredentialsArn() == null) ? 0 : getAuthorizerCredentialsArn().hashCode()); hashCode = prime * hashCode + ((getAuthorizerId() == null) ? 0 : getAuthorizerId().hashCode()); + hashCode = prime * hashCode + ((getAuthorizerPayloadFormatVersion() == null) ? 0 : getAuthorizerPayloadFormatVersion().hashCode()); hashCode = prime * hashCode + ((getAuthorizerResultTtlInSeconds() == null) ? 0 : getAuthorizerResultTtlInSeconds().hashCode()); hashCode = prime * hashCode + ((getAuthorizerType() == null) ? 0 : getAuthorizerType().hashCode()); hashCode = prime * hashCode + ((getAuthorizerUri() == null) ? 0 : getAuthorizerUri().hashCode()); + hashCode = prime * hashCode + ((getEnableSimpleResponses() == null) ? 0 : getEnableSimpleResponses().hashCode()); hashCode = prime * hashCode + ((getIdentitySource() == null) ? 0 : getIdentitySource().hashCode()); hashCode = prime * hashCode + ((getIdentityValidationExpression() == null) ? 0 : getIdentityValidationExpression().hashCode()); hashCode = prime * hashCode + ((getJwtConfiguration() == null) ? 0 : getJwtConfiguration().hashCode()); diff --git a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/UpdateAuthorizerResult.java b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/UpdateAuthorizerResult.java index d958f10cb44f..1fa16dad4e03 100644 --- a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/UpdateAuthorizerResult.java +++ b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/UpdateAuthorizerResult.java @@ -22,7 +22,7 @@ public class UpdateAuthorizerResult extends com.amazonaws.AmazonWebServiceResult *
* Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM * role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on - * the Lambda function, specify null. Supported only for REQUEST authorizers. + * the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. *
*/ private String authorizerCredentialsArn; @@ -34,20 +34,31 @@ public class UpdateAuthorizerResult extends com.amazonaws.AmazonWebServiceResult private String authorizerId; /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ */ + private String authorizerPayloadFormatVersion; + /** + *+ * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
*/ private Integer authorizerResultTtlInSeconds; /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
*/ private String authorizerType; /** *
- * The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda
+ * The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda
* function URI, for example,
* arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2:
*
+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer + * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ */ + private Boolean enableSimpleResponses; /** ** The identity source for which authorization is requested. *
** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
*/ private java.util.List* Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM * role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on - * the Lambda function, specify null. Supported only for REQUEST authorizers. + * the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. *
* * @param authorizerCredentialsArn * Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an * IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based - * permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. + * permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. */ public void setAuthorizerCredentialsArn(String authorizerCredentialsArn) { @@ -122,12 +145,12 @@ public void setAuthorizerCredentialsArn(String authorizerCredentialsArn) { ** Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM * role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on - * the Lambda function, specify null. Supported only for REQUEST authorizers. + * the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. *
* * @return Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an * IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based - * permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. + * permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. */ public String getAuthorizerCredentialsArn() { @@ -138,13 +161,13 @@ public String getAuthorizerCredentialsArn() { ** Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM * role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on - * the Lambda function, specify null. Supported only for REQUEST authorizers. + * the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. *
* * @param authorizerCredentialsArn * Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an * IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based - * permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. + * permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -195,11 +218,73 @@ public UpdateAuthorizerResult withAuthorizerId(String authorizerId) { /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ * + * @param authorizerPayloadFormatVersion + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. + */ + + public void setAuthorizerPayloadFormatVersion(String authorizerPayloadFormatVersion) { + this.authorizerPayloadFormatVersion = authorizerPayloadFormatVersion; + } + + /** + *+ * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ * + * @return Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. + */ + + public String getAuthorizerPayloadFormatVersion() { + return this.authorizerPayloadFormatVersion; + } + + /** + *+ * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. + *
+ * + * @param authorizerPayloadFormatVersion + * Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda + * authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. + * @return Returns a reference to this object so that method calls can be chained together. + */ + + public UpdateAuthorizerResult withAuthorizerPayloadFormatVersion(String authorizerPayloadFormatVersion) { + setAuthorizerPayloadFormatVersion(authorizerPayloadFormatVersion); + return this; + } + + /** + *+ * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
* * @param authorizerResultTtlInSeconds - * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or + * 1 hour. Supported only for HTTP API Lambda authorizers. */ public void setAuthorizerResultTtlInSeconds(Integer authorizerResultTtlInSeconds) { @@ -208,10 +293,14 @@ public void setAuthorizerResultTtlInSeconds(Integer authorizerResultTtlInSeconds /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
* - * @return Authorizer caching is not currently supported. Don't specify this value for authorizers. + * @return The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching + * is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, + * or 1 hour. Supported only for HTTP API Lambda authorizers. */ public Integer getAuthorizerResultTtlInSeconds() { @@ -220,11 +309,15 @@ public Integer getAuthorizerResultTtlInSeconds() { /** *- * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. + * Supported only for HTTP API Lambda authorizers. *
* * @param authorizerResultTtlInSeconds - * Authorizer caching is not currently supported. Don't specify this value for authorizers. + * The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is + * disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or + * 1 hour. Supported only for HTTP API Lambda authorizers. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -235,13 +328,13 @@ public UpdateAuthorizerResult withAuthorizerResultTtlInSeconds(Integer authorize /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* * @param authorizerType - * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @see AuthorizerType */ @@ -251,12 +344,12 @@ public void setAuthorizerType(String authorizerType) { /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* - * @return The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * @return The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @see AuthorizerType */ @@ -266,13 +359,13 @@ public String getAuthorizerType() { /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* * @param authorizerType - * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizerType */ @@ -284,13 +377,13 @@ public UpdateAuthorizerResult withAuthorizerType(String authorizerType) { /** *- * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. - * For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use + * JSON Web Tokens (supported only for HTTP APIs). *
* * @param authorizerType - * The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request - * parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. + * The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT + * to use JSON Web Tokens (supported only for HTTP APIs). * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizerType */ @@ -302,7 +395,7 @@ public UpdateAuthorizerResult withAuthorizerType(AuthorizerType authorizerType) /** *
- * The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda
+ * The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda
* function URI, for example,
* arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2:
*
- * The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda
+ * The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda
* function URI, for example,
* arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2:
*
- * The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda
+ * The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda
* function URI, for example,
* arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2:
*
+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer + * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @param enableSimpleResponses + * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda + * authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn + * more, see Working with AWS Lambda authorizers for HTTP APIs + */ + + public void setEnableSimpleResponses(Boolean enableSimpleResponses) { + this.enableSimpleResponses = enableSimpleResponses; + } + + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer + * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @return Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda + * authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn + * more, see Working with AWS Lambda authorizers for HTTP APIs + */ + + public Boolean getEnableSimpleResponses() { + return this.enableSimpleResponses; + } + + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer + * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @param enableSimpleResponses + * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda + * authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn + * more, see Working with AWS Lambda authorizers for HTTP APIs + * @return Returns a reference to this object so that method calls can be chained together. + */ + + public UpdateAuthorizerResult withEnableSimpleResponses(Boolean enableSimpleResponses) { + setEnableSimpleResponses(enableSimpleResponses); + return this; + } + + /** + *+ * Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer + * can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs + *
+ * + * @return Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda + * authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn + * more, see Working with AWS Lambda authorizers for HTTP APIs + */ + + public Boolean isEnableSimpleResponses() { + return this.enableSimpleResponses; + } + /** ** The identity source for which authorization is requested. *
** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
* * @return The identity source for which authorization is requested. ** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, + * see Working with AWS Lambda authorizers for HTTP APIs. *
*
* For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests.
* Currently only header-based and query parameter-based selections are supported, for example
- * "$request.header.Authorization".
+ * $request.header.Authorization.
*/
public java.util.List
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
* * @param identitySource * The identity source for which authorization is requested. ** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see + * + * Working with AWS Lambda authorizers for HTTP APIs. *
*
* For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests.
* Currently only header-based and query parameter-based selections are supported, for example
- * "$request.header.Authorization".
+ * $request.header.Authorization.
*/
public void setIdentitySource(java.util.Collection
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
*
* NOTE: This method appends the values to the existing list (if any). Use
@@ -514,18 +705,22 @@ public void setIdentitySource(java.util.Collection
* For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see + * + * Working with AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. * Currently only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * $request.header.Authorization. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -545,36 +740,43 @@ public UpdateAuthorizerResult withIdentitySource(String... identitySource) { *
** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, stage - * variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined - * as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters - * will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related - * request parameters are present in the request, not null, and non-empty. Only when this is true does the - * authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without - * calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage variables, and + * context parameters. For example, if an Auth header and a Name query string parameter are defined as identity + * sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP + * APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. + * These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the + * identity-related request parameters are present in the request, not null, and non-empty. Only when this is true + * does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response + * without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching + * is enabled. To learn more, see Working with + * AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently - * only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * only header-based and query parameter-based selections are supported, for example $request.header.Authorization. *
* * @param identitySource * The identity source for which authorization is requested. ** For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the - * specified request parameters. Currently, the identity source can be headers, query string parameters, - * stage variables, and context parameters. For example, if an Auth header and a Name query string parameter - * are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. - * These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all - * of the identity-related request parameters are present in the request, not null, and non-empty. Only when - * this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 - * Unauthorized response without calling the Lambda function. + * specified request parameters. The identity source can be headers, query string parameters, stage + * variables, and context parameters. For example, if an Auth header and a Name query string parameter are + * defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for + * WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, + * $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation + * for Lambda-based authorizers by verifying all of the identity-related request parameters are present in + * the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer + * Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. + * For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see + * + * Working with AWS Lambda authorizers for HTTP APIs. *
** For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. * Currently only header-based and query parameter-based selections are supported, for example - * "$request.header.Authorization". + * $request.header.Authorization. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -725,12 +927,16 @@ public String toString() { sb.append("AuthorizerCredentialsArn: ").append(getAuthorizerCredentialsArn()).append(","); if (getAuthorizerId() != null) sb.append("AuthorizerId: ").append(getAuthorizerId()).append(","); + if (getAuthorizerPayloadFormatVersion() != null) + sb.append("AuthorizerPayloadFormatVersion: ").append(getAuthorizerPayloadFormatVersion()).append(","); if (getAuthorizerResultTtlInSeconds() != null) sb.append("AuthorizerResultTtlInSeconds: ").append(getAuthorizerResultTtlInSeconds()).append(","); if (getAuthorizerType() != null) sb.append("AuthorizerType: ").append(getAuthorizerType()).append(","); if (getAuthorizerUri() != null) sb.append("AuthorizerUri: ").append(getAuthorizerUri()).append(","); + if (getEnableSimpleResponses() != null) + sb.append("EnableSimpleResponses: ").append(getEnableSimpleResponses()).append(","); if (getIdentitySource() != null) sb.append("IdentitySource: ").append(getIdentitySource()).append(","); if (getIdentityValidationExpression() != null) @@ -761,6 +967,11 @@ public boolean equals(Object obj) { return false; if (other.getAuthorizerId() != null && other.getAuthorizerId().equals(this.getAuthorizerId()) == false) return false; + if (other.getAuthorizerPayloadFormatVersion() == null ^ this.getAuthorizerPayloadFormatVersion() == null) + return false; + if (other.getAuthorizerPayloadFormatVersion() != null + && other.getAuthorizerPayloadFormatVersion().equals(this.getAuthorizerPayloadFormatVersion()) == false) + return false; if (other.getAuthorizerResultTtlInSeconds() == null ^ this.getAuthorizerResultTtlInSeconds() == null) return false; if (other.getAuthorizerResultTtlInSeconds() != null && other.getAuthorizerResultTtlInSeconds().equals(this.getAuthorizerResultTtlInSeconds()) == false) @@ -773,6 +984,10 @@ public boolean equals(Object obj) { return false; if (other.getAuthorizerUri() != null && other.getAuthorizerUri().equals(this.getAuthorizerUri()) == false) return false; + if (other.getEnableSimpleResponses() == null ^ this.getEnableSimpleResponses() == null) + return false; + if (other.getEnableSimpleResponses() != null && other.getEnableSimpleResponses().equals(this.getEnableSimpleResponses()) == false) + return false; if (other.getIdentitySource() == null ^ this.getIdentitySource() == null) return false; if (other.getIdentitySource() != null && other.getIdentitySource().equals(this.getIdentitySource()) == false) @@ -799,9 +1014,11 @@ public int hashCode() { hashCode = prime * hashCode + ((getAuthorizerCredentialsArn() == null) ? 0 : getAuthorizerCredentialsArn().hashCode()); hashCode = prime * hashCode + ((getAuthorizerId() == null) ? 0 : getAuthorizerId().hashCode()); + hashCode = prime * hashCode + ((getAuthorizerPayloadFormatVersion() == null) ? 0 : getAuthorizerPayloadFormatVersion().hashCode()); hashCode = prime * hashCode + ((getAuthorizerResultTtlInSeconds() == null) ? 0 : getAuthorizerResultTtlInSeconds().hashCode()); hashCode = prime * hashCode + ((getAuthorizerType() == null) ? 0 : getAuthorizerType().hashCode()); hashCode = prime * hashCode + ((getAuthorizerUri() == null) ? 0 : getAuthorizerUri().hashCode()); + hashCode = prime * hashCode + ((getEnableSimpleResponses() == null) ? 0 : getEnableSimpleResponses().hashCode()); hashCode = prime * hashCode + ((getIdentitySource() == null) ? 0 : getIdentitySource().hashCode()); hashCode = prime * hashCode + ((getIdentityValidationExpression() == null) ? 0 : getIdentityValidationExpression().hashCode()); hashCode = prime * hashCode + ((getJwtConfiguration() == null) ? 0 : getJwtConfiguration().hashCode()); diff --git a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/UpdateRouteRequest.java b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/UpdateRouteRequest.java index 39317ff1a0ad..717c6171c16f 100644 --- a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/UpdateRouteRequest.java +++ b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/UpdateRouteRequest.java @@ -47,7 +47,8 @@ public class UpdateRouteRequest extends com.amazonaws.AmazonWebServiceRequest im *
* The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
*/ private String authorizationType; @@ -273,13 +274,15 @@ public UpdateRouteRequest withAuthorizationScopes(java.util.Collection* The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @param authorizationType * The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for + * using a Lambda authorizer. * @see AuthorizationType */ @@ -291,12 +294,14 @@ public void setAuthorizationType(String authorizationType) { ** The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @return The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM + * for using a Lambda authorizer. * @see AuthorizationType */ @@ -308,13 +313,15 @@ public String getAuthorizationType() { ** The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @param authorizationType * The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for + * using a Lambda authorizer. * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizationType */ @@ -328,13 +335,15 @@ public UpdateRouteRequest withAuthorizationType(String authorizationType) { ** The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @param authorizationType * The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for + * using a Lambda authorizer. * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizationType */ diff --git a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/UpdateRouteResult.java b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/UpdateRouteResult.java index 1350ba6b6043..ec037e434033 100644 --- a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/UpdateRouteResult.java +++ b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/UpdateRouteResult.java @@ -45,7 +45,8 @@ public class UpdateRouteResult extends com.amazonaws.AmazonWebServiceResult* The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @param authorizationType * The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for + * using a Lambda authorizer. * @see AuthorizationType */ @@ -345,12 +348,14 @@ public void setAuthorizationType(String authorizationType) { ** The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @return The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM + * for using a Lambda authorizer. * @see AuthorizationType */ @@ -362,13 +367,15 @@ public String getAuthorizationType() { ** The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @param authorizationType * The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for + * using a Lambda authorizer. * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizationType */ @@ -382,13 +389,15 @@ public UpdateRouteResult withAuthorizationType(String authorizationType) { ** The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for * using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open - * access, or JWT for using JSON Web Tokens. + * access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda + * authorizer. *
* * @param authorizationType * The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM * for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are - * NONE for open access, or JWT for using JSON Web Tokens. + * NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for + * using a Lambda authorizer. * @return Returns a reference to this object so that method calls can be chained together. * @see AuthorizationType */ diff --git a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/transform/AuthorizerJsonUnmarshaller.java b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/transform/AuthorizerJsonUnmarshaller.java index 66c07f43a82a..649099f0071a 100644 --- a/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/transform/AuthorizerJsonUnmarshaller.java +++ b/aws-java-sdk-apigatewayv2/src/main/java/com/amazonaws/services/apigatewayv2/model/transform/AuthorizerJsonUnmarshaller.java @@ -56,6 +56,10 @@ public Authorizer unmarshall(JsonUnmarshallerContext context) throws Exception { context.nextToken(); authorizer.setAuthorizerId(context.getUnmarshaller(String.class).unmarshall(context)); } + if (context.testExpression("authorizerPayloadFormatVersion", targetDepth)) { + context.nextToken(); + authorizer.setAuthorizerPayloadFormatVersion(context.getUnmarshaller(String.class).unmarshall(context)); + } if (context.testExpression("authorizerResultTtlInSeconds", targetDepth)) { context.nextToken(); authorizer.setAuthorizerResultTtlInSeconds(context.getUnmarshaller(Integer.class).unmarshall(context)); @@ -68,6 +72,10 @@ public Authorizer unmarshall(JsonUnmarshallerContext context) throws Exception { context.nextToken(); authorizer.setAuthorizerUri(context.getUnmarshaller(String.class).unmarshall(context)); } + if (context.testExpression("enableSimpleResponses", targetDepth)) { + context.nextToken(); + authorizer.setEnableSimpleResponses(context.getUnmarshaller(Boolean.class).unmarshall(context)); + } if (context.testExpression("identitySource", targetDepth)) { context.nextToken(); authorizer.setIdentitySource(new ListUnmarshaller
- * DeleteReportGroup: Deletes a report group. Before you delete a report group, you must delete its
- * reports. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete
- * the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an
- * exception is thrown.
+ * Deletes a report group. Before you delete a report group, you must delete its reports.
*
- * DeleteReportGroup: Deletes a report group. Before you delete a report group, you must delete its
- * reports. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete
- * the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an
- * exception is thrown.
+ * Deletes a report group. Before you delete a report group, you must delete its reports.
*
- * DeleteReportGroup: Deletes a report group. Before you delete a report group, you must delete its
- * reports. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete
- * the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an
- * exception is thrown.
+ * Deletes a report group. Before you delete a report group, you must delete its reports.
*
- * DeleteReportGroup: Deletes a report group. Before you delete a report group, you must delete its
- * reports. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete
- * the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an
- * exception is thrown.
+ * Deletes a report group. Before you delete a report group, you must delete its reports.
*
+ * If true, deletes any reports that belong to a report group before deleting the report group.
+ *
+ * If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete
+ * the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an
+ * exception is thrown.
+ *
@@ -72,6 +86,122 @@ public DeleteReportGroupRequest withArn(String arn) { return this; } + /** + *
+ * If true, deletes any reports that belong to a report group before deleting the report group.
+ *
+ * If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete
+ * the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an
+ * exception is thrown.
+ *
true, deletes any reports that belong to a report group before deleting the report group.
+ *
+ *
+ * If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to
+ * delete the reports. If you call DeleteReportGroup for a report group that contains one or
+ * more reports, an exception is thrown.
+ */
+
+ public void setDeleteReports(Boolean deleteReports) {
+ this.deleteReports = deleteReports;
+ }
+
+ /**
+ *
+ * If true, deletes any reports that belong to a report group before deleting the report group.
+ *
+ * If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete
+ * the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an
+ * exception is thrown.
+ *
true, deletes any reports that belong to a report group before deleting the report group.
+ *
+ *
+ * If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport
+ * to delete the reports. If you call DeleteReportGroup for a report group that contains one or
+ * more reports, an exception is thrown.
+ */
+
+ public Boolean getDeleteReports() {
+ return this.deleteReports;
+ }
+
+ /**
+ *
+ * If true, deletes any reports that belong to a report group before deleting the report group.
+ *
+ * If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete
+ * the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an
+ * exception is thrown.
+ *
true, deletes any reports that belong to a report group before deleting the report group.
+ *
+ *
+ * If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to
+ * delete the reports. If you call DeleteReportGroup for a report group that contains one or
+ * more reports, an exception is thrown.
+ * @return Returns a reference to this object so that method calls can be chained together.
+ */
+
+ public DeleteReportGroupRequest withDeleteReports(Boolean deleteReports) {
+ setDeleteReports(deleteReports);
+ return this;
+ }
+
+ /**
+ *
+ * If true, deletes any reports that belong to a report group before deleting the report group.
+ *
+ * If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete
+ * the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an
+ * exception is thrown.
+ *
true, deletes any reports that belong to a report group before deleting the report group.
+ *
+ *
+ * If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport
+ * to delete the reports. If you call DeleteReportGroup for a report group that contains one or
+ * more reports, an exception is thrown.
+ */
+
+ public Boolean isDeleteReports() {
+ return this.deleteReports;
+ }
+
/**
* Returns a string representation of this object. This is useful for testing and debugging. Sensitive data will be
* redacted from this string using a placeholder value.
@@ -85,7 +215,9 @@ public String toString() {
StringBuilder sb = new StringBuilder();
sb.append("{");
if (getArn() != null)
- sb.append("Arn: ").append(getArn());
+ sb.append("Arn: ").append(getArn()).append(",");
+ if (getDeleteReports() != null)
+ sb.append("DeleteReports: ").append(getDeleteReports());
sb.append("}");
return sb.toString();
}
@@ -104,6 +236,10 @@ public boolean equals(Object obj) {
return false;
if (other.getArn() != null && other.getArn().equals(this.getArn()) == false)
return false;
+ if (other.getDeleteReports() == null ^ this.getDeleteReports() == null)
+ return false;
+ if (other.getDeleteReports() != null && other.getDeleteReports().equals(this.getDeleteReports()) == false)
+ return false;
return true;
}
@@ -113,6 +249,7 @@ public int hashCode() {
int hashCode = 1;
hashCode = prime * hashCode + ((getArn() == null) ? 0 : getArn().hashCode());
+ hashCode = prime * hashCode + ((getDeleteReports() == null) ? 0 : getDeleteReports().hashCode());
return hashCode;
}
diff --git a/aws-java-sdk-codebuild/src/main/java/com/amazonaws/services/codebuild/model/EnvironmentVariable.java b/aws-java-sdk-codebuild/src/main/java/com/amazonaws/services/codebuild/model/EnvironmentVariable.java
index b6a854f1371a..a8872e7a0d60 100644
--- a/aws-java-sdk-codebuild/src/main/java/com/amazonaws/services/codebuild/model/EnvironmentVariable.java
+++ b/aws-java-sdk-codebuild/src/main/java/com/amazonaws/services/codebuild/model/EnvironmentVariable.java
@@ -57,9 +57,9 @@ public class EnvironmentVariable implements Serializable, Cloneable, StructuredP
*
* PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To
- * learn how to specify a parameter store environment variable, see
- * parameter store reference-key in the buildspec file.
+ * learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
*
* SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a
- * secrets manager environment variable, see
- * secrets manager reference-key in the buildspec file.
+ * secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
*
* PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To
- * learn how to specify a parameter store environment variable, see
- * parameter store reference-key in the buildspec file.
+ * learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
*
* SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a
- * secrets manager environment variable, see
- * secrets manager reference-key in the buildspec file.
+ * secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
*
* PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter
* Store. To learn how to specify a parameter store environment variable, see
- * parameter store reference-key in the buildspec file.
+ * "https://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html#build-spec.env.parameter-store"
+ * >env/parameter-store in the AWS CodeBuild User Guide.
*
* SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to
* specify a secrets manager environment variable, see
- * secrets manager reference-key in the buildspec file.
+ * "https://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html#build-spec.env.secrets-manager"
+ * >env/secrets-manager in the AWS CodeBuild User Guide.
*
* PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To
- * learn how to specify a parameter store environment variable, see
- * parameter store reference-key in the buildspec file.
+ * learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
*
* SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a
- * secrets manager environment variable, see
- * secrets manager reference-key in the buildspec file.
+ * secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
*
* PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter
* Store. To learn how to specify a parameter store environment variable, see
- * parameter store reference-key in the buildspec file.
+ * "https://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html#build-spec.env.parameter-store"
+ * >env/parameter-store in the AWS CodeBuild User Guide.
*
* SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to
* specify a secrets manager environment variable, see
- * secrets manager reference-key in the buildspec file.
+ * "https://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html#build-spec.env.secrets-manager"
+ * >env/secrets-manager in the AWS CodeBuild User Guide.
*
* PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To
- * learn how to specify a parameter store environment variable, see
- * parameter store reference-key in the buildspec file.
+ * learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
*
* SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a
- * secrets manager environment variable, see
- * secrets manager reference-key in the buildspec file.
+ * secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
*
* PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter
* Store. To learn how to specify a parameter store environment variable, see
- * parameter store reference-key in the buildspec file.
+ * "https://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html#build-spec.env.parameter-store"
+ * >env/parameter-store in the AWS CodeBuild User Guide.
*
* SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to
* specify a secrets manager environment variable, see
- * secrets manager reference-key in the buildspec file.
+ * "https://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html#build-spec.env.secrets-manager"
+ * >env/secrets-manager in the AWS CodeBuild User Guide.
*
* PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To
- * learn how to specify a parameter store environment variable, see
- * parameter store reference-key in the buildspec file.
+ * learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
*
* SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a
- * secrets manager environment variable, see
- * secrets manager reference-key in the buildspec file.
+ * secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
*
* PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter
* Store. To learn how to specify a parameter store environment variable, see
- * parameter store reference-key in the buildspec file.
+ * "https://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html#build-spec.env.parameter-store"
+ * >env/parameter-store in the AWS CodeBuild User Guide.
*
* SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to
* specify a secrets manager environment variable, see
- * secrets manager reference-key in the buildspec file.
+ * "https://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html#build-spec.env.secrets-manager"
+ * >env/secrets-manager in the AWS CodeBuild User Guide.
*
- * For an image tag: registry/repository:tag. For example, to specify an image with the tag "latest,"
- * use registry/repository:latest.
+ * For an image tag: <registry>/<repository>:<tag>. For example, in the Docker
+ * repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0
+ * . To specify the latest version of this image, this would be aws/codebuild/standard:latest.
*
- * For an image digest: registry/repository@digest. For example, to specify an image with the digest
- * "sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf," use
- * registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
+ * For an image digest: <registry>/<repository>@<digest>. For example, to specify an
+ * image with the digest "sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf," use
+ * <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf
+ * .
*
- * For an image tag: registry/repository:tag. For example, to specify an image with the tag "latest,"
- * use registry/repository:latest.
+ * For an image tag: <registry>/<repository>:<tag>. For example, in the Docker
+ * repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0
+ * . To specify the latest version of this image, this would be aws/codebuild/standard:latest.
*
- * For an image digest: registry/repository@digest. For example, to specify an image with the digest
- * "sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf," use
- * registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
+ * For an image digest: <registry>/<repository>@<digest>. For example, to specify an
+ * image with the digest "sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf," use
+ * <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf
+ * .
*
- * For an image tag: registry/repository:tag. For example, to specify an image with the tag
- * "latest," use registry/repository:latest.
+ * For an image tag: <registry>/<repository>:<tag>. For example, in the Docker
+ * repository that CodeBuild uses to manage its Docker images, this would be
+ * aws/codebuild/standard:4.0. To specify the latest version of this image, this would be
+ * aws/codebuild/standard:latest.
*
- * For an image digest: registry/repository@digest. For example, to specify an image with the
- * digest "sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf," use
- * registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
+ * For an image digest: <registry>/<repository>@<digest>. For example, to
+ * specify an image with the digest
+ * "sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf," use
+ * <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf
+ * .
*
- * For an image tag: registry/repository:tag. For example, to specify an image with the tag "latest,"
- * use registry/repository:latest.
+ * For an image tag: <registry>/<repository>:<tag>. For example, in the Docker
+ * repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0
+ * . To specify the latest version of this image, this would be aws/codebuild/standard:latest.
*
- * For an image digest: registry/repository@digest. For example, to specify an image with the digest
- * "sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf," use
- * registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
+ * For an image digest: <registry>/<repository>@<digest>. For example, to specify an
+ * image with the digest "sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf," use
+ * <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf
+ * .
*
- * For an image tag: registry/repository:tag. For example, to specify an image with the tag
- * "latest," use registry/repository:latest.
+ * For an image tag: <registry>/<repository>:<tag>. For example, in the
+ * Docker repository that CodeBuild uses to manage its Docker images, this would be
+ * aws/codebuild/standard:4.0. To specify the latest version of this image, this would be
+ * aws/codebuild/standard:latest.
*
- * For an image digest: registry/repository@digest. For example, to specify an image with the
- * digest "sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf," use
- * registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
+ * For an image digest: <registry>/<repository>@<digest>. For example, to
+ * specify an image with the digest
+ * "sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf," use
+ * <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf
+ * .
*
- * For an image tag: registry/repository:tag. For example, to specify an image with the tag "latest,"
- * use registry/repository:latest.
+ * For an image tag: <registry>/<repository>:<tag>. For example, in the Docker
+ * repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0
+ * . To specify the latest version of this image, this would be aws/codebuild/standard:latest.
*
- * For an image digest: registry/repository@digest. For example, to specify an image with the digest
- * "sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf," use
- * registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
+ * For an image digest: <registry>/<repository>@<digest>. For example, to specify an
+ * image with the digest "sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf," use
+ * <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf
+ * .
*
- * For an image tag: registry/repository:tag. For example, to specify an image with the tag
- * "latest," use registry/repository:latest.
+ * For an image tag: <registry>/<repository>:<tag>. For example, in the Docker
+ * repository that CodeBuild uses to manage its Docker images, this would be
+ * aws/codebuild/standard:4.0. To specify the latest version of this image, this would be
+ * aws/codebuild/standard:latest.
*
- * For an image digest: registry/repository@digest. For example, to specify an image with the
- * digest "sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf," use
- * registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
+ * For an image digest: <registry>/<repository>@<digest>. For example, to
+ * specify an image with the digest
+ * "sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf," use
+ * <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf
+ * .
*
- * A filter used to return specific types of test cases. + * A filter used to return specific types of test cases. In order to pass the filter, the report must meet all of the + * filter properties. *
* * @see AWS API @@ -30,24 +31,106 @@ public class TestCaseFilter implements Serializable, Cloneable, StructuredPojo { /** *
- * The status used to filter test cases. Valid statuses are SUCCEEDED, FAILED,
- * ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one
- * status.
+ * The status used to filter test cases. A TestCaseFilter can have one status. Valid values are:
*
+ * SUCCEEDED
+ *
+ * FAILED
+ *
+ * ERROR
+ *
+ * SKIPPED
+ *
+ * UNKNOWN
+ *
+ * A keyword that is used to filter on the name or the prefix of the test cases. Only test
+ * cases where the keyword is a substring of the name or the prefix will be returned.
+ *
- * The status used to filter test cases. Valid statuses are SUCCEEDED, FAILED,
- * ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one
- * status.
+ * The status used to filter test cases. A TestCaseFilter can have one status. Valid values are:
+ *
+ * SUCCEEDED
+ *
+ * FAILED
*
+ * ERROR
+ *
+ * SKIPPED
+ *
+ * UNKNOWN
+ *
SUCCEEDED, FAILED,
- * ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have
- * one status.
+ * The status used to filter test cases. A TestCaseFilter can have one status. Valid values
+ * are:
+ *
+ * SUCCEEDED
+ *
+ * FAILED
+ *
+ * ERROR
+ *
+ * SKIPPED
+ *
+ * UNKNOWN
+ *
- * The status used to filter test cases. Valid statuses are SUCCEEDED, FAILED,
- * ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one
- * status.
+ * The status used to filter test cases. A TestCaseFilter can have one status. Valid values are:
+ *
+ * SUCCEEDED
+ *
+ * FAILED
+ *
+ * ERROR
+ *
+ * SKIPPED
*
+ * UNKNOWN
+ *
SUCCEEDED, FAILED,
- * ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can
- * have one status.
+ * @return The status used to filter test cases. A TestCaseFilter can have one status. Valid values
+ * are:
+ *
+ * SUCCEEDED
+ *
+ * FAILED
+ *
+ * ERROR
+ *
+ * SKIPPED
+ *
+ * UNKNOWN
+ *
- * The status used to filter test cases. Valid statuses are SUCCEEDED, FAILED,
- * ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one
- * status.
+ * The status used to filter test cases. A TestCaseFilter can have one status. Valid values are:
+ *
+ * SUCCEEDED
*
+ * FAILED
+ *
+ * ERROR
+ *
+ * SKIPPED
+ *
+ * UNKNOWN
+ *
SUCCEEDED, FAILED,
- * ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have
- * one status.
+ * The status used to filter test cases. A TestCaseFilter can have one status. Valid values
+ * are:
+ *
+ * SUCCEEDED
+ *
+ * FAILED
+ *
+ * ERROR
+ *
+ * SKIPPED
+ *
+ * UNKNOWN
+ *
+ * A keyword that is used to filter on the name or the prefix of the test cases. Only test
+ * cases where the keyword is a substring of the name or the prefix will be returned.
+ *
name or the prefix of the test cases.
+ * Only test cases where the keyword is a substring of the name or the prefix will
+ * be returned.
+ */
+
+ public void setKeyword(String keyword) {
+ this.keyword = keyword;
+ }
+
+ /**
+ *
+ * A keyword that is used to filter on the name or the prefix of the test cases. Only test
+ * cases where the keyword is a substring of the name or the prefix will be returned.
+ *
name or the prefix of the test cases.
+ * Only test cases where the keyword is a substring of the name or the prefix will
+ * be returned.
+ */
+
+ public String getKeyword() {
+ return this.keyword;
+ }
+
+ /**
+ *
+ * A keyword that is used to filter on the name or the prefix of the test cases. Only test
+ * cases where the keyword is a substring of the name or the prefix will be returned.
+ *
name or the prefix of the test cases.
+ * Only test cases where the keyword is a substring of the name or the prefix will
+ * be returned.
+ * @return Returns a reference to this object so that method calls can be chained together.
+ */
+
+ public TestCaseFilter withKeyword(String keyword) {
+ setKeyword(keyword);
+ return this;
+ }
+
/**
* Returns a string representation of this object. This is useful for testing and debugging. Sensitive data will be
* redacted from this string using a placeholder value.
@@ -102,7 +334,9 @@ public String toString() {
StringBuilder sb = new StringBuilder();
sb.append("{");
if (getStatus() != null)
- sb.append("Status: ").append(getStatus());
+ sb.append("Status: ").append(getStatus()).append(",");
+ if (getKeyword() != null)
+ sb.append("Keyword: ").append(getKeyword());
sb.append("}");
return sb.toString();
}
@@ -121,6 +355,10 @@ public boolean equals(Object obj) {
return false;
if (other.getStatus() != null && other.getStatus().equals(this.getStatus()) == false)
return false;
+ if (other.getKeyword() == null ^ this.getKeyword() == null)
+ return false;
+ if (other.getKeyword() != null && other.getKeyword().equals(this.getKeyword()) == false)
+ return false;
return true;
}
@@ -130,6 +368,7 @@ public int hashCode() {
int hashCode = 1;
hashCode = prime * hashCode + ((getStatus() == null) ? 0 : getStatus().hashCode());
+ hashCode = prime * hashCode + ((getKeyword() == null) ? 0 : getKeyword().hashCode());
return hashCode;
}
diff --git a/aws-java-sdk-codebuild/src/main/java/com/amazonaws/services/codebuild/model/transform/DeleteReportGroupRequestMarshaller.java b/aws-java-sdk-codebuild/src/main/java/com/amazonaws/services/codebuild/model/transform/DeleteReportGroupRequestMarshaller.java
index 9bf94f35a0e2..2b7908a06c3d 100644
--- a/aws-java-sdk-codebuild/src/main/java/com/amazonaws/services/codebuild/model/transform/DeleteReportGroupRequestMarshaller.java
+++ b/aws-java-sdk-codebuild/src/main/java/com/amazonaws/services/codebuild/model/transform/DeleteReportGroupRequestMarshaller.java
@@ -29,6 +29,8 @@ public class DeleteReportGroupRequestMarshaller {
private static final MarshallingInfo+ * [Application Load Balancers on Outposts] The ID of the Outpost. + *
+ */ + private String outpostId; /** ** [Network Load Balancers] If you need static IP addresses for your load balancer, you can specify one Elastic IP @@ -127,6 +133,46 @@ public AvailabilityZone withSubnetId(String subnetId) { return this; } + /** + *
+ * [Application Load Balancers on Outposts] The ID of the Outpost. + *
+ * + * @param outpostId + * [Application Load Balancers on Outposts] The ID of the Outpost. + */ + + public void setOutpostId(String outpostId) { + this.outpostId = outpostId; + } + + /** + *+ * [Application Load Balancers on Outposts] The ID of the Outpost. + *
+ * + * @return [Application Load Balancers on Outposts] The ID of the Outpost. + */ + + public String getOutpostId() { + return this.outpostId; + } + + /** + *+ * [Application Load Balancers on Outposts] The ID of the Outpost. + *
+ * + * @param outpostId + * [Application Load Balancers on Outposts] The ID of the Outpost. + * @return Returns a reference to this object so that method calls can be chained together. + */ + + public AvailabilityZone withOutpostId(String outpostId) { + setOutpostId(outpostId); + return this; + } + /** ** [Network Load Balancers] If you need static IP addresses for your load balancer, you can specify one Elastic IP @@ -229,6 +275,8 @@ public String toString() { sb.append("ZoneName: ").append(getZoneName()).append(","); if (getSubnetId() != null) sb.append("SubnetId: ").append(getSubnetId()).append(","); + if (getOutpostId() != null) + sb.append("OutpostId: ").append(getOutpostId()).append(","); if (getLoadBalancerAddresses() != null) sb.append("LoadBalancerAddresses: ").append(getLoadBalancerAddresses()); sb.append("}"); @@ -253,6 +301,10 @@ public boolean equals(Object obj) { return false; if (other.getSubnetId() != null && other.getSubnetId().equals(this.getSubnetId()) == false) return false; + if (other.getOutpostId() == null ^ this.getOutpostId() == null) + return false; + if (other.getOutpostId() != null && other.getOutpostId().equals(this.getOutpostId()) == false) + return false; if (other.getLoadBalancerAddresses() == null ^ this.getLoadBalancerAddresses() == null) return false; if (other.getLoadBalancerAddresses() != null && other.getLoadBalancerAddresses().equals(this.getLoadBalancerAddresses()) == false) @@ -267,6 +319,7 @@ public int hashCode() { hashCode = prime * hashCode + ((getZoneName() == null) ? 0 : getZoneName().hashCode()); hashCode = prime * hashCode + ((getSubnetId() == null) ? 0 : getSubnetId().hashCode()); + hashCode = prime * hashCode + ((getOutpostId() == null) ? 0 : getOutpostId().hashCode()); hashCode = prime * hashCode + ((getLoadBalancerAddresses() == null) ? 0 : getLoadBalancerAddresses().hashCode()); return hashCode; } diff --git a/aws-java-sdk-elasticloadbalancingv2/src/main/java/com/amazonaws/services/elasticloadbalancingv2/model/CreateLoadBalancerRequest.java b/aws-java-sdk-elasticloadbalancingv2/src/main/java/com/amazonaws/services/elasticloadbalancingv2/model/CreateLoadBalancerRequest.java index 72bec0e7a1f2..4f288512d18b 100644 --- a/aws-java-sdk-elasticloadbalancingv2/src/main/java/com/amazonaws/services/elasticloadbalancingv2/model/CreateLoadBalancerRequest.java +++ b/aws-java-sdk-elasticloadbalancingv2/src/main/java/com/amazonaws/services/elasticloadbalancingv2/model/CreateLoadBalancerRequest.java @@ -44,6 +44,12 @@ public class CreateLoadBalancerRequest extends com.amazonaws.AmazonWebServiceReq * [Application Load Balancers] You must specify subnets from at least two Availability Zones. *
*+ * [Application Load Balancers on Outposts] You must specify one Outpost subnet. + *
+ *+ * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. + *
+ ** [Network Load Balancers] You can specify subnets from one or more Availability Zones. *
*/ @@ -58,6 +64,12 @@ public class CreateLoadBalancerRequest extends com.amazonaws.AmazonWebServiceReq * Elastic IP addresses for your subnets. * *+ * [Application Load Balancers on Outposts] You must specify one Outpost subnet. + *
+ *+ * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. + *
+ ** [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic * IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load * balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet. @@ -106,6 +118,12 @@ public class CreateLoadBalancerRequest extends com.amazonaws.AmazonWebServiceReq *
*/ private String ipAddressType; + /** + *+ * [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). + *
+ */ + private String customerOwnedIpv4Pool; /** *@@ -180,6 +198,12 @@ public CreateLoadBalancerRequest withName(String name) { * [Application Load Balancers] You must specify subnets from at least two Availability Zones. *
*+ * [Application Load Balancers on Outposts] You must specify one Outpost subnet. + *
+ *+ * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. + *
+ ** [Network Load Balancers] You can specify subnets from one or more Availability Zones. *
* @@ -189,6 +213,12 @@ public CreateLoadBalancerRequest withName(String name) { * [Application Load Balancers] You must specify subnets from at least two Availability Zones. * *+ * [Application Load Balancers on Outposts] You must specify one Outpost subnet. + *
+ *+ * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. + *
+ *
* [Network Load Balancers] You can specify subnets from one or more Availability Zones.
*/
@@ -205,6 +235,12 @@ public java.util.List
+ * [Application Load Balancers on Outposts] You must specify one Outpost subnet. + *
+ *+ * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. + *
+ ** [Network Load Balancers] You can specify subnets from one or more Availability Zones. *
* @@ -215,6 +251,12 @@ public java.util.List+ * [Application Load Balancers on Outposts] You must specify one Outpost subnet. + *
+ *+ * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. + *
+ *
* [Network Load Balancers] You can specify subnets from one or more Availability Zones.
*/
@@ -236,6 +278,12 @@ public void setSubnets(java.util.Collection
+ * [Application Load Balancers on Outposts] You must specify one Outpost subnet. + *
+ *+ * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. + *
+ ** [Network Load Balancers] You can specify subnets from one or more Availability Zones. *
*
@@ -251,6 +299,12 @@ public void setSubnets(java.util.Collection
+ * [Application Load Balancers on Outposts] You must specify one Outpost subnet. + *
+ *+ * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. + *
+ ** [Network Load Balancers] You can specify subnets from one or more Availability Zones. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -274,6 +328,12 @@ public CreateLoadBalancerRequest withSubnets(String... subnets) { * [Application Load Balancers] You must specify subnets from at least two Availability Zones. *
*+ * [Application Load Balancers on Outposts] You must specify one Outpost subnet. + *
+ *+ * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. + *
+ ** [Network Load Balancers] You can specify subnets from one or more Availability Zones. *
* @@ -284,6 +344,12 @@ public CreateLoadBalancerRequest withSubnets(String... subnets) { * [Application Load Balancers] You must specify subnets from at least two Availability Zones. * *+ * [Application Load Balancers on Outposts] You must specify one Outpost subnet. + *
+ *+ * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. + *
+ *
* [Network Load Balancers] You can specify subnets from one or more Availability Zones.
* @return Returns a reference to this object so that method calls can be chained together.
*/
@@ -303,6 +369,12 @@ public CreateLoadBalancerRequest withSubnets(java.util.Collection
+ * [Application Load Balancers on Outposts] You must specify one Outpost subnet. + *
+ *+ * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. + *
+ *
* [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic
* IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load
* balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
@@ -315,6 +387,12 @@ public CreateLoadBalancerRequest withSubnets(java.util.Collection
+ * [Application Load Balancers on Outposts] You must specify one Outpost subnet. + *
+ *+ * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. + *
+ *
* [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one
* Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For
* internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the
@@ -335,6 +413,12 @@ public java.util.List
+ * [Application Load Balancers on Outposts] You must specify one Outpost subnet. + *
+ *+ * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. + *
+ *
* [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic
* IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load
* balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
@@ -348,6 +432,12 @@ public java.util.List
+ * [Application Load Balancers on Outposts] You must specify one Outpost subnet. + *
+ *+ * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. + *
+ *
* [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one
* Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For
* internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the
@@ -373,6 +463,12 @@ public void setSubnetMappings(java.util.Collection
+ * [Application Load Balancers on Outposts] You must specify one Outpost subnet. + *
+ *+ * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. + *
+ *
* [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic
* IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load
* balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
@@ -391,6 +487,12 @@ public void setSubnetMappings(java.util.Collection
+ * [Application Load Balancers on Outposts] You must specify one Outpost subnet. + *
+ *+ * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. + *
+ ** [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one * Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For * internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the @@ -418,6 +520,12 @@ public CreateLoadBalancerRequest withSubnetMappings(SubnetMapping... subnetMappi * Elastic IP addresses for your subnets. *
*+ * [Application Load Balancers on Outposts] You must specify one Outpost subnet. + *
+ *+ * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. + *
+ ** [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic * IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load * balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet. @@ -431,6 +539,12 @@ public CreateLoadBalancerRequest withSubnetMappings(SubnetMapping... subnetMappi * specify Elastic IP addresses for your subnets. *
*+ * [Application Load Balancers on Outposts] You must specify one Outpost subnet. + *
+ *+ * [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. + *
+ ** [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one * Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For * internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the @@ -917,6 +1031,46 @@ public CreateLoadBalancerRequest withIpAddressType(IpAddressType ipAddressType) return this; } + /** + *
+ * [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). + *
+ * + * @param customerOwnedIpv4Pool + * [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). + */ + + public void setCustomerOwnedIpv4Pool(String customerOwnedIpv4Pool) { + this.customerOwnedIpv4Pool = customerOwnedIpv4Pool; + } + + /** + *+ * [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). + *
+ * + * @return [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). + */ + + public String getCustomerOwnedIpv4Pool() { + return this.customerOwnedIpv4Pool; + } + + /** + *+ * [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). + *
+ * + * @param customerOwnedIpv4Pool + * [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). + * @return Returns a reference to this object so that method calls can be chained together. + */ + + public CreateLoadBalancerRequest withCustomerOwnedIpv4Pool(String customerOwnedIpv4Pool) { + setCustomerOwnedIpv4Pool(customerOwnedIpv4Pool); + return this; + } + /** * Returns a string representation of this object. This is useful for testing and debugging. Sensitive data will be * redacted from this string using a placeholder value. @@ -944,7 +1098,9 @@ public String toString() { if (getType() != null) sb.append("Type: ").append(getType()).append(","); if (getIpAddressType() != null) - sb.append("IpAddressType: ").append(getIpAddressType()); + sb.append("IpAddressType: ").append(getIpAddressType()).append(","); + if (getCustomerOwnedIpv4Pool() != null) + sb.append("CustomerOwnedIpv4Pool: ").append(getCustomerOwnedIpv4Pool()); sb.append("}"); return sb.toString(); } @@ -991,6 +1147,10 @@ public boolean equals(Object obj) { return false; if (other.getIpAddressType() != null && other.getIpAddressType().equals(this.getIpAddressType()) == false) return false; + if (other.getCustomerOwnedIpv4Pool() == null ^ this.getCustomerOwnedIpv4Pool() == null) + return false; + if (other.getCustomerOwnedIpv4Pool() != null && other.getCustomerOwnedIpv4Pool().equals(this.getCustomerOwnedIpv4Pool()) == false) + return false; return true; } @@ -1007,6 +1167,7 @@ public int hashCode() { hashCode = prime * hashCode + ((getTags() == null) ? 0 : getTags().hashCode()); hashCode = prime * hashCode + ((getType() == null) ? 0 : getType().hashCode()); hashCode = prime * hashCode + ((getIpAddressType() == null) ? 0 : getIpAddressType().hashCode()); + hashCode = prime * hashCode + ((getCustomerOwnedIpv4Pool() == null) ? 0 : getCustomerOwnedIpv4Pool().hashCode()); return hashCode; } diff --git a/aws-java-sdk-elasticloadbalancingv2/src/main/java/com/amazonaws/services/elasticloadbalancingv2/model/LoadBalancer.java b/aws-java-sdk-elasticloadbalancingv2/src/main/java/com/amazonaws/services/elasticloadbalancingv2/model/LoadBalancer.java index 3e670141c4d4..6b8004cf5928 100644 --- a/aws-java-sdk-elasticloadbalancingv2/src/main/java/com/amazonaws/services/elasticloadbalancingv2/model/LoadBalancer.java +++ b/aws-java-sdk-elasticloadbalancingv2/src/main/java/com/amazonaws/services/elasticloadbalancingv2/model/LoadBalancer.java @@ -89,7 +89,7 @@ public class LoadBalancer implements Serializable, Cloneable { private String type; /** *- * The Availability Zones for the load balancer. + * The subnets for the load balancer. *
*/ private java.util.List+ * [Application Load Balancers on Outposts] The ID of the customer-owned address pool. + *
+ */ + private String customerOwnedIpv4Pool; /** *@@ -600,10 +606,10 @@ public LoadBalancer withType(LoadBalancerTypeEnum type) { /** *
- * The Availability Zones for the load balancer. + * The subnets for the load balancer. *
* - * @return The Availability Zones for the load balancer. + * @return The subnets for the load balancer. */ public java.util.List- * The Availability Zones for the load balancer. + * The subnets for the load balancer. *
* * @param availabilityZones - * The Availability Zones for the load balancer. + * The subnets for the load balancer. */ public void setAvailabilityZones(java.util.Collection- * The Availability Zones for the load balancer. + * The subnets for the load balancer. *
*
* NOTE: This method appends the values to the existing list (if any). Use
@@ -639,7 +645,7 @@ public void setAvailabilityZones(java.util.Collection
- * The Availability Zones for the load balancer. + * The subnets for the load balancer. *
* * @param availabilityZones - * The Availability Zones for the load balancer. + * The subnets for the load balancer. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -821,6 +827,46 @@ public LoadBalancer withIpAddressType(IpAddressType ipAddressType) { return this; } + /** + *+ * [Application Load Balancers on Outposts] The ID of the customer-owned address pool. + *
+ * + * @param customerOwnedIpv4Pool + * [Application Load Balancers on Outposts] The ID of the customer-owned address pool. + */ + + public void setCustomerOwnedIpv4Pool(String customerOwnedIpv4Pool) { + this.customerOwnedIpv4Pool = customerOwnedIpv4Pool; + } + + /** + *+ * [Application Load Balancers on Outposts] The ID of the customer-owned address pool. + *
+ * + * @return [Application Load Balancers on Outposts] The ID of the customer-owned address pool. + */ + + public String getCustomerOwnedIpv4Pool() { + return this.customerOwnedIpv4Pool; + } + + /** + *+ * [Application Load Balancers on Outposts] The ID of the customer-owned address pool. + *
+ * + * @param customerOwnedIpv4Pool + * [Application Load Balancers on Outposts] The ID of the customer-owned address pool. + * @return Returns a reference to this object so that method calls can be chained together. + */ + + public LoadBalancer withCustomerOwnedIpv4Pool(String customerOwnedIpv4Pool) { + setCustomerOwnedIpv4Pool(customerOwnedIpv4Pool); + return this; + } + /** * Returns a string representation of this object. This is useful for testing and debugging. Sensitive data will be * redacted from this string using a placeholder value. @@ -856,7 +902,9 @@ public String toString() { if (getSecurityGroups() != null) sb.append("SecurityGroups: ").append(getSecurityGroups()).append(","); if (getIpAddressType() != null) - sb.append("IpAddressType: ").append(getIpAddressType()); + sb.append("IpAddressType: ").append(getIpAddressType()).append(","); + if (getCustomerOwnedIpv4Pool() != null) + sb.append("CustomerOwnedIpv4Pool: ").append(getCustomerOwnedIpv4Pool()); sb.append("}"); return sb.toString(); } @@ -919,6 +967,10 @@ public boolean equals(Object obj) { return false; if (other.getIpAddressType() != null && other.getIpAddressType().equals(this.getIpAddressType()) == false) return false; + if (other.getCustomerOwnedIpv4Pool() == null ^ this.getCustomerOwnedIpv4Pool() == null) + return false; + if (other.getCustomerOwnedIpv4Pool() != null && other.getCustomerOwnedIpv4Pool().equals(this.getCustomerOwnedIpv4Pool()) == false) + return false; return true; } @@ -939,6 +991,7 @@ public int hashCode() { hashCode = prime * hashCode + ((getAvailabilityZones() == null) ? 0 : getAvailabilityZones().hashCode()); hashCode = prime * hashCode + ((getSecurityGroups() == null) ? 0 : getSecurityGroups().hashCode()); hashCode = prime * hashCode + ((getIpAddressType() == null) ? 0 : getIpAddressType().hashCode()); + hashCode = prime * hashCode + ((getCustomerOwnedIpv4Pool() == null) ? 0 : getCustomerOwnedIpv4Pool().hashCode()); return hashCode; } diff --git a/aws-java-sdk-elasticloadbalancingv2/src/main/java/com/amazonaws/services/elasticloadbalancingv2/model/SetSubnetsResult.java b/aws-java-sdk-elasticloadbalancingv2/src/main/java/com/amazonaws/services/elasticloadbalancingv2/model/SetSubnetsResult.java index c374a0e2cb78..a5fcdc83b71f 100644 --- a/aws-java-sdk-elasticloadbalancingv2/src/main/java/com/amazonaws/services/elasticloadbalancingv2/model/SetSubnetsResult.java +++ b/aws-java-sdk-elasticloadbalancingv2/src/main/java/com/amazonaws/services/elasticloadbalancingv2/model/SetSubnetsResult.java @@ -25,17 +25,17 @@ public class SetSubnetsResult extends com.amazonaws.AmazonWebServiceResult- * Information about the subnet and Availability Zone. + * Information about the subnets. *
* - * @return Information about the subnet and Availability Zone. + * @return Information about the subnets. */ public java.util.List- * Information about the subnet and Availability Zone. + * Information about the subnets. *
* * @param availabilityZones - * Information about the subnet and Availability Zone. + * Information about the subnets. */ public void setAvailabilityZones(java.util.Collection- * Information about the subnet and Availability Zone. + * Information about the subnets. *
*
* NOTE: This method appends the values to the existing list (if any). Use
@@ -71,7 +71,7 @@ public void setAvailabilityZones(java.util.Collection
- * Information about the subnet and Availability Zone. + * Information about the subnets. *
* * @param availabilityZones - * Information about the subnet and Availability Zone. + * Information about the subnets. * @return Returns a reference to this object so that method calls can be chained together. */ diff --git a/aws-java-sdk-elasticloadbalancingv2/src/main/java/com/amazonaws/services/elasticloadbalancingv2/model/transform/AvailabilityZoneStaxUnmarshaller.java b/aws-java-sdk-elasticloadbalancingv2/src/main/java/com/amazonaws/services/elasticloadbalancingv2/model/transform/AvailabilityZoneStaxUnmarshaller.java index f70163da0c59..180caa8ac76a 100644 --- a/aws-java-sdk-elasticloadbalancingv2/src/main/java/com/amazonaws/services/elasticloadbalancingv2/model/transform/AvailabilityZoneStaxUnmarshaller.java +++ b/aws-java-sdk-elasticloadbalancingv2/src/main/java/com/amazonaws/services/elasticloadbalancingv2/model/transform/AvailabilityZoneStaxUnmarshaller.java @@ -55,6 +55,11 @@ public AvailabilityZone unmarshall(StaxUnmarshallerContext context) throws Excep continue; } + if (context.testExpression("OutpostId", targetDepth)) { + availabilityZone.setOutpostId(StringStaxUnmarshaller.getInstance().unmarshall(context)); + continue; + } + if (context.testExpression("LoadBalancerAddresses", targetDepth)) { availabilityZone.withLoadBalancerAddresses(new ArrayList- * The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. + * The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. *
*/ private Statement abortStatement; @@ -138,8 +138,8 @@ public class CreateBotVersionResult extends com.amazonaws.AmazonWebServiceResult private Boolean childDirected; /** *
- * Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True
- * indicates that the bot is using the new model, otherwise, false.
+ * Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the
+ * imoprovements, otherwise, false.
*
- * The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. + * The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. *
* * @param abortStatement - * The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. + * The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. */ public void setAbortStatement(Statement abortStatement) { @@ -361,10 +361,10 @@ public void setAbortStatement(Statement abortStatement) { /** *- * The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. + * The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. *
* - * @return The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. + * @return The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. */ public Statement getAbortStatement() { @@ -373,11 +373,11 @@ public Statement getAbortStatement() { /** *- * The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. + * The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. *
* * @param abortStatement - * The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. + * The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. * @return Returns a reference to this object so that method calls can be chained together. */ @@ -1049,13 +1049,13 @@ public Boolean isChildDirected() { /** *
- * Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True
- * indicates that the bot is using the new model, otherwise, false.
+ * Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the
+ * imoprovements, otherwise, false.
*
true indicates that the bot is using
+ * the imoprovements, otherwise, false.
*/
public void setEnableModelImprovements(Boolean enableModelImprovements) {
@@ -1064,12 +1064,12 @@ public void setEnableModelImprovements(Boolean enableModelImprovements) {
/**
*
- * Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True
- * indicates that the bot is using the new model, otherwise, false.
+ * Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the
+ * imoprovements, otherwise, false.
*
true indicates that the bot is using
+ * the imoprovements, otherwise, false.
*/
public Boolean getEnableModelImprovements() {
@@ -1078,13 +1078,13 @@ public Boolean getEnableModelImprovements() {
/**
*
- * Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True
- * indicates that the bot is using the new model, otherwise, false.
+ * Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the
+ * imoprovements, otherwise, false.
*
true indicates that the bot is using
+ * the imoprovements, otherwise, false.
* @return Returns a reference to this object so that method calls can be chained together.
*/
@@ -1095,12 +1095,12 @@ public CreateBotVersionResult withEnableModelImprovements(Boolean enableModelImp
/**
*
- * Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True
- * indicates that the bot is using the new model, otherwise, false.
+ * Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the
+ * imoprovements, otherwise, false.
*
true indicates that the bot is using
+ * the imoprovements, otherwise, false.
*/
public Boolean isEnableModelImprovements() {
diff --git a/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/GetBotResult.java b/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/GetBotResult.java
index f904ea5c0eee..932417faf6f7 100644
--- a/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/GetBotResult.java
+++ b/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/GetBotResult.java
@@ -43,8 +43,8 @@ public class GetBotResult extends com.amazonaws.AmazonWebServiceResult
- * Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True
- * indicates that the bot is using the new model, otherwise, false.
+ * Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the
+ * imoprovements, otherwise, false.
*
AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are
- * configured for the bot.
+ * AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value.
+ * AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
*
*/
private Double nluIntentConfidenceThreshold;
@@ -328,13 +328,13 @@ public GetBotResult withIntents(java.util.Collection
- * Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True
- * indicates that the bot is using the new model, otherwise, false.
+ * Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the
+ * imoprovements, otherwise, false.
*
true indicates that the bot is using
+ * the imoprovements, otherwise, false.
*/
public void setEnableModelImprovements(Boolean enableModelImprovements) {
@@ -343,12 +343,12 @@ public void setEnableModelImprovements(Boolean enableModelImprovements) {
/**
*
- * Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True
- * indicates that the bot is using the new model, otherwise, false.
+ * Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the
+ * imoprovements, otherwise, false.
*
true indicates that the bot is using
+ * the imoprovements, otherwise, false.
*/
public Boolean getEnableModelImprovements() {
@@ -357,13 +357,13 @@ public Boolean getEnableModelImprovements() {
/**
*
- * Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True
- * indicates that the bot is using the new model, otherwise, false.
+ * Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the
+ * imoprovements, otherwise, false.
*
true indicates that the bot is using
+ * the imoprovements, otherwise, false.
* @return Returns a reference to this object so that method calls can be chained together.
*/
@@ -374,12 +374,12 @@ public GetBotResult withEnableModelImprovements(Boolean enableModelImprovements)
/**
*
- * Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True
- * indicates that the bot is using the new model, otherwise, false.
+ * Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the
+ * imoprovements, otherwise, false.
*
true indicates that the bot is using
+ * the imoprovements, otherwise, false.
*/
public Boolean isEnableModelImprovements() {
@@ -392,8 +392,8 @@ public Boolean isEnableModelImprovements() {
* AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response.
- * AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are
- * configured for the bot.
+ * AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value.
+ * AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
*
*
* @param nluIntentConfidenceThreshold
@@ -401,8 +401,8 @@ public Boolean isEnableModelImprovements() {
* AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response.
- * AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they
- * are configured for the bot.
+ * AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this
+ * value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
*/
public void setNluIntentConfidenceThreshold(Double nluIntentConfidenceThreshold) {
@@ -415,16 +415,16 @@ public void setNluIntentConfidenceThreshold(Double nluIntentConfidenceThreshold)
* AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response.
- * AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are
- * configured for the bot.
+ * AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value.
+ * AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
*
*
* @return The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent,
* AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response.
- * AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they
- * are configured for the bot.
+ * AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this
+ * value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
*/
public Double getNluIntentConfidenceThreshold() {
@@ -437,8 +437,8 @@ public Double getNluIntentConfidenceThreshold() {
* AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response.
- * AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are
- * configured for the bot.
+ * AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value.
+ * AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
*
*
* @param nluIntentConfidenceThreshold
@@ -446,8 +446,8 @@ public Double getNluIntentConfidenceThreshold() {
* AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response.
- * AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they
- * are configured for the bot.
+ * AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this
+ * value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
* @return Returns a reference to this object so that method calls can be chained together.
*/
diff --git a/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/Locale.java b/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/Locale.java
index 0d735bc33c66..6944b57462e7 100644
--- a/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/Locale.java
+++ b/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/Locale.java
@@ -22,7 +22,8 @@ public enum Locale {
EnUS("en-US"),
EnGB("en-GB"),
- DeDE("de-DE");
+ DeDE("de-DE"),
+ EnAU("en-AU");
private String value;
diff --git a/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/PutBotRequest.java b/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/PutBotRequest.java
index 15abbebdfcf6..ff6fabb32e52 100644
--- a/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/PutBotRequest.java
+++ b/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/PutBotRequest.java
@@ -46,8 +46,7 @@ public class PutBotRequest extends com.amazonaws.AmazonWebServiceRequest impleme
private java.util.List
- * Set to true to enable the use of a new natural language understanding (NLU) model. Using the new NLU
- * may improve the performance of your bot.
+ * Set to true to enable access to natural language understanding improvements.
*
* When you set the enableModelImprovements parameter to true you can use the
@@ -56,9 +55,7 @@ public class PutBotRequest extends com.amazonaws.AmazonWebServiceRequest impleme
*
* You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter
- * to true, your bot will use the new NLU. If you set the parameter to false, your bot
- * will continue to use the original NLU. If you set the parameter to false after setting it to
- * true, your bot will return to the original NLU.
+ * to true, your bot has access to accuracy improvements.
*
* The Regions where you can set the enableModelImprovements parameter to true are:
@@ -125,6 +122,31 @@ public class PutBotRequest extends com.amazonaws.AmazonWebServiceRequest impleme
*
* You must set the enableModelImprovements parameter to true to use confidence scores.
*
+ * US East (N. Virginia) (us-east-1) + *
+ *+ * US West (Oregon) (us-west-2) + *
+ *+ * Asia Pacific (Sydney) (ap-southeast-2) + *
+ *+ * EU (Ireland) (eu-west-1) + *
+ *
+ * In other Regions, the enableModelImprovements parameter is set to true by default.
+ *
* For example, suppose a bot is configured with the confidence threshold of 0.80 and the
* AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence
@@ -203,7 +225,7 @@ public class PutBotRequest extends com.amazonaws.AmazonWebServiceRequest impleme
/**
*
* When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times.
- * After that, Amazon Lex sends the message defined in abortStatement to the user, and then aborts the
+ * After that, Amazon Lex sends the message defined in abortStatement to the user, and then cancels the
* conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
*
@@ -217,7 +239,7 @@ public class PutBotRequest extends com.amazonaws.AmazonWebServiceRequest impleme
* create the CrustType slot.
*
- * If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is + * If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is * used instead. For more information, see AMAZON.FallbackIntent. *
@@ -501,8 +523,7 @@ public PutBotRequest withIntents(java.util.Collection
- * Set to true to enable the use of a new natural language understanding (NLU) model. Using the new NLU
- * may improve the performance of your bot.
+ * Set to true to enable access to natural language understanding improvements.
*
* When you set the enableModelImprovements parameter to true you can use the
@@ -511,9 +532,7 @@ public PutBotRequest withIntents(java.util.Collection
* You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter
- * to true, your bot will use the new NLU. If you set the parameter to false, your bot
- * will continue to use the original NLU. If you set the parameter to false after setting it to
- * true, your bot will return to the original NLU.
+ * to true, your bot has access to accuracy improvements.
*
* The Regions where you can set the enableModelImprovements parameter to true are:
@@ -568,8 +587,7 @@ public PutBotRequest withIntents(java.util.Collection
true to enable the use of a new natural language understanding (NLU) model. Using the
- * new NLU may improve the performance of your bot.
+ * Set to true to enable access to natural language understanding improvements.
*
* When you set the enableModelImprovements parameter to true you can use the
* nluIntentConfidenceThreshold parameter to configure confidence scores. For more information,
@@ -577,9 +595,7 @@ public PutBotRequest withIntents(java.util.Collection
* You can only set the enableModelImprovements parameter in certain Regions. If you set the
- * parameter to true, your bot will use the new NLU. If you set the parameter to
- * false, your bot will continue to use the original NLU. If you set the parameter to
- * false after setting it to true, your bot will return to the original NLU.
+ * parameter to true, your bot has access to accuracy improvements.
*
* The Regions where you can set the enableModelImprovements parameter to true are:
@@ -640,8 +656,7 @@ public void setEnableModelImprovements(Boolean enableModelImprovements) {
/**
*
- * Set to true to enable the use of a new natural language understanding (NLU) model. Using the new NLU
- * may improve the performance of your bot.
+ * Set to true to enable access to natural language understanding improvements.
*
* When you set the enableModelImprovements parameter to true you can use the
@@ -650,9 +665,7 @@ public void setEnableModelImprovements(Boolean enableModelImprovements) {
*
* You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter
- * to true, your bot will use the new NLU. If you set the parameter to false, your bot
- * will continue to use the original NLU. If you set the parameter to false after setting it to
- * true, your bot will return to the original NLU.
+ * to true, your bot has access to accuracy improvements.
*
* The Regions where you can set the enableModelImprovements parameter to true are:
@@ -706,8 +719,7 @@ public void setEnableModelImprovements(Boolean enableModelImprovements) {
*
*
true to enable the use of a new natural language understanding (NLU) model. Using the
- * new NLU may improve the performance of your bot.
+ * @return Set to true to enable access to natural language understanding improvements.
*
* When you set the enableModelImprovements parameter to true you can use the
* nluIntentConfidenceThreshold parameter to configure confidence scores. For more information,
@@ -715,9 +727,7 @@ public void setEnableModelImprovements(Boolean enableModelImprovements) {
*
* You can only set the enableModelImprovements parameter in certain Regions. If you set the
- * parameter to true, your bot will use the new NLU. If you set the parameter to
- * false, your bot will continue to use the original NLU. If you set the parameter to
- * false after setting it to true, your bot will return to the original NLU.
+ * parameter to true, your bot has access to accuracy improvements.
*
* The Regions where you can set the enableModelImprovements parameter to true
@@ -779,8 +789,7 @@ public Boolean getEnableModelImprovements() {
/**
*
- * Set to true to enable the use of a new natural language understanding (NLU) model. Using the new NLU
- * may improve the performance of your bot.
+ * Set to true to enable access to natural language understanding improvements.
*
* When you set the enableModelImprovements parameter to true you can use the
@@ -789,9 +798,7 @@ public Boolean getEnableModelImprovements() {
*
* You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter
- * to true, your bot will use the new NLU. If you set the parameter to false, your bot
- * will continue to use the original NLU. If you set the parameter to false after setting it to
- * true, your bot will return to the original NLU.
+ * to true, your bot has access to accuracy improvements.
*
* The Regions where you can set the enableModelImprovements parameter to true are:
@@ -846,8 +853,7 @@ public Boolean getEnableModelImprovements() {
*
true to enable the use of a new natural language understanding (NLU) model. Using the
- * new NLU may improve the performance of your bot.
+ * Set to true to enable access to natural language understanding improvements.
*
* When you set the enableModelImprovements parameter to true you can use the
* nluIntentConfidenceThreshold parameter to configure confidence scores. For more information,
@@ -855,9 +861,7 @@ public Boolean getEnableModelImprovements() {
*
* You can only set the enableModelImprovements parameter in certain Regions. If you set the
- * parameter to true, your bot will use the new NLU. If you set the parameter to
- * false, your bot will continue to use the original NLU. If you set the parameter to
- * false after setting it to true, your bot will return to the original NLU.
+ * parameter to true, your bot has access to accuracy improvements.
*
* The Regions where you can set the enableModelImprovements parameter to true are:
@@ -920,8 +924,7 @@ public PutBotRequest withEnableModelImprovements(Boolean enableModelImprovements
/**
*
- * Set to true to enable the use of a new natural language understanding (NLU) model. Using the new NLU
- * may improve the performance of your bot.
+ * Set to true to enable access to natural language understanding improvements.
*
* When you set the enableModelImprovements parameter to true you can use the
@@ -930,9 +933,7 @@ public PutBotRequest withEnableModelImprovements(Boolean enableModelImprovements
*
* You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter
- * to true, your bot will use the new NLU. If you set the parameter to false, your bot
- * will continue to use the original NLU. If you set the parameter to false after setting it to
- * true, your bot will return to the original NLU.
+ * to true, your bot has access to accuracy improvements.
*
* The Regions where you can set the enableModelImprovements parameter to true are:
@@ -986,8 +987,7 @@ public PutBotRequest withEnableModelImprovements(Boolean enableModelImprovements
*
*
true to enable the use of a new natural language understanding (NLU) model. Using the
- * new NLU may improve the performance of your bot.
+ * @return Set to true to enable access to natural language understanding improvements.
*
* When you set the enableModelImprovements parameter to true you can use the
* nluIntentConfidenceThreshold parameter to configure confidence scores. For more information,
@@ -995,9 +995,7 @@ public PutBotRequest withEnableModelImprovements(Boolean enableModelImprovements
*
* You can only set the enableModelImprovements parameter in certain Regions. If you set the
- * parameter to true, your bot will use the new NLU. If you set the parameter to
- * false, your bot will continue to use the original NLU. If you set the parameter to
- * false after setting it to true, your bot will return to the original NLU.
+ * parameter to true, your bot has access to accuracy improvements.
*
* The Regions where you can set the enableModelImprovements parameter to true
@@ -1069,6 +1067,31 @@ public Boolean isEnableModelImprovements() {
*
* You must set the enableModelImprovements parameter to true to use confidence scores.
*
+ * US East (N. Virginia) (us-east-1) + *
+ *+ * US West (Oregon) (us-west-2) + *
+ *+ * Asia Pacific (Sydney) (ap-southeast-2) + *
+ *+ * EU (Ireland) (eu-west-1) + *
+ *
+ * In other Regions, the enableModelImprovements parameter is set to true by default.
+ *
* For example, suppose a bot is configured with the confidence threshold of 0.80 and the
* AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence
@@ -1109,6 +1132,32 @@ public Boolean isEnableModelImprovements() {
* You must set the enableModelImprovements parameter to true to use confidence
* scores.
*
+ * US East (N. Virginia) (us-east-1) + *
+ *+ * US West (Oregon) (us-west-2) + *
+ *+ * Asia Pacific (Sydney) (ap-southeast-2) + *
+ *+ * EU (Ireland) (eu-west-1) + *
+ *
+ * In other Regions, the enableModelImprovements parameter is set to true by
+ * default.
+ *
* For example, suppose a bot is configured with the confidence threshold of 0.80 and the
* AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following
@@ -1154,6 +1203,31 @@ public void setNluIntentConfidenceThreshold(Double nluIntentConfidenceThreshold)
*
* You must set the enableModelImprovements parameter to true to use confidence scores.
*
+ * US East (N. Virginia) (us-east-1) + *
+ *+ * US West (Oregon) (us-west-2) + *
+ *+ * Asia Pacific (Sydney) (ap-southeast-2) + *
+ *+ * EU (Ireland) (eu-west-1) + *
+ *
+ * In other Regions, the enableModelImprovements parameter is set to true by default.
+ *
* For example, suppose a bot is configured with the confidence threshold of 0.80 and the
* AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence
@@ -1193,6 +1267,32 @@ public void setNluIntentConfidenceThreshold(Double nluIntentConfidenceThreshold)
* You must set the enableModelImprovements parameter to true to use confidence
* scores.
*
+ * US East (N. Virginia) (us-east-1) + *
+ *+ * US West (Oregon) (us-west-2) + *
+ *+ * Asia Pacific (Sydney) (ap-southeast-2) + *
+ *+ * EU (Ireland) (eu-west-1) + *
+ *
+ * In other Regions, the enableModelImprovements parameter is set to true by
+ * default.
+ *
* For example, suppose a bot is configured with the confidence threshold of 0.80 and the
* AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following
@@ -1238,6 +1338,31 @@ public Double getNluIntentConfidenceThreshold() {
*
* You must set the enableModelImprovements parameter to true to use confidence scores.
*
+ * US East (N. Virginia) (us-east-1) + *
+ *+ * US West (Oregon) (us-west-2) + *
+ *+ * Asia Pacific (Sydney) (ap-southeast-2) + *
+ *+ * EU (Ireland) (eu-west-1) + *
+ *
+ * In other Regions, the enableModelImprovements parameter is set to true by default.
+ *
* For example, suppose a bot is configured with the confidence threshold of 0.80 and the
* AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence
@@ -1278,6 +1403,32 @@ public Double getNluIntentConfidenceThreshold() {
* You must set the enableModelImprovements parameter to true to use confidence
* scores.
*
+ * US East (N. Virginia) (us-east-1) + *
+ *+ * US West (Oregon) (us-west-2) + *
+ *+ * Asia Pacific (Sydney) (ap-southeast-2) + *
+ *+ * EU (Ireland) (eu-west-1) + *
+ *
+ * In other Regions, the enableModelImprovements parameter is set to true by
+ * default.
+ *
* For example, suppose a bot is configured with the confidence threshold of 0.80 and the
* AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following
@@ -1594,7 +1745,7 @@ public PutBotRequest withClarificationPrompt(Prompt clarificationPrompt) {
/**
*
* When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times.
- * After that, Amazon Lex sends the message defined in abortStatement to the user, and then aborts the
+ * After that, Amazon Lex sends the message defined in abortStatement to the user, and then cancels the
* conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
*
@@ -1608,7 +1759,7 @@ public PutBotRequest withClarificationPrompt(Prompt clarificationPrompt) {
* create the CrustType slot.
*
- * If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is + * If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is * used instead. For more information, see AMAZON.FallbackIntent. *
@@ -1616,7 +1767,7 @@ public PutBotRequest withClarificationPrompt(Prompt clarificationPrompt) { * @param abortStatement * When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few * times. After that, Amazon Lex sends the message defined inabortStatement to the user, and
- * then aborts the conversation. To set the number of retries, use the valueElicitationPrompt
+ * then cancels the conversation. To set the number of retries, use the valueElicitationPrompt
* field for the slot type.
*
* For example, in a pizza ordering bot, Amazon Lex might ask a user "What type of crust would you like?" If
@@ -1629,7 +1780,7 @@ public PutBotRequest withClarificationPrompt(Prompt clarificationPrompt) {
* field when you create the CrustType slot.
*
- * If you have defined a fallback intent the abort statement will not be sent to the user, the fallback + * If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback * intent is used instead. For more information, see AMAZON.FallbackIntent. */ @@ -1641,7 +1792,7 @@ public void setAbortStatement(Statement abortStatement) { /** *
* When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times.
- * After that, Amazon Lex sends the message defined in abortStatement to the user, and then aborts the
+ * After that, Amazon Lex sends the message defined in abortStatement to the user, and then cancels the
* conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
*
@@ -1655,14 +1806,14 @@ public void setAbortStatement(Statement abortStatement) {
* create the CrustType slot.
*
- * If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is + * If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is * used instead. For more information, see AMAZON.FallbackIntent. *
* * @return When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few * times. After that, Amazon Lex sends the message defined inabortStatement to the user, and
- * then aborts the conversation. To set the number of retries, use the valueElicitationPrompt
+ * then cancels the conversation. To set the number of retries, use the valueElicitationPrompt
* field for the slot type.
*
* For example, in a pizza ordering bot, Amazon Lex might ask a user "What type of crust would you like?" If
@@ -1675,7 +1826,7 @@ public void setAbortStatement(Statement abortStatement) {
* field when you create the CrustType slot.
*
- * If you have defined a fallback intent the abort statement will not be sent to the user, the fallback + * If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback * intent is used instead. For more information, see * AMAZON.FallbackIntent. @@ -1688,7 +1839,7 @@ public Statement getAbortStatement() { /** *
* When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times.
- * After that, Amazon Lex sends the message defined in abortStatement to the user, and then aborts the
+ * After that, Amazon Lex sends the message defined in abortStatement to the user, and then cancels the
* conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
*
@@ -1702,7 +1853,7 @@ public Statement getAbortStatement() {
* create the CrustType slot.
*
- * If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is + * If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is * used instead. For more information, see AMAZON.FallbackIntent. *
@@ -1710,7 +1861,7 @@ public Statement getAbortStatement() { * @param abortStatement * When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few * times. After that, Amazon Lex sends the message defined inabortStatement to the user, and
- * then aborts the conversation. To set the number of retries, use the valueElicitationPrompt
+ * then cancels the conversation. To set the number of retries, use the valueElicitationPrompt
* field for the slot type.
*
* For example, in a pizza ordering bot, Amazon Lex might ask a user "What type of crust would you like?" If
@@ -1723,7 +1874,7 @@ public Statement getAbortStatement() {
* field when you create the CrustType slot.
*
- * If you have defined a fallback intent the abort statement will not be sent to the user, the fallback
+ * If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback
* intent is used instead. For more information, see AMAZON.FallbackIntent.
* @return Returns a reference to this object so that method calls can be chained together.
diff --git a/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/PutBotResult.java b/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/PutBotResult.java
index 92b4948d6712..33a595a40888 100644
--- a/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/PutBotResult.java
+++ b/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/PutBotResult.java
@@ -43,8 +43,8 @@ public class PutBotResult extends com.amazonaws.AmazonWebServiceResult
- * Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True
- * indicates that the bot is using the new model, otherwise, false.
+ * Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the
+ * imoprovements, otherwise, false.
* AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are
- * configured for the bot.
+ * AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value.
+ * AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
*
- * Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True
- * indicates that the bot is using the new model, otherwise, false.
+ * Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the
+ * imoprovements, otherwise, false.
*
true indicates that the bot is using
+ * the imoprovements, otherwise, false.
*/
public void setEnableModelImprovements(Boolean enableModelImprovements) {
@@ -358,12 +358,12 @@ public void setEnableModelImprovements(Boolean enableModelImprovements) {
/**
*
- * Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True
- * indicates that the bot is using the new model, otherwise, false.
+ * Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the
+ * imoprovements, otherwise, false.
*
true indicates that the bot is using
+ * the imoprovements, otherwise, false.
*/
public Boolean getEnableModelImprovements() {
@@ -372,13 +372,13 @@ public Boolean getEnableModelImprovements() {
/**
*
- * Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True
- * indicates that the bot is using the new model, otherwise, false.
+ * Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the
+ * imoprovements, otherwise, false.
*
true indicates that the bot is using
+ * the imoprovements, otherwise, false.
* @return Returns a reference to this object so that method calls can be chained together.
*/
@@ -389,12 +389,12 @@ public PutBotResult withEnableModelImprovements(Boolean enableModelImprovements)
/**
*
- * Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True
- * indicates that the bot is using the new model, otherwise, false.
+ * Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the
+ * imoprovements, otherwise, false.
*
true indicates that the bot is using
+ * the imoprovements, otherwise, false.
*/
public Boolean isEnableModelImprovements() {
@@ -407,8 +407,8 @@ public Boolean isEnableModelImprovements() {
* AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response.
- * AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are
- * configured for the bot.
+ * AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value.
+ * AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
*
*
* @param nluIntentConfidenceThreshold
@@ -416,8 +416,8 @@ public Boolean isEnableModelImprovements() {
* AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response.
- * AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they
- * are configured for the bot.
+ * AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this
+ * value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
*/
public void setNluIntentConfidenceThreshold(Double nluIntentConfidenceThreshold) {
@@ -430,16 +430,16 @@ public void setNluIntentConfidenceThreshold(Double nluIntentConfidenceThreshold)
* AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response.
- * AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are
- * configured for the bot.
+ * AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value.
+ * AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
*
*
* @return The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent,
* AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response.
- * AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they
- * are configured for the bot.
+ * AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this
+ * value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
*/
public Double getNluIntentConfidenceThreshold() {
@@ -452,8 +452,8 @@ public Double getNluIntentConfidenceThreshold() {
* AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response.
- * AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are
- * configured for the bot.
+ * AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value.
+ * AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
*
*
* @param nluIntentConfidenceThreshold
@@ -461,8 +461,8 @@ public Double getNluIntentConfidenceThreshold() {
* AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response.
- * AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they
- * are configured for the bot.
+ * AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this
+ * value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
* @return Returns a reference to this object so that method calls can be chained together.
*/
@@ -519,11 +519,11 @@ public PutBotResult withClarificationPrompt(Prompt clarificationPrompt) {
/**
* - * The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. + * The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. *
* * @param abortStatement - * The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. + * The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. */ public void setAbortStatement(Statement abortStatement) { @@ -532,10 +532,10 @@ public void setAbortStatement(Statement abortStatement) { /** *- * The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. + * The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. *
* - * @return The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. + * @return The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. */ public Statement getAbortStatement() { @@ -544,11 +544,11 @@ public Statement getAbortStatement() { /** *- * The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. + * The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. *
* * @param abortStatement - * The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. + * The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. * @return Returns a reference to this object so that method calls can be chained together. */ diff --git a/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/PutSlotTypeRequest.java b/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/PutSlotTypeRequest.java index 6e038eac1c5f..d031c50aa26e 100644 --- a/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/PutSlotTypeRequest.java +++ b/aws-java-sdk-lexmodelbuilding/src/main/java/com/amazonaws/services/lexmodelbuilding/model/PutSlotTypeRequest.java @@ -54,6 +54,10 @@ public class PutSlotTypeRequest extends com.amazonaws.AmazonWebServiceRequest im * about the values that it resolves for a slot. * *+ * A regular expression slot type doesn't require enumeration values. All other slot types require a list of + * enumeration values. + *
+ ** When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values * for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not * using a Lambda function you can choose to return the value that the user entered or the first value in the @@ -271,6 +275,10 @@ public PutSlotTypeRequest withDescription(String description) { * about the values that it resolves for a slot. *
*+ * A regular expression slot type doesn't require enumeration values. All other slot types require a list of + * enumeration values. + *
+ *
* When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values
* for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not
* using a Lambda function you can choose to return the value that the user entered or the first value in the
@@ -281,6 +289,10 @@ public PutSlotTypeRequest withDescription(String description) {
* value can have a list of synonyms, which are additional values that help train the machine
* learning model about the values that it resolves for a slot.
+ * A regular expression slot type doesn't require enumeration values. All other slot types require a list of + * enumeration values. + *
+ *
* When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible
* values for the slot. If you are using a Lambda function, this resolution list is passed to the function.
* If you are not using a Lambda function you can choose to return the value that the user entered or the
@@ -299,6 +311,10 @@ public java.util.List
+ * A regular expression slot type doesn't require enumeration values. All other slot types require a list of + * enumeration values. + *
+ *
* When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values
* for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not
* using a Lambda function you can choose to return the value that the user entered or the first value in the
@@ -310,6 +326,10 @@ public java.util.Listsynonyms, which are additional values that help train the machine
* learning model about the values that it resolves for a slot.
+ * A regular expression slot type doesn't require enumeration values. All other slot types require a list of + * enumeration values. + *
+ *
* When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible
* values for the slot. If you are using a Lambda function, this resolution list is passed to the function.
* If you are not using a Lambda function you can choose to return the value that the user entered or the
@@ -333,6 +353,10 @@ public void setEnumerationValues(java.util.Collection
+ * A regular expression slot type doesn't require enumeration values. All other slot types require a list of + * enumeration values. + *
+ *
* When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values
* for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not
* using a Lambda function you can choose to return the value that the user entered or the first value in the
@@ -349,6 +373,10 @@ public void setEnumerationValues(java.util.Collectionsynonyms, which are additional values that help train the machine
* learning model about the values that it resolves for a slot.
+ * A regular expression slot type doesn't require enumeration values. All other slot types require a list of + * enumeration values. + *
+ ** When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible * values for the slot. If you are using a Lambda function, this resolution list is passed to the function. * If you are not using a Lambda function you can choose to return the value that the user entered or the @@ -374,6 +402,10 @@ public PutSlotTypeRequest withEnumerationValues(EnumerationValue... enumerationV * about the values that it resolves for a slot. *
*+ * A regular expression slot type doesn't require enumeration values. All other slot types require a list of + * enumeration values. + *
+ *
* When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values
* for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not
* using a Lambda function you can choose to return the value that the user entered or the first value in the
@@ -385,6 +417,10 @@ public PutSlotTypeRequest withEnumerationValues(EnumerationValue... enumerationV
* value can have a list of synonyms, which are additional values that help train the machine
* learning model about the values that it resolves for a slot.
+ * A regular expression slot type doesn't require enumeration values. All other slot types require a list of + * enumeration values. + *
+ *
* When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible
* values for the slot. If you are using a Lambda function, this resolution list is passed to the function.
* If you are not using a Lambda function you can choose to return the value that the user entered or the
diff --git a/aws-java-sdk-licensemanager/pom.xml b/aws-java-sdk-licensemanager/pom.xml
index 2ab82a6237dc..19ed741e8894 100644
--- a/aws-java-sdk-licensemanager/pom.xml
+++ b/aws-java-sdk-licensemanager/pom.xml
@@ -5,7 +5,7 @@
Resets all authorizer cache entries on a stage. Supported only for HTTP APIs. The resource specified in the request was not found. The client is sending more than the allowed number of requests per unit of time. The authorization type. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withIdentitySource", - "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/",
"getterMethodName" : "getIdentitySource",
"getterModel" : {
"returnType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "setterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/", "setterMethodName" : "setIdentitySource", "setterModel" : { "timestampFormat" : null, @@ -7439,13 +7618,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withIdentitySource", - "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/",
"getterMethodName" : "getIdentitySource",
"getterModel" : {
"returnType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "setterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/", "setterMethodName" : "setIdentitySource", "setterModel" : { "timestampFormat" : null, @@ -8151,13 +8470,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withIdentitySource", - "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/",
"getterMethodName" : "getIdentitySource",
"getterModel" : {
"returnType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "setterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/", "setterMethodName" : "setIdentitySource", "setterModel" : { "timestampFormat" : null, @@ -16418,13 +16875,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withIdentitySource", - "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/",
"getterMethodName" : "getIdentitySource",
"getterModel" : {
"returnType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "setterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/", "setterMethodName" : "setIdentitySource", "setterModel" : { "timestampFormat" : null, @@ -17130,13 +17727,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withIdentitySource", - "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/",
"getterMethodName" : "getIdentitySource",
"getterModel" : {
"returnType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "setterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/", "setterMethodName" : "setIdentitySource", "setterModel" : { "timestampFormat" : null, @@ -17879,13 +18614,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withIdentitySource", - "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/",
"getterMethodName" : "getIdentitySource",
"getterModel" : {
"returnType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "setterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/", "setterMethodName" : "setIdentitySource", "setterModel" : { "timestampFormat" : null, @@ -18591,13 +19466,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withIdentitySource", - "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/",
"getterMethodName" : "getIdentitySource",
"getterModel" : {
"returnType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "setterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/", "setterMethodName" : "setIdentitySource", "setterModel" : { "timestampFormat" : null, @@ -62732,13 +63745,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withIdentitySource", - "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/",
"getterMethodName" : "getIdentitySource",
"getterModel" : {
"returnType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "setterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/", "setterMethodName" : "setIdentitySource", "setterModel" : { "timestampFormat" : null, @@ -63444,13 +64597,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The API identifier. The API identifier. The API identifier. The API identifier. The API identifier. The API identifier. The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be $default. Maximum length is 128 characters. The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be $default. Maximum length is 128 characters. The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be $default. Maximum length is 128 characters. The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be $default. Maximum length is 128 characters. The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be $default. Maximum length is 128 characters. The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be $default. Maximum length is 128 characters. The API identifier. The API identifier. The API identifier. The API identifier. The API identifier. The API identifier. The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be $default. Maximum length is 128 characters. The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be $default. Maximum length is 128 characters. The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be $default. Maximum length is 128 characters. The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be $default. Maximum length is 128 characters. The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be $default. Maximum length is 128 characters. The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be $default. Maximum length is 128 characters. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withIdentitySource", - "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/",
"getterMethodName" : "getIdentitySource",
"getterModel" : {
"returnType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "setterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/", "setterMethodName" : "setIdentitySource", "setterModel" : { "timestampFormat" : null, @@ -118644,13 +120306,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withIdentitySource", - "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/",
"getterMethodName" : "getIdentitySource",
"getterModel" : {
"returnType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "setterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/", "setterMethodName" : "setIdentitySource", "setterModel" : { "timestampFormat" : null, @@ -119426,13 +121228,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withIdentitySource", - "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/",
"getterMethodName" : "getIdentitySource",
"getterModel" : {
"returnType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "setterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/", "setterMethodName" : "setIdentitySource", "setterModel" : { "timestampFormat" : null, @@ -120175,13 +122115,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withIdentitySource", - "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "getterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@return The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/",
"getterMethodName" : "getIdentitySource",
"getterModel" : {
"returnType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".*/", + "setterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.*/", "setterMethodName" : "setIdentitySource", "setterModel" : { "timestampFormat" : null, @@ -120887,13 +122967,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\".\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**
The identity source for which authorization is requested.
For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setIdentitySource(java.util.Collection)} or {@link #withIdentitySource(java.util.Collection)} if you want to override the existing values.
\n@param identitySource The identity source for which authorization is requested.For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs.
For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "java.util.List The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. One of the parameters in the request is invalid. The resource specified in the request was not found. The client is sending more than the allowed number of requests per unit of time. Resets all authorizer cache entries on a stage. Supported only for HTTP APIs. The authorization type. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. The authorizer identifier. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT )from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. The authorizer identifier. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. Represents an exported definition of an API in a particular output format, for example, YAML. The API is serialized to the requested specification, for example, OpenAPI 3.0. The API identifier. The stage name. Stage names can contain only alphanumeric characters, hyphens, and underscores, or be $default. Maximum length is 128 characters. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. The authorizer identifier. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. The authorizer identifier. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: Specifies whether a Lambda authorizer returns a response in a simple format. By default, a Lambda authorizer must return an IAM policy. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, specify null. Supported only for REQUEST authorizers. Specifies the required credentials as an IAM role for API Gateway to invoke the authorizer. To specify an IAM role for API Gateway to assume, use the role's Amazon Resource Name (ARN). To use resource-based permissions on the Lambda function, don't specify this parameter. Supported only for REQUEST authorizers. The authorizer identifier. Specifies the format of the payload sent to an HTTP API Lambda authorizer. Required for HTTP API Lambda authorizers. Supported values are 1.0 and 2.0. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. Authorizer caching is not currently supported. Don't specify this value for authorizers. The time to live (TTL) for cached authorizer results, in seconds. If it equals 0, authorization caching is disabled. If it is greater than 0, API Gateway caches authorizer responses. The maximum value is 3600, or 1 hour. Supported only for HTTP API Lambda authorizers. The authorizer type. For WebSocket APIs, specify REQUEST for a Lambda function using incoming request parameters. For HTTP APIs, specify JWT to use JSON Web Tokens. The authorizer type. Specify REQUEST for a Lambda function using incoming request parameters. Specify JWT to use JSON Web Tokens (supported only for HTTP APIs). The authorizer's Uniform Resource Identifier (URI). ForREQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: The authorizer's Uniform Resource Identifier (URI). For REQUEST authorizers, this must be a well-formed Lambda function URI, for example, arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:us-west-2: Specifies whether a Lambda authorizer returns a response in a simple format. If enabled, the Lambda authorizer can return a boolean value instead of an IAM policy. Supported only for HTTP APIs. To learn more, see Working with AWS Lambda authorizers for HTTP APIs The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. Currently, the identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name. These parameters will be used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example \"$request.header.Authorization\". The identity source for which authorization is requested. For a REQUEST authorizer, this is optional. The value is a set of one or more mapping expressions of the specified request parameters. The identity source can be headers, query string parameters, stage variables, and context parameters. For example, if an Auth header and a Name query string parameter are defined as identity sources, this value is route.request.header.Auth, route.request.querystring.Name for WebSocket APIs. For HTTP APIs, use selection expressions prefixed with $, for example, $request.header.Auth, $request.querystring.Name. These parameters are used to perform runtime validation for Lambda-based authorizers by verifying all of the identity-related request parameters are present in the request, not null, and non-empty. Only when this is true does the authorizer invoke the authorizer Lambda function. Otherwise, it returns a 401 Unauthorized response without calling the Lambda function. For HTTP APIs, identity sources are also used as the cache key when caching is enabled. To learn more, see Working with AWS Lambda authorizers for HTTP APIs. For JWT, a single entry that specifies where to extract the JSON Web Token (JWT) from inbound requests. Currently only header-based and query parameter-based selections are supported, for example $request.header.Authorization. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, or JWT for using JSON Web Tokens. The authorization type for the route. For WebSocket APIs, valid values are NONE for open access, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer For HTTP APIs, valid values are NONE for open access, JWT for using JSON Web Tokens, AWS_IAM for using AWS IAM permissions, and CUSTOM for using a Lambda authorizer. Deletes a report group. Before you delete a report group, you must delete its reports. The ARN of the report group to delete. The ARN of the report group to delete. The ARN of the report group to delete. The ARN of the report group to delete. The ARN of the report group to delete. The ARN of the report group to delete. The ARN of the report group to delete. The ARN of the report group to delete. The ARN of the report group to delete. The ARN of the report group to delete. The ARN of the report group to delete. The ARN of the report group to delete. If If If If DeleteReportGroup: Deletes a report group. Before you delete a report group, you must delete its reports. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown. true, deletes any reports that belong to a report group before deleting the report group. false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown. true, deletes any reports that belong to a report group before deleting the report group. false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown. true, deletes any reports that belong to a report group before deleting the report group.
If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "fluentSetterMethodName" : "withDeleteReports",
+ "getterDocumentation" : "/**
If true, deletes any reports that belong to a report group before deleting the report group.
If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.
true, deletes any reports that belong to a report group before deleting the report group. If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.*/",
+ "getterMethodName" : "getDeleteReports",
+ "getterModel" : {
+ "returnType" : "Boolean",
+ "documentation" : null
+ },
+ "http" : {
+ "additionalMarshallingPath" : null,
+ "additionalUnmarshallingPath" : null,
+ "flattened" : false,
+ "greedy" : false,
+ "header" : false,
+ "isPayload" : false,
+ "isStreaming" : false,
+ "location" : null,
+ "marshallLocation" : "PAYLOAD",
+ "marshallLocationName" : "deleteReports",
+ "queryString" : false,
+ "requiresLength" : false,
+ "statusCode" : false,
+ "unmarshallLocationName" : "deleteReports",
+ "uri" : false
+ },
+ "idempotencyToken" : false,
+ "isBinary" : false,
+ "jsonValue" : false,
+ "list" : false,
+ "listModel" : null,
+ "map" : false,
+ "mapModel" : null,
+ "marshallingTargetClass" : "Boolean",
+ "marshallingType" : "BOOLEAN",
+ "name" : "DeleteReports",
+ "sensitive" : false,
+ "setterDocumentation" : "/**
If true, deletes any reports that belong to a report group before deleting the report group.
If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.
true, deletes any reports that belong to a report group before deleting the report group. If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.*/",
+ "setterMethodName" : "setDeleteReports",
+ "setterModel" : {
+ "timestampFormat" : null,
+ "variableDeclarationType" : "Boolean",
+ "variableName" : "deleteReports",
+ "variableType" : "Boolean",
+ "documentation" : "",
+ "simpleType" : "Boolean",
+ "variableSetterType" : "Boolean"
+ },
+ "shouldEmitLegacyEnumSetter" : false,
+ "shouldFullyQualify" : false,
+ "simple" : true,
+ "unmarshallingType" : null,
+ "varargSetterDocumentation" : "/**
If true, deletes any reports that belong to a report group before deleting the report group.
If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.
true, deletes any reports that belong to a report group before deleting the report group. If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "variable" : {
+ "timestampFormat" : null,
+ "variableDeclarationType" : "Boolean",
+ "variableName" : "deleteReports",
+ "variableType" : "Boolean",
+ "documentation" : "
If true, deletes any reports that belong to a report group before deleting the report group.
If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.
The ARN of the report group to delete.
", + "documentation" : "The ARN of the report group to delete.
", "endpointDiscoveryId" : false, "enumType" : null, - "fluentSetterDocumentation" : "/**The ARN of the report group to delete.
\n@param arn The ARN of the report group to delete.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**The ARN of the report group to delete.
\n@param arn The ARN of the report group to delete.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withArn", - "getterDocumentation" : "/**The ARN of the report group to delete.
\n@return The ARN of the report group to delete.*/", + "getterDocumentation" : "/**The ARN of the report group to delete.
\n@return The ARN of the report group to delete.*/", "getterMethodName" : "getArn", "getterModel" : { "returnType" : "String", @@ -35916,7 +35985,7 @@ "marshallingType" : "STRING", "name" : "Arn", "sensitive" : false, - "setterDocumentation" : "/**The ARN of the report group to delete.
\n@param arn The ARN of the report group to delete.*/", + "setterDocumentation" : "/**The ARN of the report group to delete.
\n@param arn The ARN of the report group to delete.*/", "setterMethodName" : "setArn", "setterModel" : { "timestampFormat" : null, @@ -35931,17 +36000,87 @@ "shouldFullyQualify" : false, "simple" : true, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**The ARN of the report group to delete.
\n@param arn The ARN of the report group to delete.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**The ARN of the report group to delete.
\n@param arn The ARN of the report group to delete.\n@return Returns a reference to this object so that method calls can be chained together.*/", "variable" : { "timestampFormat" : null, "variableDeclarationType" : "String", "variableName" : "arn", "variableType" : "String", - "documentation" : "The ARN of the report group to delete.
", + "documentation" : "The ARN of the report group to delete.
", "simpleType" : "String", "variableSetterType" : "String" }, "xmlNameSpaceUri" : null + }, + "DeleteReports" : { + "c2jName" : "deleteReports", + "c2jShape" : "Boolean", + "deprecated" : false, + "documentation" : "If true, deletes any reports that belong to a report group before deleting the report group.
If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.
If true, deletes any reports that belong to a report group before deleting the report group.
If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.
true, deletes any reports that belong to a report group before deleting the report group. If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "fluentSetterMethodName" : "withDeleteReports",
+ "getterDocumentation" : "/**
If true, deletes any reports that belong to a report group before deleting the report group.
If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.
true, deletes any reports that belong to a report group before deleting the report group. If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.*/",
+ "getterMethodName" : "getDeleteReports",
+ "getterModel" : {
+ "returnType" : "Boolean",
+ "documentation" : null
+ },
+ "http" : {
+ "additionalMarshallingPath" : null,
+ "additionalUnmarshallingPath" : null,
+ "flattened" : false,
+ "greedy" : false,
+ "header" : false,
+ "isPayload" : false,
+ "isStreaming" : false,
+ "location" : null,
+ "marshallLocation" : "PAYLOAD",
+ "marshallLocationName" : "deleteReports",
+ "queryString" : false,
+ "requiresLength" : false,
+ "statusCode" : false,
+ "unmarshallLocationName" : "deleteReports",
+ "uri" : false
+ },
+ "idempotencyToken" : false,
+ "isBinary" : false,
+ "jsonValue" : false,
+ "list" : false,
+ "listModel" : null,
+ "map" : false,
+ "mapModel" : null,
+ "marshallingTargetClass" : "Boolean",
+ "marshallingType" : "BOOLEAN",
+ "name" : "DeleteReports",
+ "sensitive" : false,
+ "setterDocumentation" : "/**
If true, deletes any reports that belong to a report group before deleting the report group.
If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.
true, deletes any reports that belong to a report group before deleting the report group. If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.*/",
+ "setterMethodName" : "setDeleteReports",
+ "setterModel" : {
+ "timestampFormat" : null,
+ "variableDeclarationType" : "Boolean",
+ "variableName" : "deleteReports",
+ "variableType" : "Boolean",
+ "documentation" : "",
+ "simpleType" : "Boolean",
+ "variableSetterType" : "Boolean"
+ },
+ "shouldEmitLegacyEnumSetter" : false,
+ "shouldFullyQualify" : false,
+ "simple" : true,
+ "unmarshallingType" : null,
+ "varargSetterDocumentation" : "/**
If true, deletes any reports that belong to a report group before deleting the report group.
If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.
true, deletes any reports that belong to a report group before deleting the report group. If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "variable" : {
+ "timestampFormat" : null,
+ "variableDeclarationType" : "Boolean",
+ "variableName" : "deleteReports",
+ "variableType" : "Boolean",
+ "documentation" : "
If true, deletes any reports that belong to a report group before deleting the report group.
If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
A filter used to return specific types of test cases.
", + "documentation" : "A filter used to return specific types of test cases. In order to pass the filter, the report must meet all of the filter properties.
", "endpointDiscoveryMembers" : null, "enums" : null, "errorCode" : null, @@ -89981,12 +90120,12 @@ "c2jName" : "status", "c2jShape" : "String", "deprecated" : false, - "documentation" : " The status used to filter test cases. Valid statuses are SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.
The status used to filter test cases. A TestCaseFilter can have one status. Valid values are:
SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
The status used to filter test cases. Valid statuses are SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.
SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "fluentSetterDocumentation" : "/**The status used to filter test cases. A TestCaseFilter can have one status. Valid values are:
SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
TestCaseFilter can have one status. Valid values are: SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
The status used to filter test cases. Valid statuses are SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.
SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.*/",
+ "getterDocumentation" : "/**The status used to filter test cases. A TestCaseFilter can have one status. Valid values are:
SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
TestCaseFilter can have one status. Valid values are: SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
The status used to filter test cases. Valid statuses are SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.
SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.*/",
+ "setterDocumentation" : "/**The status used to filter test cases. A TestCaseFilter can have one status. Valid values are:
SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
TestCaseFilter can have one status. Valid values are: SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
The status used to filter test cases. Valid statuses are SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.
SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "varargSetterDocumentation" : "/**The status used to filter test cases. A TestCaseFilter can have one status. Valid values are:
SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
TestCaseFilter can have one status. Valid values are: SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
The status used to filter test cases. Valid statuses are SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.
The status used to filter test cases. A TestCaseFilter can have one status. Valid values are:
SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
A keyword that is used to filter on the name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.
A keyword that is used to filter on the name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.
name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "fluentSetterMethodName" : "withKeyword",
+ "getterDocumentation" : "/**A keyword that is used to filter on the name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.
name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.*/",
+ "getterMethodName" : "getKeyword",
+ "getterModel" : {
+ "returnType" : "String",
+ "documentation" : null
+ },
+ "http" : {
+ "additionalMarshallingPath" : null,
+ "additionalUnmarshallingPath" : null,
+ "flattened" : false,
+ "greedy" : false,
+ "header" : false,
+ "isPayload" : false,
+ "isStreaming" : false,
+ "location" : null,
+ "marshallLocation" : "PAYLOAD",
+ "marshallLocationName" : "keyword",
+ "queryString" : false,
+ "requiresLength" : false,
+ "statusCode" : false,
+ "unmarshallLocationName" : "keyword",
+ "uri" : false
+ },
+ "idempotencyToken" : false,
+ "isBinary" : false,
+ "jsonValue" : false,
+ "list" : false,
+ "listModel" : null,
+ "map" : false,
+ "mapModel" : null,
+ "marshallingTargetClass" : "String",
+ "marshallingType" : "STRING",
+ "name" : "Keyword",
+ "sensitive" : false,
+ "setterDocumentation" : "/**A keyword that is used to filter on the name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.
name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.*/",
+ "setterMethodName" : "setKeyword",
+ "setterModel" : {
+ "timestampFormat" : null,
+ "variableDeclarationType" : "String",
+ "variableName" : "keyword",
+ "variableType" : "String",
+ "documentation" : "",
+ "simpleType" : "String",
+ "variableSetterType" : "String"
+ },
+ "shouldEmitLegacyEnumSetter" : false,
+ "shouldFullyQualify" : false,
+ "simple" : true,
+ "unmarshallingType" : null,
+ "varargSetterDocumentation" : "/**A keyword that is used to filter on the name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.
name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "variable" : {
+ "timestampFormat" : null,
+ "variableDeclarationType" : "String",
+ "variableName" : "keyword",
+ "variableType" : "String",
+ "documentation" : "A keyword that is used to filter on the name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.
A keyword that is used to filter on the name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.
A keyword that is used to filter on the name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.
name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "fluentSetterMethodName" : "withKeyword",
+ "getterDocumentation" : "/**A keyword that is used to filter on the name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.
name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.*/",
+ "getterMethodName" : "getKeyword",
+ "getterModel" : {
+ "returnType" : "String",
+ "documentation" : null
+ },
+ "http" : {
+ "additionalMarshallingPath" : null,
+ "additionalUnmarshallingPath" : null,
+ "flattened" : false,
+ "greedy" : false,
+ "header" : false,
+ "isPayload" : false,
+ "isStreaming" : false,
+ "location" : null,
+ "marshallLocation" : "PAYLOAD",
+ "marshallLocationName" : "keyword",
+ "queryString" : false,
+ "requiresLength" : false,
+ "statusCode" : false,
+ "unmarshallLocationName" : "keyword",
+ "uri" : false
+ },
+ "idempotencyToken" : false,
+ "isBinary" : false,
+ "jsonValue" : false,
+ "list" : false,
+ "listModel" : null,
+ "map" : false,
+ "mapModel" : null,
+ "marshallingTargetClass" : "String",
+ "marshallingType" : "STRING",
+ "name" : "Keyword",
+ "sensitive" : false,
+ "setterDocumentation" : "/**A keyword that is used to filter on the name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.
name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.*/",
+ "setterMethodName" : "setKeyword",
+ "setterModel" : {
+ "timestampFormat" : null,
+ "variableDeclarationType" : "String",
+ "variableName" : "keyword",
+ "variableType" : "String",
+ "documentation" : "",
+ "simpleType" : "String",
+ "variableSetterType" : "String"
+ },
+ "shouldEmitLegacyEnumSetter" : false,
+ "shouldFullyQualify" : false,
+ "simple" : true,
+ "unmarshallingType" : null,
+ "varargSetterDocumentation" : "/**A keyword that is used to filter on the name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.
name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "variable" : {
+ "timestampFormat" : null,
+ "variableDeclarationType" : "String",
+ "variableName" : "keyword",
+ "variableType" : "String",
+ "documentation" : "A keyword that is used to filter on the name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.
The status used to filter test cases. Valid statuses are SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.
The status used to filter test cases. A TestCaseFilter can have one status. Valid values are:
SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
The status used to filter test cases. Valid statuses are SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.
SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "fluentSetterDocumentation" : "/**The status used to filter test cases. A TestCaseFilter can have one status. Valid values are:
SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
TestCaseFilter can have one status. Valid values are: SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
The status used to filter test cases. Valid statuses are SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.
SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.*/",
+ "getterDocumentation" : "/**The status used to filter test cases. A TestCaseFilter can have one status. Valid values are:
SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
TestCaseFilter can have one status. Valid values are: SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
The status used to filter test cases. Valid statuses are SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.
SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.*/",
+ "setterDocumentation" : "/**The status used to filter test cases. A TestCaseFilter can have one status. Valid values are:
SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
TestCaseFilter can have one status. Valid values are: SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
The status used to filter test cases. Valid statuses are SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.
SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "varargSetterDocumentation" : "/**The status used to filter test cases. A TestCaseFilter can have one status. Valid values are:
SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
TestCaseFilter can have one status. Valid values are: SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
The status used to filter test cases. Valid statuses are SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.
The status used to filter test cases. A TestCaseFilter can have one status. Valid values are:
SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
DeleteReportGroup: Deletes a report group. Before you delete a report group, you must delete its reports. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.
Deletes a report group. Before you delete a report group, you must delete its reports.
" }, "DeleteResourcePolicy":{ "name":"DeleteResourcePolicy", @@ -1650,7 +1650,11 @@ "members":{ "arn":{ "shape":"NonEmptyString", - "documentation":"The ARN of the report group to delete.
" + "documentation":"The ARN of the report group to delete.
" + }, + "deleteReports":{ + "shape":"Boolean", + "documentation":"If true, deletes any reports that belong to a report group before deleting the report group.
If false, you must delete any reports in the report group. Use ListReportsForReportGroup to get the reports in a report group. Use DeleteReport to delete the reports. If you call DeleteReportGroup for a report group that contains one or more reports, an exception is thrown.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see parameter store reference-key in the buildspec file.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see secrets manager reference-key in the buildspec file.
The type of environment variable. Valid values include:
PARAMETER_STORE: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see env/parameter-store in the AWS CodeBuild User Guide.
PLAINTEXT: An environment variable in plain text format. This is the default value.
SECRETS_MANAGER: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see env/secrets-manager in the AWS CodeBuild User Guide.
Information about an environment variable for a build project or a build.
" @@ -2790,7 +2794,7 @@ }, "image":{ "shape":"NonEmptyString", - "documentation":"The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: registry/repository:tag. For example, to specify an image with the tag \"latest,\" use registry/repository:latest.
For an image digest: registry/repository@digest. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use registry/repository@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The image tag or image digest that identifies the Docker image to use for this build project. Use the following formats:
For an image tag: <registry>/<repository>:<tag>. For example, in the Docker repository that CodeBuild uses to manage its Docker images, this would be aws/codebuild/standard:4.0. To specify the latest version of this image, this would be aws/codebuild/standard:latest.
For an image digest: <registry>/<repository>@<digest>. For example, to specify an image with the digest \"sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf,\" use <registry>/<repository>@sha256:cbbf2f9a99b47fc460d422812b6a5adff7dfee951d8fa2e4a98caa0382cfbdbf.
The status used to filter test cases. Valid statuses are SUCCEEDED, FAILED, ERROR, SKIPPED, and UNKNOWN. A TestCaseFilter can have one status.
The status used to filter test cases. A TestCaseFilter can have one status. Valid values are:
SUCCEEDED
FAILED
ERROR
SKIPPED
UNKNOWN
A keyword that is used to filter on the name or the prefix of the test cases. Only test cases where the keyword is a substring of the name or the prefix will be returned.
A filter used to return specific types of test cases.
" + "documentation":"A filter used to return specific types of test cases. In order to pass the filter, the report must meet all of the filter properties.
" }, "TestCases":{ "type":"list", diff --git a/aws-java-sdk-models/src/main/resources/models/codeguru-reviewer-2019-09-19-intermediate.json b/aws-java-sdk-models/src/main/resources/models/codeguru-reviewer-2019-09-19-intermediate.json index 7e26e76deb9b..fa521d0dd7a3 100644 --- a/aws-java-sdk-models/src/main/resources/models/codeguru-reviewer-2019-09-19-intermediate.json +++ b/aws-java-sdk-models/src/main/resources/models/codeguru-reviewer-2019-09-19-intermediate.json @@ -20,7 +20,7 @@ "customServiceMetadata" : null, "customServiceNameForRequest" : null, "customSignerProvider" : null, - "deprecatedSuppressions" : [ "ClientConstructors", "ClientMutationMethods", "EnumSetterOverload" ], + "deprecatedSuppressions" : [ "ClientMutationMethods", "ClientConstructors", "EnumSetterOverload" ], "emitLegacyEnumSetterFor" : null, "operationModifiers" : null, "operationsWithResponseStreamContentLengthValidation" : null, diff --git a/aws-java-sdk-models/src/main/resources/models/compute-optimizer-2019-11-01-intermediate.json b/aws-java-sdk-models/src/main/resources/models/compute-optimizer-2019-11-01-intermediate.json index 40bbbc60efda..6e0a305dc2ef 100644 --- a/aws-java-sdk-models/src/main/resources/models/compute-optimizer-2019-11-01-intermediate.json +++ b/aws-java-sdk-models/src/main/resources/models/compute-optimizer-2019-11-01-intermediate.json @@ -20,7 +20,7 @@ "customServiceMetadata" : null, "customServiceNameForRequest" : null, "customSignerProvider" : null, - "deprecatedSuppressions" : [ "ClientMutationMethods", "ClientConstructors", "EnumSetterOverload" ], + "deprecatedSuppressions" : [ "ClientConstructors", "EnumSetterOverload", "ClientMutationMethods" ], "emitLegacyEnumSetterFor" : null, "operationModifiers" : null, "operationsWithResponseStreamContentLengthValidation" : null, diff --git a/aws-java-sdk-models/src/main/resources/models/data.mediastore-2017-09-01-intermediate.json b/aws-java-sdk-models/src/main/resources/models/data.mediastore-2017-09-01-intermediate.json index 9d649b4e7282..21363144be70 100644 --- a/aws-java-sdk-models/src/main/resources/models/data.mediastore-2017-09-01-intermediate.json +++ b/aws-java-sdk-models/src/main/resources/models/data.mediastore-2017-09-01-intermediate.json @@ -20,7 +20,7 @@ "customServiceMetadata" : null, "customServiceNameForRequest" : null, "customSignerProvider" : null, - "deprecatedSuppressions" : [ "ClientMutationMethods", "ClientConstructors", "EnumSetterOverload" ], + "deprecatedSuppressions" : [ "EnumSetterOverload", "ClientMutationMethods", "ClientConstructors" ], "emitLegacyEnumSetterFor" : null, "operationModifiers" : null, "operationsWithResponseStreamContentLengthValidation" : null, diff --git a/aws-java-sdk-models/src/main/resources/models/dataexchange-2017-07-25-intermediate.json b/aws-java-sdk-models/src/main/resources/models/dataexchange-2017-07-25-intermediate.json index fd5171808395..eb8096a50043 100644 --- a/aws-java-sdk-models/src/main/resources/models/dataexchange-2017-07-25-intermediate.json +++ b/aws-java-sdk-models/src/main/resources/models/dataexchange-2017-07-25-intermediate.json @@ -20,7 +20,7 @@ "customServiceMetadata" : null, "customServiceNameForRequest" : null, "customSignerProvider" : null, - "deprecatedSuppressions" : [ "ClientMutationMethods", "EnumSetterOverload", "ClientConstructors" ], + "deprecatedSuppressions" : [ "ClientConstructors", "EnumSetterOverload", "ClientMutationMethods" ], "emitLegacyEnumSetterFor" : null, "operationModifiers" : null, "operationsWithResponseStreamContentLengthValidation" : null, diff --git a/aws-java-sdk-models/src/main/resources/models/datasync-2018-11-09-intermediate.json b/aws-java-sdk-models/src/main/resources/models/datasync-2018-11-09-intermediate.json index 876f45dabdca..6d718a1e6eef 100644 --- a/aws-java-sdk-models/src/main/resources/models/datasync-2018-11-09-intermediate.json +++ b/aws-java-sdk-models/src/main/resources/models/datasync-2018-11-09-intermediate.json @@ -20,7 +20,7 @@ "customServiceMetadata" : null, "customServiceNameForRequest" : null, "customSignerProvider" : null, - "deprecatedSuppressions" : [ "ClientConstructors", "ClientMutationMethods", "EnumSetterOverload" ], + "deprecatedSuppressions" : [ "ClientMutationMethods", "ClientConstructors", "EnumSetterOverload" ], "emitLegacyEnumSetterFor" : null, "operationModifiers" : null, "operationsWithResponseStreamContentLengthValidation" : null, diff --git a/aws-java-sdk-models/src/main/resources/models/dax-2017-04-19-intermediate.json b/aws-java-sdk-models/src/main/resources/models/dax-2017-04-19-intermediate.json index 71057b0302f5..6e297e1daea2 100644 --- a/aws-java-sdk-models/src/main/resources/models/dax-2017-04-19-intermediate.json +++ b/aws-java-sdk-models/src/main/resources/models/dax-2017-04-19-intermediate.json @@ -20,7 +20,7 @@ "customServiceMetadata" : null, "customServiceNameForRequest" : null, "customSignerProvider" : null, - "deprecatedSuppressions" : [ "EnumSetterOverload", "ClientMutationMethods", "ClientConstructors" ], + "deprecatedSuppressions" : [ "ClientMutationMethods", "ClientConstructors", "EnumSetterOverload" ], "emitLegacyEnumSetterFor" : { "DescribeEventsRequest" : [ "SourceType" ], "Event" : [ "SourceType" ], diff --git a/aws-java-sdk-models/src/main/resources/models/detective-2018-10-26-intermediate.json b/aws-java-sdk-models/src/main/resources/models/detective-2018-10-26-intermediate.json index c18ebb7c1871..c14b9c3f645a 100644 --- a/aws-java-sdk-models/src/main/resources/models/detective-2018-10-26-intermediate.json +++ b/aws-java-sdk-models/src/main/resources/models/detective-2018-10-26-intermediate.json @@ -20,7 +20,7 @@ "customServiceMetadata" : null, "customServiceNameForRequest" : null, "customSignerProvider" : null, - "deprecatedSuppressions" : [ "ClientMutationMethods", "ClientConstructors", "EnumSetterOverload" ], + "deprecatedSuppressions" : [ "EnumSetterOverload", "ClientMutationMethods", "ClientConstructors" ], "emitLegacyEnumSetterFor" : null, "operationModifiers" : null, "operationsWithResponseStreamContentLengthValidation" : null, diff --git a/aws-java-sdk-models/src/main/resources/models/devices.iot1click-2018-05-14-intermediate.json b/aws-java-sdk-models/src/main/resources/models/devices.iot1click-2018-05-14-intermediate.json index 8609cb670d81..5e7c2cb9f9e9 100644 --- a/aws-java-sdk-models/src/main/resources/models/devices.iot1click-2018-05-14-intermediate.json +++ b/aws-java-sdk-models/src/main/resources/models/devices.iot1click-2018-05-14-intermediate.json @@ -20,7 +20,7 @@ "customServiceMetadata" : null, "customServiceNameForRequest" : null, "customSignerProvider" : null, - "deprecatedSuppressions" : [ "ClientMutationMethods", "EnumSetterOverload", "ClientConstructors" ], + "deprecatedSuppressions" : [ "ClientMutationMethods", "ClientConstructors", "EnumSetterOverload" ], "emitLegacyEnumSetterFor" : null, "operationModifiers" : null, "operationsWithResponseStreamContentLengthValidation" : null, diff --git a/aws-java-sdk-models/src/main/resources/models/ec2-instance-connect-2018-04-02-intermediate.json b/aws-java-sdk-models/src/main/resources/models/ec2-instance-connect-2018-04-02-intermediate.json index 07a36887c78d..0d6259dd2cd9 100644 --- a/aws-java-sdk-models/src/main/resources/models/ec2-instance-connect-2018-04-02-intermediate.json +++ b/aws-java-sdk-models/src/main/resources/models/ec2-instance-connect-2018-04-02-intermediate.json @@ -20,7 +20,7 @@ "customServiceMetadata" : null, "customServiceNameForRequest" : null, "customSignerProvider" : null, - "deprecatedSuppressions" : [ "ClientMutationMethods", "EnumSetterOverload", "ClientConstructors" ], + "deprecatedSuppressions" : [ "ClientMutationMethods", "ClientConstructors", "EnumSetterOverload" ], "emitLegacyEnumSetterFor" : null, "operationModifiers" : null, "operationsWithResponseStreamContentLengthValidation" : null, diff --git a/aws-java-sdk-models/src/main/resources/models/eks-2017-11-01-intermediate.json b/aws-java-sdk-models/src/main/resources/models/eks-2017-11-01-intermediate.json index 115c5c876323..fd5b55bb7c45 100644 --- a/aws-java-sdk-models/src/main/resources/models/eks-2017-11-01-intermediate.json +++ b/aws-java-sdk-models/src/main/resources/models/eks-2017-11-01-intermediate.json @@ -20,7 +20,7 @@ "customServiceMetadata" : null, "customServiceNameForRequest" : null, "customSignerProvider" : null, - "deprecatedSuppressions" : [ "ClientConstructors", "ClientMutationMethods", "EnumSetterOverload" ], + "deprecatedSuppressions" : [ "ClientConstructors", "EnumSetterOverload", "ClientMutationMethods" ], "emitLegacyEnumSetterFor" : null, "operationModifiers" : null, "operationsWithResponseStreamContentLengthValidation" : null, diff --git a/aws-java-sdk-models/src/main/resources/models/elasticloadbalancing-2015-12-01-intermediate.json b/aws-java-sdk-models/src/main/resources/models/elasticloadbalancing-2015-12-01-intermediate.json index ddb49042ac95..91661ba8f79b 100644 --- a/aws-java-sdk-models/src/main/resources/models/elasticloadbalancing-2015-12-01-intermediate.json +++ b/aws-java-sdk-models/src/main/resources/models/elasticloadbalancing-2015-12-01-intermediate.json @@ -8116,6 +8116,75 @@ "variableSetterType" : "String" }, "xmlNameSpaceUri" : null + }, { + "c2jName" : "OutpostId", + "c2jShape" : "OutpostId", + "deprecated" : false, + "documentation" : "[Application Load Balancers on Outposts] The ID of the Outpost.
", + "endpointDiscoveryId" : false, + "enumType" : null, + "fluentSetterDocumentation" : "/**[Application Load Balancers on Outposts] The ID of the Outpost.
\n@param outpostId [Application Load Balancers on Outposts] The ID of the Outpost.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterMethodName" : "withOutpostId", + "getterDocumentation" : "/**[Application Load Balancers on Outposts] The ID of the Outpost.
\n@return [Application Load Balancers on Outposts] The ID of the Outpost.*/", + "getterMethodName" : "getOutpostId", + "getterModel" : { + "returnType" : "String", + "documentation" : null + }, + "http" : { + "additionalMarshallingPath" : null, + "additionalUnmarshallingPath" : null, + "flattened" : false, + "greedy" : false, + "header" : false, + "isPayload" : false, + "isStreaming" : false, + "location" : null, + "marshallLocation" : "PAYLOAD", + "marshallLocationName" : "OutpostId", + "queryString" : false, + "requiresLength" : false, + "statusCode" : false, + "unmarshallLocationName" : "OutpostId", + "uri" : false + }, + "idempotencyToken" : false, + "isBinary" : false, + "jsonValue" : false, + "list" : false, + "listModel" : null, + "map" : false, + "mapModel" : null, + "marshallingTargetClass" : "String", + "marshallingType" : "STRING", + "name" : "OutpostId", + "sensitive" : false, + "setterDocumentation" : "/**[Application Load Balancers on Outposts] The ID of the Outpost.
\n@param outpostId [Application Load Balancers on Outposts] The ID of the Outpost.*/", + "setterMethodName" : "setOutpostId", + "setterModel" : { + "timestampFormat" : null, + "variableDeclarationType" : "String", + "variableName" : "outpostId", + "variableType" : "String", + "documentation" : "", + "simpleType" : "String", + "variableSetterType" : "String" + }, + "shouldEmitLegacyEnumSetter" : false, + "shouldFullyQualify" : false, + "simple" : true, + "unmarshallingType" : null, + "varargSetterDocumentation" : "/**[Application Load Balancers on Outposts] The ID of the Outpost.
\n@param outpostId [Application Load Balancers on Outposts] The ID of the Outpost.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "variable" : { + "timestampFormat" : null, + "variableDeclarationType" : "String", + "variableName" : "outpostId", + "variableType" : "String", + "documentation" : "[Application Load Balancers on Outposts] The ID of the Outpost.
", + "simpleType" : "String", + "variableSetterType" : "String" + }, + "xmlNameSpaceUri" : null }, { "c2jName" : "LoadBalancerAddresses", "c2jShape" : "LoadBalancerAddresses", @@ -8425,6 +8494,76 @@ }, "xmlNameSpaceUri" : null }, + "OutpostId" : { + "c2jName" : "OutpostId", + "c2jShape" : "OutpostId", + "deprecated" : false, + "documentation" : "[Application Load Balancers on Outposts] The ID of the Outpost.
", + "endpointDiscoveryId" : false, + "enumType" : null, + "fluentSetterDocumentation" : "/**[Application Load Balancers on Outposts] The ID of the Outpost.
\n@param outpostId [Application Load Balancers on Outposts] The ID of the Outpost.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterMethodName" : "withOutpostId", + "getterDocumentation" : "/**[Application Load Balancers on Outposts] The ID of the Outpost.
\n@return [Application Load Balancers on Outposts] The ID of the Outpost.*/", + "getterMethodName" : "getOutpostId", + "getterModel" : { + "returnType" : "String", + "documentation" : null + }, + "http" : { + "additionalMarshallingPath" : null, + "additionalUnmarshallingPath" : null, + "flattened" : false, + "greedy" : false, + "header" : false, + "isPayload" : false, + "isStreaming" : false, + "location" : null, + "marshallLocation" : "PAYLOAD", + "marshallLocationName" : "OutpostId", + "queryString" : false, + "requiresLength" : false, + "statusCode" : false, + "unmarshallLocationName" : "OutpostId", + "uri" : false + }, + "idempotencyToken" : false, + "isBinary" : false, + "jsonValue" : false, + "list" : false, + "listModel" : null, + "map" : false, + "mapModel" : null, + "marshallingTargetClass" : "String", + "marshallingType" : "STRING", + "name" : "OutpostId", + "sensitive" : false, + "setterDocumentation" : "/**[Application Load Balancers on Outposts] The ID of the Outpost.
\n@param outpostId [Application Load Balancers on Outposts] The ID of the Outpost.*/", + "setterMethodName" : "setOutpostId", + "setterModel" : { + "timestampFormat" : null, + "variableDeclarationType" : "String", + "variableName" : "outpostId", + "variableType" : "String", + "documentation" : "", + "simpleType" : "String", + "variableSetterType" : "String" + }, + "shouldEmitLegacyEnumSetter" : false, + "shouldFullyQualify" : false, + "simple" : true, + "unmarshallingType" : null, + "varargSetterDocumentation" : "/**[Application Load Balancers on Outposts] The ID of the Outpost.
\n@param outpostId [Application Load Balancers on Outposts] The ID of the Outpost.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "variable" : { + "timestampFormat" : null, + "variableDeclarationType" : "String", + "variableName" : "outpostId", + "variableType" : "String", + "documentation" : "[Application Load Balancers on Outposts] The ID of the Outpost.
", + "simpleType" : "String", + "variableSetterType" : "String" + }, + "xmlNameSpaceUri" : null + }, "SubnetId" : { "c2jName" : "SubnetId", "c2jShape" : "SubnetId", @@ -11294,12 +11433,12 @@ "c2jName" : "Subnets", "c2jShape" : "Subnets", "deprecated" : false, - "documentation" : "The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.
", + "documentation" : "The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.
", "endpointDiscoveryId" : false, "enumType" : null, - "fluentSetterDocumentation" : "/**The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.
\n@param subnets The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.
\n@param subnets The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withSubnets", - "getterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.
\n@return The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.*/", + "getterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.
\n@return The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.*/",
"getterMethodName" : "getSubnets",
"getterModel" : {
"returnType" : "java.util.List The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. [Network Load Balancers] You can specify subnets from one or more Availability Zones.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.*/", + "setterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.
\n@param subnets The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.*/", "setterMethodName" : "setSubnets", "setterModel" : { "timestampFormat" : null, @@ -11432,13 +11571,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setSubnets(java.util.Collection)} or {@link #withSubnets(java.util.Collection)} if you want to override the existing values.
\n@param subnets The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setSubnets(java.util.Collection)} or {@link #withSubnets(java.util.Collection)} if you want to override the existing values.
\n@param subnets The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "java.util.List The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. [Network Load Balancers] You can specify subnets from one or more Availability Zones. The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. [Application Load Balancers on Outposts] You must specify one Outpost subnet. [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. [Network Load Balancers] You can specify subnets from one or more Availability Zones. The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets. [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet. The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets. [Application Load Balancers on Outposts] You must specify one Outpost subnet. [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet. The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets. [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
\n@param subnetMappings The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withSubnetMappings", - "getterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
\n@return The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.*/", + "getterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
\n@return The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.*/",
"getterMethodName" : "getSubnetMappings",
"getterModel" : {
"returnType" : "java.util.List The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets. [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.*/", + "setterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
\n@param subnetMappings The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.*/", "setterMethodName" : "setSubnetMappings", "setterModel" : { "timestampFormat" : null, @@ -11585,13 +11724,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setSubnetMappings(java.util.Collection)} or {@link #withSubnetMappings(java.util.Collection)} if you want to override the existing values.
\n@param subnetMappings The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setSubnetMappings(java.util.Collection)} or {@link #withSubnetMappings(java.util.Collection)} if you want to override the existing values.
\n@param subnetMappings The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "java.util.List The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets. [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet. The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets. [Application Load Balancers on Outposts] You must specify one Outpost subnet. [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet. [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets. [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet. The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets. [Application Load Balancers on Outposts] You must specify one Outpost subnet. [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet. The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets. [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
\n@param subnetMappings The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withSubnetMappings", - "getterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
\n@return The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.*/", + "getterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
\n@return The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.*/",
"getterMethodName" : "getSubnetMappings",
"getterModel" : {
"returnType" : "java.util.List The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets. [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.*/", + "setterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
\n@param subnetMappings The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.*/", "setterMethodName" : "setSubnetMappings", "setterModel" : { "timestampFormat" : null, @@ -12617,13 +12895,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setSubnetMappings(java.util.Collection)} or {@link #withSubnetMappings(java.util.Collection)} if you want to override the existing values.
\n@param subnetMappings The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setSubnetMappings(java.util.Collection)} or {@link #withSubnetMappings(java.util.Collection)} if you want to override the existing values.
\n@param subnetMappings The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "java.util.List The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets. [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet. The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets. [Application Load Balancers on Outposts] You must specify one Outpost subnet. [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet. The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. [Network Load Balancers] You can specify subnets from one or more Availability Zones. The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. [Application Load Balancers on Outposts] You must specify one Outpost subnet. [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. [Network Load Balancers] You can specify subnets from one or more Availability Zones. The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. [Network Load Balancers] You can specify subnets from one or more Availability Zones.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.
\n@param subnets The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withSubnets", - "getterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.
\n@return The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.*/", + "getterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.
\n@return The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.*/",
"getterMethodName" : "getSubnets",
"getterModel" : {
"returnType" : "java.util.List The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. [Network Load Balancers] You can specify subnets from one or more Availability Zones.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.*/", + "setterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.
\n@param subnets The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.*/", "setterMethodName" : "setSubnets", "setterModel" : { "timestampFormat" : null, @@ -12771,13 +13049,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setSubnets(java.util.Collection)} or {@link #withSubnets(java.util.Collection)} if you want to override the existing values.
\n@param subnets The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.
\nNOTE: This method appends the values to the existing list (if any). Use {@link #setSubnets(java.util.Collection)} or {@link #withSubnets(java.util.Collection)} if you want to override the existing values.
\n@param subnets The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings.[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "java.util.List The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. [Network Load Balancers] You can specify subnets from one or more Availability Zones. The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. [Application Load Balancers on Outposts] You must specify one Outpost subnet. [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. [Network Load Balancers] You can specify subnets from one or more Availability Zones. The Availability Zones for the load balancer. The subnets for the load balancer. The Availability Zones for the load balancer. The subnets for the load balancer. The Availability Zones for the load balancer. The subnets for the load balancer. The Availability Zones for the load balancer. The subnets for the load balancer. The Availability Zones for the load balancer. NOTE: This method appends the values to the existing list (if any). Use {@link #setAvailabilityZones(java.util.Collection)} or {@link #withAvailabilityZones(java.util.Collection)} if you want to override the existing values. The subnets for the load balancer. NOTE: This method appends the values to the existing list (if any). Use {@link #setAvailabilityZones(java.util.Collection)} or {@link #withAvailabilityZones(java.util.Collection)} if you want to override the existing values. The Availability Zones for the load balancer. The subnets for the load balancer. [Application Load Balancers on Outposts] The ID of the customer-owned address pool. [Application Load Balancers on Outposts] The ID of the customer-owned address pool. [Application Load Balancers on Outposts] The ID of the customer-owned address pool. [Application Load Balancers on Outposts] The ID of the customer-owned address pool. [Application Load Balancers on Outposts] The ID of the customer-owned address pool. [Application Load Balancers on Outposts] The ID of the customer-owned address pool. The Availability Zones for the load balancer. The subnets for the load balancer. The Availability Zones for the load balancer. The subnets for the load balancer. The Availability Zones for the load balancer. The subnets for the load balancer. The Availability Zones for the load balancer. The subnets for the load balancer. The Availability Zones for the load balancer. NOTE: This method appends the values to the existing list (if any). Use {@link #setAvailabilityZones(java.util.Collection)} or {@link #withAvailabilityZones(java.util.Collection)} if you want to override the existing values. The subnets for the load balancer. NOTE: This method appends the values to the existing list (if any). Use {@link #setAvailabilityZones(java.util.Collection)} or {@link #withAvailabilityZones(java.util.Collection)} if you want to override the existing values. The Availability Zones for the load balancer. The subnets for the load balancer. [Application Load Balancers on Outposts] The ID of the customer-owned address pool. [Application Load Balancers on Outposts] The ID of the customer-owned address pool. [Application Load Balancers on Outposts] The ID of the customer-owned address pool. [Application Load Balancers on Outposts] The ID of the customer-owned address pool. [Application Load Balancers on Outposts] The ID of the customer-owned address pool. [Application Load Balancers on Outposts] The ID of the customer-owned address pool. Information about the subnet and Availability Zone. Information about the subnets. Information about the subnet and Availability Zone. Information about the subnets. Information about the subnet and Availability Zone. Information about the subnets. Information about the subnet and Availability Zone. Information about the subnets. Information about the subnet and Availability Zone. NOTE: This method appends the values to the existing list (if any). Use {@link #setAvailabilityZones(java.util.Collection)} or {@link #withAvailabilityZones(java.util.Collection)} if you want to override the existing values. Information about the subnets. NOTE: This method appends the values to the existing list (if any). Use {@link #setAvailabilityZones(java.util.Collection)} or {@link #withAvailabilityZones(java.util.Collection)} if you want to override the existing values. Information about the subnet and Availability Zone. Information about the subnets. Information about the subnet and Availability Zone. Information about the subnets. Information about the subnet and Availability Zone. Information about the subnets. Information about the subnet and Availability Zone. Information about the subnets. Information about the subnet and Availability Zone. Information about the subnets. Information about the subnet and Availability Zone. NOTE: This method appends the values to the existing list (if any). Use {@link #setAvailabilityZones(java.util.Collection)} or {@link #withAvailabilityZones(java.util.Collection)} if you want to override the existing values. Information about the subnets. NOTE: This method appends the values to the existing list (if any). Use {@link #setAvailabilityZones(java.util.Collection)} or {@link #withAvailabilityZones(java.util.Collection)} if you want to override the existing values. Information about the subnet and Availability Zone. Information about the subnets. The ID of the subnet. You can specify one subnet per Availability Zone. [Application Load Balancers on Outposts] The ID of the Outpost. [Network Load Balancers] If you need static IP addresses for your load balancer, you can specify one Elastic IP address per Availability Zone when you create an internal-facing load balancer. For internal load balancers, you can specify a private IP address from the IPv4 range of the subnet. The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. [Network Load Balancers] You can specify subnets from one or more Availability Zones. The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. [Application Load Balancers on Outposts] You must specify one Outpost subnet. [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. [Network Load Balancers] You can specify subnets from one or more Availability Zones. The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets. [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet. The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings. [Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets. [Application Load Balancers on Outposts] You must specify one Outpost subnet. [Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones. [Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet. [Application Load Balancers] The type of IP addresses used by the subnets for your load balancer. The possible values are [Application Load Balancers on Outposts] The ID of the customer-owned address pool (CoIP pool). The Availability Zones for the load balancer. The subnets for the load balancer. The type of IP addresses used by the subnets for your load balancer. The possible values are [Application Load Balancers on Outposts] The ID of the customer-owned address pool. Information about a load balancer. Information about the subnet and Availability Zone. Information about the subnets. The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the Set to When you set the You can only set the The Regions where you can set the US East (N. Virginia) (us-east-1) US West (Oregon) (us-west-2) Asia Pacific (Sydney) (ap-southeast-2) EU (Ireland) (eu-west-1) In other Regions, the Asia Pacific (Singapore) (ap-southeast-1) Asia Pacific (Tokyo) (ap-northeast-1) EU (Frankfurt) (eu-central-1) EU (London) (eu-west-2) Set to When you set the You can only set the The Regions where you can set the US East (N. Virginia) (us-east-1) US West (Oregon) (us-west-2) Asia Pacific (Sydney) (ap-southeast-2) EU (Ireland) (eu-west-1) In other Regions, the Asia Pacific (Singapore) (ap-southeast-1) Asia Pacific (Tokyo) (ap-northeast-1) EU (Frankfurt) (eu-central-1) EU (London) (eu-west-2) Set to When you set the You can only set the The Regions where you can set the US East (N. Virginia) (us-east-1) US West (Oregon) (us-west-2) Asia Pacific (Sydney) (ap-southeast-2) EU (Ireland) (eu-west-1) In other Regions, the Asia Pacific (Singapore) (ap-southeast-1) Asia Pacific (Tokyo) (ap-northeast-1) EU (Frankfurt) (eu-central-1) EU (London) (eu-west-2)ipv4 (for IPv4 addresses) and dualstack (for IPv4 and IPv6 addresses). Internal load balancers must use ipv4.ipv4 (for IPv4 addresses) and dualstack (for IPv4 and IPv6 addresses).true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"fluentSetterMethodName" : "withEnableModelImprovements",
- "getterDocumentation" : "/**true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.*/",
"getterMethodName" : "getEnableModelImprovements",
"getterModel" : {
"returnType" : "Boolean",
@@ -9820,7 +9820,7 @@
"marshallingType" : "BOOLEAN",
"name" : "EnableModelImprovements",
"sensitive" : false,
- "setterDocumentation" : "/**true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.*/",
"setterMethodName" : "setEnableModelImprovements",
"setterModel" : {
"timestampFormat" : null,
@@ -9835,13 +9835,13 @@
"shouldFullyQualify" : false,
"simple" : true,
"unmarshallingType" : null,
- "varargSetterDocumentation" : "/**true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "Boolean",
"variableName" : "enableModelImprovements",
"variableType" : "Boolean",
- "documentation" : "true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"fluentSetterMethodName" : "withEnableModelImprovements",
- "getterDocumentation" : "/**true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.*/",
"getterMethodName" : "getEnableModelImprovements",
"getterModel" : {
"returnType" : "Boolean",
@@ -10450,7 +10450,7 @@
"marshallingType" : "BOOLEAN",
"name" : "EnableModelImprovements",
"sensitive" : false,
- "setterDocumentation" : "/**true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.*/",
"setterMethodName" : "setEnableModelImprovements",
"setterModel" : {
"timestampFormat" : null,
@@ -10465,13 +10465,13 @@
"shouldFullyQualify" : false,
"simple" : true,
"unmarshallingType" : null,
- "varargSetterDocumentation" : "/**true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "Boolean",
"variableName" : "enableModelImprovements",
"variableType" : "Boolean",
- "documentation" : "true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"fluentSetterMethodName" : "withEnableModelImprovements",
- "getterDocumentation" : "/**true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.*/",
"getterMethodName" : "getEnableModelImprovements",
"getterModel" : {
"returnType" : "Boolean",
@@ -27071,7 +27071,7 @@
"marshallingType" : "BOOLEAN",
"name" : "EnableModelImprovements",
"sensitive" : false,
- "setterDocumentation" : "/**true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.*/",
"setterMethodName" : "setEnableModelImprovements",
"setterModel" : {
"timestampFormat" : null,
@@ -27086,13 +27086,13 @@
"shouldFullyQualify" : false,
"simple" : true,
"unmarshallingType" : null,
- "varargSetterDocumentation" : "/**true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "Boolean",
"variableName" : "enableModelImprovements",
"variableType" : "Boolean",
- "documentation" : "true indicates that the bot is using the imoprovements, otherwise, false.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "fluentSetterDocumentation" : "/**AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"fluentSetterMethodName" : "withNluIntentConfidenceThreshold",
- "getterDocumentation" : "/**AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.*/",
+ "getterDocumentation" : "/**AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.*/",
"getterMethodName" : "getNluIntentConfidenceThreshold",
"getterModel" : {
"returnType" : "Double",
@@ -27140,7 +27140,7 @@
"marshallingType" : "DOUBLE",
"name" : "NluIntentConfidenceThreshold",
"sensitive" : false,
- "setterDocumentation" : "/**AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.*/",
+ "setterDocumentation" : "/**AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.*/",
"setterMethodName" : "setNluIntentConfidenceThreshold",
"setterModel" : {
"timestampFormat" : null,
@@ -27155,13 +27155,13 @@
"shouldFullyQualify" : false,
"simple" : true,
"unmarshallingType" : null,
- "varargSetterDocumentation" : "/**AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "varargSetterDocumentation" : "/**AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "Double",
"variableName" : "nluIntentConfidenceThreshold",
"variableType" : "Double",
- "documentation" : "AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"fluentSetterMethodName" : "withEnableModelImprovements",
- "getterDocumentation" : "/**true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.*/",
"getterMethodName" : "getEnableModelImprovements",
"getterModel" : {
"returnType" : "Boolean",
@@ -28598,7 +28598,7 @@
"marshallingType" : "BOOLEAN",
"name" : "EnableModelImprovements",
"sensitive" : false,
- "setterDocumentation" : "/**true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.*/",
"setterMethodName" : "setEnableModelImprovements",
"setterModel" : {
"timestampFormat" : null,
@@ -28613,13 +28613,13 @@
"shouldFullyQualify" : false,
"simple" : true,
"unmarshallingType" : null,
- "varargSetterDocumentation" : "/**true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "Boolean",
"variableName" : "enableModelImprovements",
"variableType" : "Boolean",
- "documentation" : "true indicates that the bot is using the imoprovements, otherwise, false.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "fluentSetterDocumentation" : "/**AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"fluentSetterMethodName" : "withNluIntentConfidenceThreshold",
- "getterDocumentation" : "/**AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.*/",
+ "getterDocumentation" : "/**AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.*/",
"getterMethodName" : "getNluIntentConfidenceThreshold",
"getterModel" : {
"returnType" : "Double",
@@ -29172,7 +29172,7 @@
"marshallingType" : "DOUBLE",
"name" : "NluIntentConfidenceThreshold",
"sensitive" : false,
- "setterDocumentation" : "/**AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.*/",
+ "setterDocumentation" : "/**AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.*/",
"setterMethodName" : "setNluIntentConfidenceThreshold",
"setterModel" : {
"timestampFormat" : null,
@@ -29187,13 +29187,13 @@
"shouldFullyQualify" : false,
"simple" : true,
"unmarshallingType" : null,
- "varargSetterDocumentation" : "/**AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "varargSetterDocumentation" : "/**AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "Double",
"variableName" : "nluIntentConfidenceThreshold",
"variableType" : "Double",
- "documentation" : "AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot. enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.enableModelImprovements parameter to true are:
enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
",
+ "documentation" : "true to enable access to natural language understanding improvements. enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.enableModelImprovements parameter to true are:
enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
",
"endpointDiscoveryId" : false,
"enumType" : null,
- "fluentSetterDocumentation" : "/**true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot. enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.enableModelImprovements parameter to true are:
enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
\n@param enableModelImprovements Set to true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable access to natural language understanding improvements.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
true to enable access to natural language understanding improvements. When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot. When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable access to natural language understanding improvements.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
true to enable access to natural language understanding improvements. When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot. When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable access to natural language understanding improvements.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
true to enable access to natural language understanding improvements. When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot. When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable access to natural language understanding improvements.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
true to enable access to natural language understanding improvements. When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable access to natural language understanding improvements.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot. You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot. You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot. You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot. You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot. You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot. You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot. You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot. You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
", + "documentation" : "When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
", "endpointDiscoveryId" : false, "enumType" : null, - "fluentSetterDocumentation" : "/**When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
\n@param abortStatement When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined inabortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type. For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**
When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
\n@param abortStatement When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined inabortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type. For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withAbortStatement", - "getterDocumentation" : "/**
When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
\n@return When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined inabortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type. For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.*/", + "getterDocumentation" : "/**
When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
\n@return When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined inabortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type. For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.*/", "getterMethodName" : "getAbortStatement", "getterModel" : { "returnType" : "Statement", @@ -55834,7 +55837,7 @@ "marshallingType" : "STRUCTURED", "name" : "AbortStatement", "sensitive" : false, - "setterDocumentation" : "/**
When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
\n@param abortStatement When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined inabortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type. For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.*/", + "setterDocumentation" : "/**
When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
\n@param abortStatement When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined inabortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type. For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.*/", "setterMethodName" : "setAbortStatement", "setterModel" : { "timestampFormat" : null, @@ -55849,13 +55852,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**
When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
\n@param abortStatement When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined inabortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type. For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**
When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
\n@param abortStatement When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined inabortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type. For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.\n@return Returns a reference to this object so that method calls can be chained together.*/", "variable" : { "timestampFormat" : null, "variableDeclarationType" : "Statement", "variableName" : "abortStatement", "variableType" : "Statement", - "documentation" : "
When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
", + "documentation" : "When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
", "simpleType" : "Statement", "variableSetterType" : "Statement" }, @@ -56571,12 +56574,12 @@ "c2jName" : "abortStatement", "c2jShape" : "Statement", "deprecated" : false, - "documentation" : "When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
", + "documentation" : "When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
", "endpointDiscoveryId" : false, "enumType" : null, - "fluentSetterDocumentation" : "/**When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
\n@param abortStatement When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined inabortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type. For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**
When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
\n@param abortStatement When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined inabortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type. For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withAbortStatement", - "getterDocumentation" : "/**
When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
\n@return When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined inabortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type. For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.*/", + "getterDocumentation" : "/**
When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
\n@return When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined inabortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type. For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.*/", "getterMethodName" : "getAbortStatement", "getterModel" : { "returnType" : "Statement", @@ -56610,7 +56613,7 @@ "marshallingType" : "STRUCTURED", "name" : "AbortStatement", "sensitive" : false, - "setterDocumentation" : "/**
When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
\n@param abortStatement When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined inabortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type. For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.*/", + "setterDocumentation" : "/**
When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
\n@param abortStatement When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined inabortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type. For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.*/", "setterMethodName" : "setAbortStatement", "setterModel" : { "timestampFormat" : null, @@ -56625,13 +56628,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**
When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
\n@param abortStatement When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined inabortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type. For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**
When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
\n@param abortStatement When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined inabortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type. For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.\n@return Returns a reference to this object so that method calls can be chained together.*/", "variable" : { "timestampFormat" : null, "variableDeclarationType" : "Statement", "variableName" : "abortStatement", "variableType" : "Statement", - "documentation" : "
When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
", + "documentation" : "When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in abortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type.
For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times.
For example, in a pizza ordering application, OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.
If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent.
", "simpleType" : "Statement", "variableSetterType" : "Statement" }, @@ -57061,12 +57064,12 @@ "c2jName" : "enableModelImprovements", "c2jShape" : "Boolean", "deprecated" : false, - "documentation" : "Set to true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable access to natural language understanding improvements.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot. When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable access to natural language understanding improvements.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
true to enable access to natural language understanding improvements. When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot. When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable access to natural language understanding improvements.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
true to enable access to natural language understanding improvements. When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot. When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable access to natural language understanding improvements.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
true to enable access to natural language understanding improvements. When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot. When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable access to natural language understanding improvements.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
true to enable access to natural language understanding improvements. When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Set to true to enable access to natural language understanding improvements.
When you set the enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.
You can only set the enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.
The Regions where you can set the enableModelImprovements parameter to true are:
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
Asia Pacific (Singapore) (ap-southeast-1)
Asia Pacific (Tokyo) (ap-northeast-1)
EU (Frankfurt) (eu-central-1)
EU (London) (eu-west-2)
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot. You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot. You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot. You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot. You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot. You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot. You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot. You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot. You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Determines the threshold where Amazon Lex will insert the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
You must set the enableModelImprovements parameter to true to use confidence scores.
US East (N. Virginia) (us-east-1)
US West (Oregon) (us-west-2)
Asia Pacific (Sydney) (ap-southeast-2)
EU (Ireland) (eu-west-1)
In other Regions, the enableModelImprovements parameter is set to true by default.
For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
AMAZON.FallbackIntent
IntentA
IntentB
IntentC
Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.
", + "documentation" : "Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the imoprovements, otherwise, false.
Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.
\n@param enableModelImprovements Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the imoprovements, otherwise, false.
true indicates that the bot is using the imoprovements, otherwise, false.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"fluentSetterMethodName" : "withEnableModelImprovements",
- "getterDocumentation" : "/**Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.
\n@return Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.*/", + "getterDocumentation" : "/**Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the imoprovements, otherwise, false.
true indicates that the bot is using the imoprovements, otherwise, false.*/",
"getterMethodName" : "getEnableModelImprovements",
"getterModel" : {
"returnType" : "Boolean",
@@ -58229,7 +58232,7 @@
"marshallingType" : "BOOLEAN",
"name" : "EnableModelImprovements",
"sensitive" : false,
- "setterDocumentation" : "/**Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.
\n@param enableModelImprovements Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.*/", + "setterDocumentation" : "/**Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the imoprovements, otherwise, false.
true indicates that the bot is using the imoprovements, otherwise, false.*/",
"setterMethodName" : "setEnableModelImprovements",
"setterModel" : {
"timestampFormat" : null,
@@ -58244,13 +58247,13 @@
"shouldFullyQualify" : false,
"simple" : true,
"unmarshallingType" : null,
- "varargSetterDocumentation" : "/**Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.
\n@param enableModelImprovements Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the imoprovements, otherwise, false.
true indicates that the bot is using the imoprovements, otherwise, false.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "Boolean",
"variableName" : "enableModelImprovements",
"variableType" : "Boolean",
- "documentation" : "Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.
", + "documentation" : "Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the imoprovements, otherwise, false.
The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "fluentSetterDocumentation" : "/**The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"fluentSetterMethodName" : "withNluIntentConfidenceThreshold",
- "getterDocumentation" : "/**The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.*/",
+ "getterDocumentation" : "/**The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.*/",
"getterMethodName" : "getNluIntentConfidenceThreshold",
"getterModel" : {
"returnType" : "Double",
@@ -58298,7 +58301,7 @@
"marshallingType" : "DOUBLE",
"name" : "NluIntentConfidenceThreshold",
"sensitive" : false,
- "setterDocumentation" : "/**The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.*/",
+ "setterDocumentation" : "/**The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.*/",
"setterMethodName" : "setNluIntentConfidenceThreshold",
"setterModel" : {
"timestampFormat" : null,
@@ -58313,13 +58316,13 @@
"shouldFullyQualify" : false,
"simple" : true,
"unmarshallingType" : null,
- "varargSetterDocumentation" : "/**The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "varargSetterDocumentation" : "/**The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "Double",
"variableName" : "nluIntentConfidenceThreshold",
"variableType" : "Double",
- "documentation" : "The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.
", + "documentation" : "The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.
", "endpointDiscoveryId" : false, "enumType" : null, - "fluentSetterDocumentation" : "/**The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.
\n@param abortStatement The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.
\n@param abortStatement The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withAbortStatement", - "getterDocumentation" : "/**The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.
\n@return The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.*/", + "getterDocumentation" : "/**The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.
\n@return The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.*/", "getterMethodName" : "getAbortStatement", "getterModel" : { "returnType" : "Statement", @@ -58436,7 +58439,7 @@ "marshallingType" : "STRUCTURED", "name" : "AbortStatement", "sensitive" : false, - "setterDocumentation" : "/**The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.
\n@param abortStatement The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.*/", + "setterDocumentation" : "/**The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.
\n@param abortStatement The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.*/", "setterMethodName" : "setAbortStatement", "setterModel" : { "timestampFormat" : null, @@ -58451,13 +58454,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.
\n@param abortStatement The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.
\n@param abortStatement The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.\n@return Returns a reference to this object so that method calls can be chained together.*/", "variable" : { "timestampFormat" : null, "variableDeclarationType" : "Statement", "variableName" : "abortStatement", "variableType" : "Statement", - "documentation" : "The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.
", + "documentation" : "The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.
", "simpleType" : "Statement", "variableSetterType" : "Statement" }, @@ -59449,12 +59452,12 @@ "c2jName" : "abortStatement", "c2jShape" : "Statement", "deprecated" : false, - "documentation" : "The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.
", + "documentation" : "The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.
", "endpointDiscoveryId" : false, "enumType" : null, - "fluentSetterDocumentation" : "/**The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.
\n@param abortStatement The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.
\n@param abortStatement The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.\n@return Returns a reference to this object so that method calls can be chained together.*/", "fluentSetterMethodName" : "withAbortStatement", - "getterDocumentation" : "/**The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.
\n@return The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.*/", + "getterDocumentation" : "/**The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.
\n@return The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.*/", "getterMethodName" : "getAbortStatement", "getterModel" : { "returnType" : "Statement", @@ -59488,7 +59491,7 @@ "marshallingType" : "STRUCTURED", "name" : "AbortStatement", "sensitive" : false, - "setterDocumentation" : "/**The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.
\n@param abortStatement The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.*/", + "setterDocumentation" : "/**The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.
\n@param abortStatement The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.*/", "setterMethodName" : "setAbortStatement", "setterModel" : { "timestampFormat" : null, @@ -59503,13 +59506,13 @@ "shouldFullyQualify" : false, "simple" : false, "unmarshallingType" : null, - "varargSetterDocumentation" : "/**The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.
\n@param abortStatement The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.
\n@param abortStatement The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.\n@return Returns a reference to this object so that method calls can be chained together.*/", "variable" : { "timestampFormat" : null, "variableDeclarationType" : "Statement", "variableName" : "abortStatement", "variableType" : "Statement", - "documentation" : "The message that Amazon Lex uses to abort a conversation. For more information, see PutBot.
", + "documentation" : "The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot.
", "simpleType" : "Statement", "variableSetterType" : "Statement" }, @@ -60009,12 +60012,12 @@ "c2jName" : "enableModelImprovements", "c2jShape" : "Boolean", "deprecated" : false, - "documentation" : "Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.
", + "documentation" : "Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the imoprovements, otherwise, false.
Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.
\n@param enableModelImprovements Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "fluentSetterDocumentation" : "/**Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the imoprovements, otherwise, false.
true indicates that the bot is using the imoprovements, otherwise, false.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"fluentSetterMethodName" : "withEnableModelImprovements",
- "getterDocumentation" : "/**Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.
\n@return Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.*/", + "getterDocumentation" : "/**Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the imoprovements, otherwise, false.
true indicates that the bot is using the imoprovements, otherwise, false.*/",
"getterMethodName" : "getEnableModelImprovements",
"getterModel" : {
"returnType" : "Boolean",
@@ -60048,7 +60051,7 @@
"marshallingType" : "BOOLEAN",
"name" : "EnableModelImprovements",
"sensitive" : false,
- "setterDocumentation" : "/**Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.
\n@param enableModelImprovements Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.*/", + "setterDocumentation" : "/**Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the imoprovements, otherwise, false.
true indicates that the bot is using the imoprovements, otherwise, false.*/",
"setterMethodName" : "setEnableModelImprovements",
"setterModel" : {
"timestampFormat" : null,
@@ -60063,13 +60066,13 @@
"shouldFullyQualify" : false,
"simple" : true,
"unmarshallingType" : null,
- "varargSetterDocumentation" : "/**Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.
\n@param enableModelImprovements Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.\n@return Returns a reference to this object so that method calls can be chained together.*/", + "varargSetterDocumentation" : "/**Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the imoprovements, otherwise, false.
true indicates that the bot is using the imoprovements, otherwise, false.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "Boolean",
"variableName" : "enableModelImprovements",
"variableType" : "Boolean",
- "documentation" : "Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false.
", + "documentation" : "Indicates whether the bot uses accuracy improvements. true indicates that the bot is using the imoprovements, otherwise, false.
The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "fluentSetterDocumentation" : "/**The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"fluentSetterMethodName" : "withNluIntentConfidenceThreshold",
- "getterDocumentation" : "/**The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.*/",
+ "getterDocumentation" : "/**The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.*/",
"getterMethodName" : "getNluIntentConfidenceThreshold",
"getterModel" : {
"returnType" : "Double",
@@ -60622,7 +60625,7 @@
"marshallingType" : "DOUBLE",
"name" : "NluIntentConfidenceThreshold",
"sensitive" : false,
- "setterDocumentation" : "/**The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.*/",
+ "setterDocumentation" : "/**The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.*/",
"setterMethodName" : "setNluIntentConfidenceThreshold",
"setterModel" : {
"timestampFormat" : null,
@@ -60637,13 +60640,13 @@
"shouldFullyQualify" : false,
"simple" : true,
"unmarshallingType" : null,
- "varargSetterDocumentation" : "/**The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "varargSetterDocumentation" : "/**The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "Double",
"variableName" : "nluIntentConfidenceThreshold",
"variableType" : "Double",
- "documentation" : "The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.
The score that determines where Amazon Lex inserts the AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.
A list of EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.
A list of EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.
A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.
A list of EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.
EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "fluentSetterDocumentation" : "/**
A list of EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.
A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.
EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"fluentSetterMethodName" : "withEnumerationValues",
- "getterDocumentation" : "/**
A list of EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.
EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.*/",
+ "getterDocumentation" : "/**
A list of EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.
A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.
EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The A list of When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.*/",
"getterMethodName" : "getEnumerationValues",
"getterModel" : {
"returnType" : "java.util.ListEnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. valueSelectionStrategy field indicates the option to use. EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.*/",
+ "setterDocumentation" : "/**
A list of EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.
A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.
EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.*/",
"setterMethodName" : "setEnumerationValues",
"setterModel" : {
"timestampFormat" : null,
@@ -66418,13 +66421,13 @@
"shouldFullyQualify" : false,
"simple" : false,
"unmarshallingType" : null,
- "varargSetterDocumentation" : "/**
A list of EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.
NOTE: This method appends the values to the existing list (if any). Use {@link #setEnumerationValues(java.util.Collection)} or {@link #withEnumerationValues(java.util.Collection)} if you want to override the existing values.
\n@param enumerationValues A list ofEnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "varargSetterDocumentation" : "/**
A list of EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.
A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.
NOTE: This method appends the values to the existing list (if any). Use {@link #setEnumerationValues(java.util.Collection)} or {@link #withEnumerationValues(java.util.Collection)} if you want to override the existing values.
\n@param enumerationValues A list ofEnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The A list of When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The A list of A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values. When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The A list of When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The A list of A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values. When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The A list of When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "java.util.ListEnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. valueSelectionStrategy field indicates the option to use. EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. valueSelectionStrategy field indicates the option to use. EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. valueSelectionStrategy field indicates the option to use. EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. valueSelectionStrategy field indicates the option to use. EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. valueSelectionStrategy field indicates the option to use. EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "fluentSetterDocumentation" : "/**
A list of EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.
A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.
EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"fluentSetterMethodName" : "withEnumerationValues",
- "getterDocumentation" : "/**
A list of EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.
EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.*/",
+ "getterDocumentation" : "/**
A list of EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.
A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.
EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The A list of When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.*/",
"getterMethodName" : "getEnumerationValues",
"getterModel" : {
"returnType" : "java.util.ListEnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. valueSelectionStrategy field indicates the option to use. EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.*/",
+ "setterDocumentation" : "/**
A list of EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.
A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.
EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.*/",
"setterMethodName" : "setEnumerationValues",
"setterModel" : {
"timestampFormat" : null,
@@ -67212,13 +67215,13 @@
"shouldFullyQualify" : false,
"simple" : false,
"unmarshallingType" : null,
- "varargSetterDocumentation" : "/**
A list of EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.
NOTE: This method appends the values to the existing list (if any). Use {@link #setEnumerationValues(java.util.Collection)} or {@link #withEnumerationValues(java.util.Collection)} if you want to override the existing values.
\n@param enumerationValues A list ofEnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.\n@return Returns a reference to this object so that method calls can be chained together.*/",
+ "varargSetterDocumentation" : "/**
A list of EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.
A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The valueSelectionStrategy field indicates the option to use.
NOTE: This method appends the values to the existing list (if any). Use {@link #setEnumerationValues(java.util.Collection)} or {@link #withEnumerationValues(java.util.Collection)} if you want to override the existing values.
\n@param enumerationValues A list ofEnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The A list of When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The A list of A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values. When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the Set to When you set the You can only set the The Regions where you can set the US East (N. Virginia) (us-east-1) US West (Oregon) (us-west-2) Asia Pacific (Sydney) (ap-southeast-2) EU (Ireland) (eu-west-1) In other Regions, the Asia Pacific (Singapore) (ap-southeast-1) Asia Pacific (Tokyo) (ap-northeast-1) EU (Frankfurt) (eu-central-1) EU (London) (eu-west-2) Set to When you set the You can only set the The Regions where you can set the US East (N. Virginia) (us-east-1) US West (Oregon) (us-west-2) Asia Pacific (Sydney) (ap-southeast-2) EU (Ireland) (eu-west-1) In other Regions, the Asia Pacific (Singapore) (ap-southeast-1) Asia Pacific (Tokyo) (ap-northeast-1) EU (Frankfurt) (eu-central-1) EU (London) (eu-west-2) Determines the threshold where Amazon Lex will insert the You must set the For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent IntentA IntentB IntentC Determines the threshold where Amazon Lex will insert the You must set the US East (N. Virginia) (us-east-1) US West (Oregon) (us-west-2) Asia Pacific (Sydney) (ap-southeast-2) EU (Ireland) (eu-west-1) In other Regions, the For example, suppose a bot is configured with the confidence threshold of 0.80 and the AMAZON.FallbackIntent IntentA IntentB IntentC When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times. For example, in a pizza ordering application, If you have defined a fallback intent the abort statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent. When Amazon Lex can't understand the user's input in context, it tries to elicit the information a few times. After that, Amazon Lex sends the message defined in For example, in a pizza ordering bot, Amazon Lex might ask a user \"What type of crust would you like?\" If the user's response is not one of the expected responses (for example, \"thin crust, \"deep dish,\" etc.), Amazon Lex tries to elicit a correct response a few more times. For example, in a pizza ordering application, If you have defined a fallback intent the cancel statement will not be sent to the user, the fallback intent is used instead. For more information, see AMAZON.FallbackIntent. Indicates whether the bot uses the new natural language understanding (NLU) model or the original NLU. True indicates that the bot is using the new model, otherwise, false. Indicates whether the bot uses accuracy improvements. The score that determines where Amazon Lex inserts the The score that determines where Amazon Lex inserts the The message that Amazon Lex uses to abort a conversation. For more information, see PutBot. The message that Amazon Lex uses to cancel a conversation. For more information, see PutBot. A list of When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The A list of A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values. When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The A list of the tags that you want to attach to this resource. A list of the tags that you want to attach to this resource. A list of the tags that you want to attach to this resource. A list of the tags that you want to attach to this resource. A list of the tags that you want to attach to this resource. NOTE: This method appends the values to the existing list (if any). Use {@link #setTags(java.util.Collection)} or {@link #withTags(java.util.Collection)} if you want to override the existing values. A list of the tags that you want to attach to this resource. A list of the tags that you want to attach to this resource. A list of the tags that you want to attach to this resource. A list of the tags that you want to attach to this resource. A list of the tags that you want to attach to this resource. A list of the tags that you want to attach to this resource. NOTE: This method appends the values to the existing list (if any). Use {@link #setTags(java.util.Collection)} or {@link #withTags(java.util.Collection)} if you want to override the existing values. A list of the tags that you want to attach to this resource. The Amazon Resource Name (ARN) for the customization that you created for this AWS account. The Amazon Resource Name (ARN) for the customization that you created for this AWS account. The Amazon Resource Name (ARN) for the customization that you created for this AWS account. The Amazon Resource Name (ARN) for the customization that you created for this AWS account. The Amazon Resource Name (ARN) for the customization that you created for this AWS account. The Amazon Resource Name (ARN) for the customization that you created for this AWS account. The Amazon Resource Name (ARN) for the customization that you created for this AWS account. The Amazon Resource Name (ARN) for the customization that you created for this AWS account. The Amazon Resource Name (ARN) for the customization that you created for this AWS account. The Amazon Resource Name (ARN) for the customization that you created for this AWS account. The Amazon Resource Name (ARN) for the customization that you created for this AWS account. The Amazon Resource Name (ARN) for the customization that you created for this AWS account. The Amazon Resource Name (ARN) of the customization that's associated with this AWS account. The Amazon Resource Name (ARN) of the customization that's associated with this AWS account. The Amazon Resource Name (ARN) of the customization that's associated with this AWS account. The Amazon Resource Name (ARN) of the customization that's associated with this AWS account. The Amazon Resource Name (ARN) of the customization that's associated with this AWS account. The Amazon Resource Name (ARN) of the customization that's associated with this AWS account. The Amazon Resource Name (ARN) of the customization that's associated with this AWS account. The Amazon Resource Name (ARN) of the customization that's associated with this AWS account. The Amazon Resource Name (ARN) of the customization that's associated with this AWS account. The Amazon Resource Name (ARN) of the customization that's associated with this AWS account. The Amazon Resource Name (ARN) of the customization that's associated with this AWS account. The Amazon Resource Name (ARN) of the customization that's associated with this AWS account. The Amazon Resource Name (ARN) for the updated customization for this AWS account. The Amazon Resource Name (ARN) for the updated customization for this AWS account. The Amazon Resource Name (ARN) for the updated customization for this AWS account. The Amazon Resource Name (ARN) for the updated customization for this AWS account. The Amazon Resource Name (ARN) for the updated customization for this AWS account. The Amazon Resource Name (ARN) for the updated customization for this AWS account. The Amazon Resource Name (ARN) for the updated customization for this AWS account. The Amazon Resource Name (ARN) for the updated customization for this AWS account. The Amazon Resource Name (ARN) for the updated customization for this AWS account. The Amazon Resource Name (ARN) for the updated customization for this AWS account. The Amazon Resource Name (ARN) for the updated customization for this AWS account. The Amazon Resource Name (ARN) for the updated customization for this AWS account. The QuickSight customizations you're adding in the current AWS Region. You can add these to an AWS account and a QuickSight namespace. For example, you could add a default theme by setting A list of the tags that you want to attach to this resource. The Amazon Resource Name (ARN) for the customization that you created for this AWS account. The ID for the AWS account that you want to customize QuickSight for. The Amazon Resource Name (ARN) of the customization that's associated with this AWS account. The ID for the AWS account that you're describing. The Amazon Resource Name (ARN) for the updated customization for this AWS account. The ID for the AWS account that you want to update QuickSight customizations for.valueSelectionStrategy field indicates the option to use.\n@return Returns a reference to this object so that method calls can be chained together.*/",
"variable" : {
"timestampFormat" : null,
"variableDeclarationType" : "java.util.ListEnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. valueSelectionStrategy field indicates the option to use. EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. valueSelectionStrategy field indicates the option to use. true indicates that the bot is using the imoprovements, otherwise, false.true indicates that the bot is using the imoprovements, otherwise, false.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.true to enable the use of a new natural language understanding (NLU) model. Using the new NLU may improve the performance of your bot. enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot will use the new NLU. If you set the parameter to false, your bot will continue to use the original NLU. If you set the parameter to false after setting it to true, your bot will return to the original NLU.enableModelImprovements parameter to true are:
enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
"
+ "documentation":"true to enable access to natural language understanding improvements. enableModelImprovements parameter to true you can use the nluIntentConfidenceThreshold parameter to configure confidence scores. For more information, see Confidence Scores.enableModelImprovements parameter in certain Regions. If you set the parameter to true, your bot has access to accuracy improvements.enableModelImprovements parameter to true are:
enableModelImprovements parameter is set to true by default. In these Regions setting the parameter to false throws a ValidationException exception.
"
},
"nluIntentConfidenceThreshold":{
"shape":"ConfidenceThreshold",
- "documentation":"AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.enableModelImprovements parameter to true to use confidence scores.AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
"
+ "documentation":"AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.enableModelImprovements parameter to true to use confidence scores.
enableModelImprovements parameter is set to true by default.AMAZON.FallbackIntent. Amazon Lex returns three alternative intents with the following confidence scores: IntentA (0.70), IntentB (0.60), IntentC (0.50). The response from the PostText operation would be:
"
},
"clarificationPrompt":{
"shape":"Prompt",
@@ -2971,7 +2972,7 @@
},
"abortStatement":{
"shape":"Statement",
- "documentation":"abortStatement to the user, and then aborts the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type. OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.abortStatement to the user, and then cancels the conversation. To set the number of retries, use the valueElicitationPrompt field for the slot type. OrderPizza might be one of the intents. This intent might require the CrustType slot. You specify the valueElicitationPrompt field when you create the CrustType slot.true indicates that the bot is using the imoprovements, otherwise, false.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent and AMAZON.KendraSearchIntent are only inserted if they are configured for the bot.AMAZON.FallbackIntent, AMAZON.KendraSearchIntent, or both when returning alternative intents in a PostContent or PostText response. AMAZON.FallbackIntent is inserted if the confidence score for all intents is below this value. AMAZON.KendraSearchIntent is only inserted if it is configured for the bot.EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. valueSelectionStrategy field indicates the option to use. EnumerationValue objects that defines the values that the slot type can take. Each value can have a list of synonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot. valueSelectionStrategy field indicates the option to use. AccountCustomization to the midnight theme: \"AccountCustomization\": { \"DefaultTheme\": \"arn:aws:quicksight::aws:theme/MIDNIGHT\" }. . Or, you could add a custom theme by specifying \"AccountCustomization\": { \"DefaultTheme\": \"arn:aws:quicksight:us-west-2:111122223333:theme/bdb844d0-0fe9-4d9d-b520-0fe602d93639\" }.
+ * A list of the tags that you want to attach to this resource. + *
+ */ + private java.util.List@@ -215,6 +221,76 @@ public CreateAccountCustomizationRequest withAccountCustomization(AccountCustomi return this; } + /** + *
+ * A list of the tags that you want to attach to this resource. + *
+ * + * @return A list of the tags that you want to attach to this resource. + */ + + public java.util.List+ * A list of the tags that you want to attach to this resource. + *
+ * + * @param tags + * A list of the tags that you want to attach to this resource. + */ + + public void setTags(java.util.Collection+ * A list of the tags that you want to attach to this resource. + *
+ *+ * NOTE: This method appends the values to the existing list (if any). Use + * {@link #setTags(java.util.Collection)} or {@link #withTags(java.util.Collection)} if you want to override the + * existing values. + *
+ * + * @param tags + * A list of the tags that you want to attach to this resource. + * @return Returns a reference to this object so that method calls can be chained together. + */ + + public CreateAccountCustomizationRequest withTags(Tag... tags) { + if (this.tags == null) { + setTags(new java.util.ArrayList+ * A list of the tags that you want to attach to this resource. + *
+ * + * @param tags + * A list of the tags that you want to attach to this resource. + * @return Returns a reference to this object so that method calls can be chained together. + */ + + public CreateAccountCustomizationRequest withTags(java.util.Collection+ * The Amazon Resource Name (ARN) for the customization that you created for this AWS account. + *
+ */ + private String arn; /** ** The ID for the AWS account that you want to customize QuickSight for. @@ -54,6 +60,46 @@ public class CreateAccountCustomizationResult extends com.amazonaws.AmazonWebSer */ private Integer status; + /** + *
+ * The Amazon Resource Name (ARN) for the customization that you created for this AWS account. + *
+ * + * @param arn + * The Amazon Resource Name (ARN) for the customization that you created for this AWS account. + */ + + public void setArn(String arn) { + this.arn = arn; + } + + /** + *+ * The Amazon Resource Name (ARN) for the customization that you created for this AWS account. + *
+ * + * @return The Amazon Resource Name (ARN) for the customization that you created for this AWS account. + */ + + public String getArn() { + return this.arn; + } + + /** + *+ * The Amazon Resource Name (ARN) for the customization that you created for this AWS account. + *
+ * + * @param arn + * The Amazon Resource Name (ARN) for the customization that you created for this AWS account. + * @return Returns a reference to this object so that method calls can be chained together. + */ + + public CreateAccountCustomizationResult withArn(String arn) { + setArn(arn); + return this; + } + /** *
* The ID for the AWS account that you want to customize QuickSight for.
@@ -266,6 +312,8 @@ public CreateAccountCustomizationResult withStatus(Integer status) {
public String toString() {
StringBuilder sb = new StringBuilder();
sb.append("{");
+ if (getArn() != null)
+ sb.append("Arn: ").append(getArn()).append(",");
if (getAwsAccountId() != null)
sb.append("AwsAccountId: ").append(getAwsAccountId()).append(",");
if (getNamespace() != null)
@@ -290,6 +338,10 @@ public boolean equals(Object obj) {
if (obj instanceof CreateAccountCustomizationResult == false)
return false;
CreateAccountCustomizationResult other = (CreateAccountCustomizationResult) obj;
+ if (other.getArn() == null ^ this.getArn() == null)
+ return false;
+ if (other.getArn() != null && other.getArn().equals(this.getArn()) == false)
+ return false;
if (other.getAwsAccountId() == null ^ this.getAwsAccountId() == null)
return false;
if (other.getAwsAccountId() != null && other.getAwsAccountId().equals(this.getAwsAccountId()) == false)
@@ -318,6 +370,7 @@ public int hashCode() {
final int prime = 31;
int hashCode = 1;
+ hashCode = prime * hashCode + ((getArn() == null) ? 0 : getArn().hashCode());
hashCode = prime * hashCode + ((getAwsAccountId() == null) ? 0 : getAwsAccountId().hashCode());
hashCode = prime * hashCode + ((getNamespace() == null) ? 0 : getNamespace().hashCode());
hashCode = prime * hashCode + ((getAccountCustomization() == null) ? 0 : getAccountCustomization().hashCode());
diff --git a/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/DescribeAccountCustomizationResult.java b/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/DescribeAccountCustomizationResult.java
index 59231a928c30..c9f5ada232cb 100644
--- a/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/DescribeAccountCustomizationResult.java
+++ b/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/DescribeAccountCustomizationResult.java
@@ -23,6 +23,12 @@
@Generated("com.amazonaws:aws-java-sdk-code-generator")
public class DescribeAccountCustomizationResult extends com.amazonaws.AmazonWebServiceResult
+ * The Amazon Resource Name (ARN) of the customization that's associated with this AWS account.
+ *
* The ID for the AWS account that you're describing.
@@ -54,6 +60,46 @@ public class DescribeAccountCustomizationResult extends com.amazonaws.AmazonWebS
*/
private Integer status;
+ /**
+ *
+ * The Amazon Resource Name (ARN) of the customization that's associated with this AWS account.
+ *
+ * The Amazon Resource Name (ARN) of the customization that's associated with this AWS account.
+ *
+ * The Amazon Resource Name (ARN) of the customization that's associated with this AWS account.
+ *
* The ID for the AWS account that you're describing.
@@ -266,6 +312,8 @@ public DescribeAccountCustomizationResult withStatus(Integer status) {
public String toString() {
StringBuilder sb = new StringBuilder();
sb.append("{");
+ if (getArn() != null)
+ sb.append("Arn: ").append(getArn()).append(",");
if (getAwsAccountId() != null)
sb.append("AwsAccountId: ").append(getAwsAccountId()).append(",");
if (getNamespace() != null)
@@ -290,6 +338,10 @@ public boolean equals(Object obj) {
if (obj instanceof DescribeAccountCustomizationResult == false)
return false;
DescribeAccountCustomizationResult other = (DescribeAccountCustomizationResult) obj;
+ if (other.getArn() == null ^ this.getArn() == null)
+ return false;
+ if (other.getArn() != null && other.getArn().equals(this.getArn()) == false)
+ return false;
if (other.getAwsAccountId() == null ^ this.getAwsAccountId() == null)
return false;
if (other.getAwsAccountId() != null && other.getAwsAccountId().equals(this.getAwsAccountId()) == false)
@@ -318,6 +370,7 @@ public int hashCode() {
final int prime = 31;
int hashCode = 1;
+ hashCode = prime * hashCode + ((getArn() == null) ? 0 : getArn().hashCode());
hashCode = prime * hashCode + ((getAwsAccountId() == null) ? 0 : getAwsAccountId().hashCode());
hashCode = prime * hashCode + ((getNamespace() == null) ? 0 : getNamespace().hashCode());
hashCode = prime * hashCode + ((getAccountCustomization() == null) ? 0 : getAccountCustomization().hashCode());
diff --git a/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/UpdateAccountCustomizationResult.java b/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/UpdateAccountCustomizationResult.java
index 53d5b75415ad..c3070ac1f207 100644
--- a/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/UpdateAccountCustomizationResult.java
+++ b/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/UpdateAccountCustomizationResult.java
@@ -23,6 +23,12 @@
@Generated("com.amazonaws:aws-java-sdk-code-generator")
public class UpdateAccountCustomizationResult extends com.amazonaws.AmazonWebServiceResult
+ * The Amazon Resource Name (ARN) for the updated customization for this AWS account.
+ *
* The ID for the AWS account that you want to update QuickSight customizations for.
@@ -54,6 +60,46 @@ public class UpdateAccountCustomizationResult extends com.amazonaws.AmazonWebSer
*/
private Integer status;
+ /**
+ *
+ * The Amazon Resource Name (ARN) for the updated customization for this AWS account.
+ *
+ * The Amazon Resource Name (ARN) for the updated customization for this AWS account.
+ *
+ * The Amazon Resource Name (ARN) for the updated customization for this AWS account.
+ *
* The ID for the AWS account that you want to update QuickSight customizations for.
@@ -266,6 +312,8 @@ public UpdateAccountCustomizationResult withStatus(Integer status) {
public String toString() {
StringBuilder sb = new StringBuilder();
sb.append("{");
+ if (getArn() != null)
+ sb.append("Arn: ").append(getArn()).append(",");
if (getAwsAccountId() != null)
sb.append("AwsAccountId: ").append(getAwsAccountId()).append(",");
if (getNamespace() != null)
@@ -290,6 +338,10 @@ public boolean equals(Object obj) {
if (obj instanceof UpdateAccountCustomizationResult == false)
return false;
UpdateAccountCustomizationResult other = (UpdateAccountCustomizationResult) obj;
+ if (other.getArn() == null ^ this.getArn() == null)
+ return false;
+ if (other.getArn() != null && other.getArn().equals(this.getArn()) == false)
+ return false;
if (other.getAwsAccountId() == null ^ this.getAwsAccountId() == null)
return false;
if (other.getAwsAccountId() != null && other.getAwsAccountId().equals(this.getAwsAccountId()) == false)
@@ -318,6 +370,7 @@ public int hashCode() {
final int prime = 31;
int hashCode = 1;
+ hashCode = prime * hashCode + ((getArn() == null) ? 0 : getArn().hashCode());
hashCode = prime * hashCode + ((getAwsAccountId() == null) ? 0 : getAwsAccountId().hashCode());
hashCode = prime * hashCode + ((getNamespace() == null) ? 0 : getNamespace().hashCode());
hashCode = prime * hashCode + ((getAccountCustomization() == null) ? 0 : getAccountCustomization().hashCode());
diff --git a/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/transform/CreateAccountCustomizationRequestMarshaller.java b/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/transform/CreateAccountCustomizationRequestMarshaller.java
index 6187ba39028c..2b420c60b1d6 100644
--- a/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/transform/CreateAccountCustomizationRequestMarshaller.java
+++ b/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/transform/CreateAccountCustomizationRequestMarshaller.java
@@ -12,6 +12,7 @@
*/
package com.amazonaws.services.quicksight.model.transform;
+import java.util.List;
import javax.annotation.Generated;
import com.amazonaws.SdkClientException;
@@ -33,6 +34,8 @@ public class CreateAccountCustomizationRequestMarshaller {
.marshallLocation(MarshallLocation.QUERY_PARAM).marshallLocationName("namespace").build();
private static final MarshallingInfo TAGS_BINDING = MarshallingInfo.builder(MarshallingType.LIST).marshallLocation(MarshallLocation.PAYLOAD)
+ .marshallLocationName("Tags").build();
private static final CreateAccountCustomizationRequestMarshaller instance = new CreateAccountCustomizationRequestMarshaller();
@@ -53,6 +56,7 @@ public void marshall(CreateAccountCustomizationRequest createAccountCustomizatio
protocolMarshaller.marshall(createAccountCustomizationRequest.getAwsAccountId(), AWSACCOUNTID_BINDING);
protocolMarshaller.marshall(createAccountCustomizationRequest.getNamespace(), NAMESPACE_BINDING);
protocolMarshaller.marshall(createAccountCustomizationRequest.getAccountCustomization(), ACCOUNTCUSTOMIZATION_BINDING);
+ protocolMarshaller.marshall(createAccountCustomizationRequest.getTags(), TAGS_BINDING);
} catch (Exception e) {
throw new SdkClientException("Unable to marshall request to JSON: " + e.getMessage(), e);
}
diff --git a/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/transform/CreateAccountCustomizationResultJsonUnmarshaller.java b/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/transform/CreateAccountCustomizationResultJsonUnmarshaller.java
index 8c96516afbf6..f93d1422d779 100644
--- a/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/transform/CreateAccountCustomizationResultJsonUnmarshaller.java
+++ b/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/transform/CreateAccountCustomizationResultJsonUnmarshaller.java
@@ -50,6 +50,10 @@ public CreateAccountCustomizationResult unmarshall(JsonUnmarshallerContext conte
break;
if (token == FIELD_NAME || token == START_OBJECT) {
+ if (context.testExpression("Arn", targetDepth)) {
+ context.nextToken();
+ createAccountCustomizationResult.setArn(context.getUnmarshaller(String.class).unmarshall(context));
+ }
if (context.testExpression("AwsAccountId", targetDepth)) {
context.nextToken();
createAccountCustomizationResult.setAwsAccountId(context.getUnmarshaller(String.class).unmarshall(context));
diff --git a/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/transform/DescribeAccountCustomizationResultJsonUnmarshaller.java b/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/transform/DescribeAccountCustomizationResultJsonUnmarshaller.java
index 7bf3897029a4..f009653ea8ad 100644
--- a/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/transform/DescribeAccountCustomizationResultJsonUnmarshaller.java
+++ b/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/transform/DescribeAccountCustomizationResultJsonUnmarshaller.java
@@ -50,6 +50,10 @@ public DescribeAccountCustomizationResult unmarshall(JsonUnmarshallerContext con
break;
if (token == FIELD_NAME || token == START_OBJECT) {
+ if (context.testExpression("Arn", targetDepth)) {
+ context.nextToken();
+ describeAccountCustomizationResult.setArn(context.getUnmarshaller(String.class).unmarshall(context));
+ }
if (context.testExpression("AwsAccountId", targetDepth)) {
context.nextToken();
describeAccountCustomizationResult.setAwsAccountId(context.getUnmarshaller(String.class).unmarshall(context));
diff --git a/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/transform/UpdateAccountCustomizationResultJsonUnmarshaller.java b/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/transform/UpdateAccountCustomizationResultJsonUnmarshaller.java
index 40f4d4c295cb..5e08f1d35a55 100644
--- a/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/transform/UpdateAccountCustomizationResultJsonUnmarshaller.java
+++ b/aws-java-sdk-quicksight/src/main/java/com/amazonaws/services/quicksight/model/transform/UpdateAccountCustomizationResultJsonUnmarshaller.java
@@ -50,6 +50,10 @@ public UpdateAccountCustomizationResult unmarshall(JsonUnmarshallerContext conte
break;
if (token == FIELD_NAME || token == START_OBJECT) {
+ if (context.testExpression("Arn", targetDepth)) {
+ context.nextToken();
+ updateAccountCustomizationResult.setArn(context.getUnmarshaller(String.class).unmarshall(context));
+ }
if (context.testExpression("AwsAccountId", targetDepth)) {
context.nextToken();
updateAccountCustomizationResult.setAwsAccountId(context.getUnmarshaller(String.class).unmarshall(context));
diff --git a/aws-java-sdk-ram/pom.xml b/aws-java-sdk-ram/pom.xml
index ba73367f9afe..26bd476a5b1b 100644
--- a/aws-java-sdk-ram/pom.xml
+++ b/aws-java-sdk-ram/pom.xml
@@ -5,7 +5,7 @@