aws-sdk-lex 1.1.0 → 1.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 1b40f67e3e7dc928f8bd76d2a22ccfbe6aeaf76a
-  data.tar.gz: de37a3d87e6bc40d090b4442a0d30f50e98f8040
+  metadata.gz: 50a0e82cab65f174d50dd6000044fb18d8038643
+  data.tar.gz: a45f8a25725cbd77238e3bdfacfc66b413ca1d14
 SHA512:
-  metadata.gz: 4e1a1d4781b252e88c15a06c4955b09cfa959ccfab2a90346f2f6a281b5334c686c9cf627de340afda08fb0e4b7ae3c793feb7f6ea57a7c313d4709c907e14be
-  data.tar.gz: 9beee9db72b27fe51cddbc88009b8c1560a4828bd05367aaf27d740dbcf759155985d26111954998ba13b4f0b4cfddee684f98388c35fdf04f0f78a52d28aa3d
+  metadata.gz: 29eda2c423a1e7bc1cfdc0e4dd9a426e25b746cc3740d3830f33d38e1755a2dcef9e9ea176defc50c4529276ec99bb3ca72270660ae5db1a25bcb9b4bb06f47e
+  data.tar.gz: c39d891496368bd7a2f89e140a2e42b990644e004329ea353faf08c83e5611694a818a3d4a9d119abb8f0f9709859781fac09f206ba263ad5a1b4578cd476137

data/lib/aws-sdk-lex.rb

@@ -42,6 +42,6 @@ require_relative 'aws-sdk-lex/customizations'
 # @service
 module Aws::Lex
 
-  GEM_VERSION = '1.1.0'
+  GEM_VERSION = '1.2.0'
 
 end

data/lib/aws-sdk-lex/client.rb

@@ -146,8 +146,13 @@ module Aws::Lex
     # @!group API Operations
 
     # Sends user input (text or speech) to Amazon Lex. Clients use this API
-    # to send requests to Amazon Lex at runtime. Amazon Lex interprets the
-    # user input using the machine learning model that it built for the bot.
+    # to send text and audio requests to Amazon Lex at runtime. Amazon Lex
+    # interprets the user input using the machine learning model that it
+    # built for the bot.
+    #
+    # The `PostContent` operation supports audio input at 8kHz and 16kHz.
+    # You can use 8kHz audio to achieve higher speech recognition accuracy
+    # in telephone audio applications.
     #
     # In response, Amazon Lex returns the next message to convey to the
     # user. Consider the following example messages:
@@ -210,73 +215,63 @@ module Aws::Lex
     #   Alias of the Amazon Lex bot.
     #
     # @option params [required, String] :user_id
-    #   ID of the client application user. Typically, each of your application
-    #   users should have a unique ID. The application developer decides the
-    #   user IDs. At runtime, each request must include the user ID. Note the
-    #   following considerations:
+    #   The ID of the client application user. Amazon Lex uses this to
+    #   identify a user's conversation with your bot. At runtime, each
+    #   request must contain the `userID` field.
+    #
+    #   To decide the user ID to use for your application, consider the
+    #   following factors.
+    #
+    #   * The `userID` field must not contain any personally identifiable
+    #     information of the user, for example, name, personal identification
+    #     numbers, or other end user personal information.
     #
-    #   * If you want a user to start conversation on one device and continue
-    #     the conversation on another device, you might choose a user-specific
-    #     identifier, such as the user's login, or Amazon Cognito user ID
-    #     (assuming your application is using Amazon Cognito).
+    #   * If you want a user to start a conversation on one device and
+    #     continue on another device, use a user-specific identifier.
     #
     #   * If you want the same user to be able to have two independent
-    #     conversations on two different devices, you might choose
-    #     device-specific identifier, such as device ID, or some globally
-    #     unique identifier.
+    #     conversations on two different devices, choose a device-specific
+    #     identifier.
+    #
+    #   * A user can't have two independent conversations with two different
+    #     versions of the same bot. For example, a user can't have a
+    #     conversation with the PROD and BETA versions of the same bot. If you
+    #     anticipate that a user will need to have conversation with two
+    #     different versions, for example, while testing, include the bot
+    #     alias in the user ID to separate the two conversations.
     #
     # @option params [String] :session_attributes
-    #   You pass this value in the `x-amz-lex-session-attributes` HTTP header.
-    #   The value must be map (keys and values must be strings) that is JSON
-    #   serialized and then base64 encoded.
-    #
-    #   A session represents dialog between a user and Amazon Lex. At runtime,
-    #   a client application can pass contextual information, in the request
-    #   to Amazon Lex. For example,
-    #
-    #   * You might use session attributes to track the requestID of user
-    #     requests.
-    #
-    #   * In Getting Started Exercise 1, the example bot uses the price
-    #     session attribute to maintain the price of flowers ordered (for
-    #     example, "price":25). The code hook (Lambda function) sets this
-    #     attribute based on the type of flowers ordered. For more
-    #     information, see [Review the Details of Information Flow][1].
-    #
-    #   * In the BookTrip bot exercise, the bot uses the `currentReservation`
-    #     session attribute to maintains the slot data during the in-progress
-    #     conversation to book a hotel or book a car. For more information,
-    #     see [Details of Information Flow][2].
-    #
-    #   Amazon Lex passes these session attributes to the Lambda functions
-    #   configured for the intent In the your Lambda function, you can use the
-    #   session attributes for initialization and customization (prompts).
-    #   Some examples are:
-    #
-    #   * Initialization - In a pizza ordering bot, if you pass user location
-    #     (for example, `"Location : 111 Maple Street"`), then your Lambda
-    #     function might use this information to determine the closest
-    #     pizzeria to place the order (and perhaps set the storeAddress slot
-    #     value as well).
-    #
-    #     Personalized prompts - For example, you can configure prompts to
-    #     refer to the user by name (for example, "Hey \[firstName\], what
-    #     toppings would you like?"). You can pass the user's name as a
-    #     session attribute ("firstName": "Joe") so that Amazon Lex can
-    #     substitute the placeholder to provide a personalized prompt to the
-    #     user ("Hey Joe, what toppings would you like?").
-    #
-    #   <note markdown="1"> Amazon Lex does not persist session attributes.
-    #
-    #    If you configured a code hook for the intent, Amazon Lex passes the
-    #   incoming session attributes to the Lambda function. The Lambda
-    #   function must return these session attributes if you want Amazon Lex
-    #   to return them to the client.
-    #
-    #    If there is no code hook configured for the intent Amazon Lex simply
-    #   returns the session attributes to the client application.
-    #
-    #    </note>
+    #   You pass this value as the `x-amz-lex-session-attributes` HTTP header.
+    #
+    #   Application-specific information passed between Amazon Lex and a
+    #   client application. The value must be a JSON serialized and base64
+    #   encoded map with string keys and values. The total size of the
+    #   `sessionAttributes` and `requestAttributes` headers is limited to 12
+    #   KB.
+    #
+    #   For more information, see [Setting Session Attributes][1].
+    #
+    #   **SDK automatically handles json encoding and base64 encoding for you
+    #   when the required value (Hash, Array, etc.) is provided according to
+    #   the description.**
+    #
+    #
+    #
+    #   [1]: http://docs.aws.amazon.com/lex/latest/dg/context-mgmt.html#context-mgmt-session-attribs
+    #
+    # @option params [String] :request_attributes
+    #   You pass this value as the `x-amz-lex-request-attributes` HTTP header.
+    #
+    #   Request-specific information passed between Amazon Lex and a client
+    #   application. The value must be a JSON serialized and base64 encoded
+    #   map with string keys and values. The total size of the
+    #   `requestAttributes` and `sessionAttributes` headers is limited to 12
+    #   KB.
+    #
+    #   The namespace `x-amz-lex:` is reserved for special attributes. Don't
+    #   create any request attributes with the prefix `x-amz-lex:`.
+    #
+    #   For more information, see [Setting Request Attributes][1].
     #
     #   **SDK automatically handles json encoding and base64 encoding for you
     #   when the required value (Hash, Array, etc.) is provided according to
@@ -284,25 +279,27 @@ module Aws::Lex
     #
     #
     #
-    #   [1]: http://docs.aws.amazon.com/lex/latest/dg/gs-bp-details-after-lambda.html
-    #   [2]: http://docs.aws.amazon.com/lex/latest/dg/book-trip-detail-flow.html
+    #   [1]: http://docs.aws.amazon.com/lex/latest/dg/context-mgmt.html#context-mgmt-request-attribs
     #
     # @option params [required, String] :content_type
-    #   You pass this values as the `Content-Type` HTTP header.
+    #   You pass this value as the `Content-Type` HTTP header.
     #
     #   Indicates the audio format or text. The header value must start with
     #   one of the following prefixes:
     #
-    #   * PCM format
+    #   * PCM format, audio data must be in little-endian byte order.
     #
     #     * audio/l16; rate=16000; channels=1
     #
     #     * audio/x-l16; sample-rate=16000; channel-count=1
     #
+    #     * audio/lpcm; sample-rate=8000; sample-size-bits=16;
+    #       channel-count=1; is-big-endian=false
+    #
     #   * Opus format
     #
-    #     * audio/x-cbr-opus-with-preamble; preamble-size=0; bit-rate=1;
-    #       frame-size-milliseconds=1.1
+    #     * audio/x-cbr-opus-with-preamble; preamble-size=0; bit-rate=256000;
+    #       frame-size-milliseconds=4
     #
     #     ^
     #
@@ -343,6 +340,11 @@ module Aws::Lex
     #   User input in PCM or Opus audio format or text format as described in
     #   the `Content-Type` HTTP header.
     #
+    #   You can stream audio data to Amazon Lex or you can create a local
+    #   buffer that captures all of the audio data before sending. In general,
+    #   you get better performance if you stream audio data rather than
+    #   buffering the data locally.
+    #
     # @return [Types::PostContentResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
     #   * {Types::PostContentResponse#content_type #content_type} => String
@@ -361,7 +363,8 @@ module Aws::Lex
     #     bot_name: "BotName", # required
     #     bot_alias: "BotAlias", # required
     #     user_id: "UserId", # required
-    #     session_attributes: "String",
+    #     session_attributes: "AttributesString",
+    #     request_attributes: "AttributesString",
     #     content_type: "HttpContentType", # required
     #     accept: "Accept",
     #     input_stream: "data", # required
@@ -453,75 +456,53 @@ module Aws::Lex
     #   The alias of the Amazon Lex bot.
     #
     # @option params [required, String] :user_id
-    #   The ID of the client application user. The application developer
-    #   decides the user IDs. At runtime, each request must include the user
-    #   ID. Typically, each of your application users should have a unique ID.
-    #   Note the following considerations:
+    #   The ID of the client application user. Amazon Lex uses this to
+    #   identify a user's conversation with your bot. At runtime, each
+    #   request must contain the `userID` field.
     #
-    #   * If you want a user to start a conversation on one device and
-    #     continue the conversation on another device, you might choose a
-    #     user-specific identifier, such as a login or Amazon Cognito user ID
-    #     (assuming your application is using Amazon Cognito).
+    #   To decide the user ID to use for your application, consider the
+    #   following factors.
     #
-    #   * If you want the same user to be able to have two independent
-    #     conversations on two different devices, you might choose a
-    #     device-specific identifier, such as device ID, or some globally
-    #     unique identifier.
+    #   * The `userID` field must not contain any personally identifiable
+    #     information of the user, for example, name, personal identification
+    #     numbers, or other end user personal information.
     #
-    # @option params [Hash<String,String>] :session_attributes
-    #   By using session attributes, a client application can pass contextual
-    #   information in the request to Amazon Lex For example,
-    #
-    #   * In Getting Started Exercise 1, the example bot uses the `price`
-    #     session attribute to maintain the price of the flowers ordered (for
-    #     example, "Price":25). The code hook (the Lambda function) sets
-    #     this attribute based on the type of flowers ordered. For more
-    #     information, see [Review the Details of Information Flow][1].
+    #   * If you want a user to start a conversation on one device and
+    #     continue on another device, use a user-specific identifier.
     #
-    #   * In the BookTrip bot exercise, the bot uses the `currentReservation`
-    #     session attribute to maintain slot data during the in-progress
-    #     conversation to book a hotel or book a car. For more information,
-    #     see [Details of Information Flow][2].
+    #   * If you want the same user to be able to have two independent
+    #     conversations on two different devices, choose a device-specific
+    #     identifier.
     #
-    #   * You might use the session attributes (key, value pairs) to track the
-    #     requestID of user requests.
+    #   * A user can't have two independent conversations with two different
+    #     versions of the same bot. For example, a user can't have a
+    #     conversation with the PROD and BETA versions of the same bot. If you
+    #     anticipate that a user will need to have conversation with two
+    #     different versions, for example, while testing, include the bot
+    #     alias in the user ID to separate the two conversations.
     #
-    #   Amazon Lex simply passes these session attributes to the Lambda
-    #   functions configured for the intent.
+    # @option params [Hash<String,String>] :session_attributes
+    #   Application-specific information passed between Amazon Lex and a
+    #   client application.
     #
-    #   In your Lambda function, you can also use the session attributes for
-    #   initialization and customization (prompts and response cards). Some
-    #   examples are:
+    #   For more information, see [Setting Session Attributes][1].
     #
-    #   * Initialization - In a pizza ordering bot, if you can pass the user
-    #     location as a session attribute (for example, `"Location" : "111
-    #     Maple street"`), then your Lambda function might use this
-    #     information to determine the closest pizzeria to place the order
-    #     (perhaps to set the storeAddress slot value).
     #
-    #   * Personalize prompts - For example, you can configure prompts to
-    #     refer to the user name. (For example, "Hey \[FirstName\], what
-    #     toppings would you like?"). You can pass the user name as a session
-    #     attribute (`"FirstName" : "Joe"`) so that Amazon Lex can substitute
-    #     the placeholder to provide a personalize prompt to the user ("Hey
-    #     Joe, what toppings would you like?").
     #
-    #   <note markdown="1"> Amazon Lex does not persist session attributes.
+    #   [1]: http://docs.aws.amazon.com/lex/latest/dg/context-mgmt.html#context-mgmt-session-attribs
     #
-    #    If you configure a code hook for the intent, Amazon Lex passes the
-    #   incoming session attributes to the Lambda function. If you want Amazon
-    #   Lex to return these session attributes back to the client, the Lambda
-    #   function must return them.
+    # @option params [Hash<String,String>] :request_attributes
+    #   Request-specific information passed between Amazon Lex and a client
+    #   application.
     #
-    #    If there is no code hook configured for the intent, Amazon Lex simply
-    #   returns the session attributes back to the client application.
+    #   The namespace `x-amz-lex:` is reserved for special attributes. Don't
+    #   create any request attributes with the prefix `x-amz-lex:`.
     #
-    #    </note>
+    #   For more information, see [Setting Request Attributes][1].
     #
     #
     #
-    #   [1]: http://docs.aws.amazon.com/lex/latest/dg/gs-bp-details-after-lambda.html
-    #   [2]: http://docs.aws.amazon.com/lex/latest/dg/book-trip-detail-flow.html
+    #   [1]: http://docs.aws.amazon.com/lex/latest/dg/context-mgmt.html#context-mgmt-request-attribs
     #
     # @option params [required, String] :input_text
     #   The text that the user entered (Amazon Lex interprets this text).
@@ -545,6 +526,9 @@ module Aws::Lex
     #     session_attributes: {
     #       "String" => "String",
     #     },
+    #     request_attributes: {
+    #       "String" => "String",
+    #     },
     #     input_text: "Text", # required
     #   })
     #
@@ -591,7 +575,7 @@ module Aws::Lex
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-lex'
-      context[:gem_version] = '1.1.0'
+      context[:gem_version] = '1.2.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

data/lib/aws-sdk-lex/client_api.rb

@@ -12,6 +12,7 @@ module Aws::Lex
     include Seahorse::Model
 
     Accept = Shapes::StringShape.new(name: 'Accept')
+    AttributesString = Shapes::StringShape.new(name: 'AttributesString')
     BadGatewayException = Shapes::StructureShape.new(name: 'BadGatewayException')
     BadRequestException = Shapes::StructureShape.new(name: 'BadRequestException')
     BlobStream = Shapes::BlobShape.new(name: 'BlobStream')
@@ -63,7 +64,8 @@ module Aws::Lex
     PostContentRequest.add_member(:bot_name, Shapes::ShapeRef.new(shape: BotName, required: true, location: "uri", location_name: "botName"))
     PostContentRequest.add_member(:bot_alias, Shapes::ShapeRef.new(shape: BotAlias, required: true, location: "uri", location_name: "botAlias"))
     PostContentRequest.add_member(:user_id, Shapes::ShapeRef.new(shape: UserId, required: true, location: "uri", location_name: "userId"))
-    PostContentRequest.add_member(:session_attributes, Shapes::ShapeRef.new(shape: String, location: "header", location_name: "x-amz-lex-session-attributes", metadata: {"jsonvalue"=>true}))
+    PostContentRequest.add_member(:session_attributes, Shapes::ShapeRef.new(shape: AttributesString, location: "header", location_name: "x-amz-lex-session-attributes", metadata: {"jsonvalue"=>true}))
+    PostContentRequest.add_member(:request_attributes, Shapes::ShapeRef.new(shape: AttributesString, location: "header", location_name: "x-amz-lex-request-attributes", metadata: {"jsonvalue"=>true}))
     PostContentRequest.add_member(:content_type, Shapes::ShapeRef.new(shape: HttpContentType, required: true, location: "header", location_name: "Content-Type"))
     PostContentRequest.add_member(:accept, Shapes::ShapeRef.new(shape: Accept, location: "header", location_name: "Accept"))
     PostContentRequest.add_member(:input_stream, Shapes::ShapeRef.new(shape: BlobStream, required: true, location_name: "inputStream"))
@@ -88,6 +90,7 @@ module Aws::Lex
     PostTextRequest.add_member(:bot_alias, Shapes::ShapeRef.new(shape: BotAlias, required: true, location: "uri", location_name: "botAlias"))
     PostTextRequest.add_member(:user_id, Shapes::ShapeRef.new(shape: UserId, required: true, location: "uri", location_name: "userId"))
     PostTextRequest.add_member(:session_attributes, Shapes::ShapeRef.new(shape: StringMap, location_name: "sessionAttributes"))
+    PostTextRequest.add_member(:request_attributes, Shapes::ShapeRef.new(shape: StringMap, location_name: "requestAttributes"))
     PostTextRequest.add_member(:input_text, Shapes::ShapeRef.new(shape: Text, required: true, location_name: "inputText"))
     PostTextRequest.struct_class = Types::PostTextRequest
 

data/lib/aws-sdk-lex/types.rb

@@ -70,7 +70,8 @@ module Aws::Lex
     #         bot_name: "BotName", # required
     #         bot_alias: "BotAlias", # required
     #         user_id: "UserId", # required
-    #         session_attributes: "String",
+    #         session_attributes: "AttributesString",
+    #         request_attributes: "AttributesString",
     #         content_type: "HttpContentType", # required
     #         accept: "Accept",
     #         input_stream: "data", # required
@@ -85,98 +86,88 @@ module Aws::Lex
     #   @return [String]
     #
     # @!attribute [rw] user_id
-    #   ID of the client application user. Typically, each of your
-    #   application users should have a unique ID. The application developer
-    #   decides the user IDs. At runtime, each request must include the user
-    #   ID. Note the following considerations:
+    #   The ID of the client application user. Amazon Lex uses this to
+    #   identify a user's conversation with your bot. At runtime, each
+    #   request must contain the `userID` field.
     #
-    #   * If you want a user to start conversation on one device and
-    #     continue the conversation on another device, you might choose a
-    #     user-specific identifier, such as the user's login, or Amazon
-    #     Cognito user ID (assuming your application is using Amazon
-    #     Cognito).
+    #   To decide the user ID to use for your application, consider the
+    #   following factors.
+    #
+    #   * The `userID` field must not contain any personally identifiable
+    #     information of the user, for example, name, personal
+    #     identification numbers, or other end user personal information.
+    #
+    #   * If you want a user to start a conversation on one device and
+    #     continue on another device, use a user-specific identifier.
     #
     #   * If you want the same user to be able to have two independent
-    #     conversations on two different devices, you might choose
-    #     device-specific identifier, such as device ID, or some globally
-    #     unique identifier.
+    #     conversations on two different devices, choose a device-specific
+    #     identifier.
+    #
+    #   * A user can't have two independent conversations with two
+    #     different versions of the same bot. For example, a user can't
+    #     have a conversation with the PROD and BETA versions of the same
+    #     bot. If you anticipate that a user will need to have conversation
+    #     with two different versions, for example, while testing, include
+    #     the bot alias in the user ID to separate the two conversations.
     #   @return [String]
     #
     # @!attribute [rw] session_attributes
-    #   You pass this value in the `x-amz-lex-session-attributes` HTTP
-    #   header. The value must be map (keys and values must be strings) that
-    #   is JSON serialized and then base64 encoded.
+    #   You pass this value as the `x-amz-lex-session-attributes` HTTP
+    #   header.
     #
-    #   A session represents dialog between a user and Amazon Lex. At
-    #   runtime, a client application can pass contextual information, in
-    #   the request to Amazon Lex. For example,
+    #   Application-specific information passed between Amazon Lex and a
+    #   client application. The value must be a JSON serialized and base64
+    #   encoded map with string keys and values. The total size of the
+    #   `sessionAttributes` and `requestAttributes` headers is limited to 12
+    #   KB.
     #
-    #   * You might use session attributes to track the requestID of user
-    #     requests.
+    #   For more information, see [Setting Session Attributes][1].
     #
-    #   * In Getting Started Exercise 1, the example bot uses the price
-    #     session attribute to maintain the price of flowers ordered (for
-    #     example, "price":25). The code hook (Lambda function) sets this
-    #     attribute based on the type of flowers ordered. For more
-    #     information, see [Review the Details of Information Flow][1].
     #
-    #   * In the BookTrip bot exercise, the bot uses the
-    #     `currentReservation` session attribute to maintains the slot data
-    #     during the in-progress conversation to book a hotel or book a car.
-    #     For more information, see [Details of Information Flow][2].
     #
-    #   Amazon Lex passes these session attributes to the Lambda functions
-    #   configured for the intent In the your Lambda function, you can use
-    #   the session attributes for initialization and customization
-    #   (prompts). Some examples are:
-    #
-    #   * Initialization - In a pizza ordering bot, if you pass user
-    #     location (for example, `"Location : 111 Maple Street"`), then your
-    #     Lambda function might use this information to determine the
-    #     closest pizzeria to place the order (and perhaps set the
-    #     storeAddress slot value as well).
-    #
-    #     Personalized prompts - For example, you can configure prompts to
-    #     refer to the user by name (for example, "Hey \[firstName\], what
-    #     toppings would you like?"). You can pass the user's name as a
-    #     session attribute ("firstName": "Joe") so that Amazon Lex can
-    #     substitute the placeholder to provide a personalized prompt to the
-    #     user ("Hey Joe, what toppings would you like?").
+    #   [1]: http://docs.aws.amazon.com/lex/latest/dg/context-mgmt.html#context-mgmt-session-attribs
+    #   @return [String]
     #
-    #   <note markdown="1"> Amazon Lex does not persist session attributes.
+    # @!attribute [rw] request_attributes
+    #   You pass this value as the `x-amz-lex-request-attributes` HTTP
+    #   header.
     #
-    #    If you configured a code hook for the intent, Amazon Lex passes the
-    #   incoming session attributes to the Lambda function. The Lambda
-    #   function must return these session attributes if you want Amazon Lex
-    #   to return them to the client.
+    #   Request-specific information passed between Amazon Lex and a client
+    #   application. The value must be a JSON serialized and base64 encoded
+    #   map with string keys and values. The total size of the
+    #   `requestAttributes` and `sessionAttributes` headers is limited to 12
+    #   KB.
     #
-    #    If there is no code hook configured for the intent Amazon Lex simply
-    #   returns the session attributes to the client application.
+    #   The namespace `x-amz-lex:` is reserved for special attributes.
+    #   Don't create any request attributes with the prefix `x-amz-lex:`.
     #
-    #    </note>
+    #   For more information, see [Setting Request Attributes][1].
     #
     #
     #
-    #   [1]: http://docs.aws.amazon.com/lex/latest/dg/gs-bp-details-after-lambda.html
-    #   [2]: http://docs.aws.amazon.com/lex/latest/dg/book-trip-detail-flow.html
+    #   [1]: http://docs.aws.amazon.com/lex/latest/dg/context-mgmt.html#context-mgmt-request-attribs
     #   @return [String]
     #
     # @!attribute [rw] content_type
-    #   You pass this values as the `Content-Type` HTTP header.
+    #   You pass this value as the `Content-Type` HTTP header.
     #
     #   Indicates the audio format or text. The header value must start with
     #   one of the following prefixes:
     #
-    #   * PCM format
+    #   * PCM format, audio data must be in little-endian byte order.
     #
     #     * audio/l16; rate=16000; channels=1
     #
     #     * audio/x-l16; sample-rate=16000; channel-count=1
     #
+    #     * audio/lpcm; sample-rate=8000; sample-size-bits=16;
+    #       channel-count=1; is-big-endian=false
+    #
     #   * Opus format
     #
-    #     * audio/x-cbr-opus-with-preamble; preamble-size=0; bit-rate=1;
-    #       frame-size-milliseconds=1.1
+    #     * audio/x-cbr-opus-with-preamble; preamble-size=0;
+    #       bit-rate=256000; frame-size-milliseconds=4
     #
     #     ^
     #
@@ -218,6 +209,11 @@ module Aws::Lex
     # @!attribute [rw] input_stream
     #   User input in PCM or Opus audio format or text format as described
     #   in the `Content-Type` HTTP header.
+    #
+    #   You can stream audio data to Amazon Lex or you can create a local
+    #   buffer that captures all of the audio data before sending. In
+    #   general, you get better performance if you stream audio data rather
+    #   than buffering the data locally.
     #   @return [IO]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/runtime.lex-2016-11-28/PostContentRequest AWS API Documentation
@@ -227,6 +223,7 @@ module Aws::Lex
       :bot_alias,
       :user_id,
       :session_attributes,
+      :request_attributes,
       :content_type,
       :accept,
       :input_stream)
@@ -245,6 +242,17 @@ module Aws::Lex
     # @!attribute [rw] slots
     #   Map of zero or more intent slots (name/value pairs) Amazon Lex
     #   detected from the user input during the conversation.
+    #
+    #   Amazon Lex creates a resolution list containing likely values for a
+    #   slot. The value that it returns is determined by the
+    #   `valueSelectionStrategy` selected when the slot type was created or
+    #   updated. If `valueSelectionStrategy` is set to `ORIGINAL_VALUE`, the
+    #   value provided by the user is returned, if the user value is similar
+    #   to the slot values. If `valueSelectionStrategy` is set to
+    #   `TOP_RESOLUTION` Amazon Lex returns the first value in the
+    #   resolution list or, if there is no resolution list, null. If you
+    #   don't specify a `valueSelectionStrategy`, the default is
+    #   `ORIGINAL_VALUE`.
     #   @return [String]
     #
     # @!attribute [rw] session_attributes
@@ -273,14 +281,14 @@ module Aws::Lex
     #   returns one of the following values as `dialogState`. The client can
     #   optionally use this information to customize the user interface.
     #
-    #   * `ElicitIntent` – Amazon Lex wants to elicit the user's intent.
+    #   * `ElicitIntent` - Amazon Lex wants to elicit the user's intent.
     #     Consider the following examples:
     #
     #     For example, a user might utter an intent ("I want to order a
     #     pizza"). If Amazon Lex cannot infer the user intent from this
     #     utterance, it will return this dialog state.
     #
-    #   * `ConfirmIntent` – Amazon Lex is expecting a "yes" or "no"
+    #   * `ConfirmIntent` - Amazon Lex is expecting a "yes" or "no"
     #     response.
     #
     #     For example, Amazon Lex wants user confirmation before fulfilling
@@ -291,7 +299,7 @@ module Aws::Lex
     #     examples, update the crust type slot or change the intent from
     #     OrderPizza to OrderDrink).
     #
-    #   * `ElicitSlot` – Amazon Lex is expecting the value of a slot for the
+    #   * `ElicitSlot` - Amazon Lex is expecting the value of a slot for the
     #     current intent.
     #
     #     For example, suppose that in the response Amazon Lex sends this
@@ -301,13 +309,13 @@ module Aws::Lex
     #     thick crust pizza"). Amazon Lex can process such additional
     #     information appropriately.
     #
-    #   * `Fulfilled` – Conveys that the Lambda function has successfully
+    #   * `Fulfilled` - Conveys that the Lambda function has successfully
     #     fulfilled the intent.
     #
-    #   * `ReadyForFulfillment` – Conveys that the client has to fullfill
-    #     the request.
+    #   * `ReadyForFulfillment` - Conveys that the client has to fulfill the
+    #     request.
     #
-    #   * `Failed` – Conveys that the conversation with the user failed.
+    #   * `Failed` - Conveys that the conversation with the user failed.
     #
     #     This can happen for various reasons, including that the user does
     #     not provide an appropriate response to prompts from the service
@@ -322,7 +330,13 @@ module Aws::Lex
     #   @return [String]
     #
     # @!attribute [rw] input_transcript
-    #   Transcript of the voice input to the operation.
+    #   The text used to process the request.
+    #
+    #   If the input was an audio stream, the `inputTranscript` field
+    #   contains the text extracted from the audio stream. This is the text
+    #   that is actually processed to recognize intents and slot values. You
+    #   can use this information to determine if Amazon Lex is correctly
+    #   processing the audio that you send.
     #   @return [String]
     #
     # @!attribute [rw] audio_stream
@@ -361,6 +375,9 @@ module Aws::Lex
     #         session_attributes: {
     #           "String" => "String",
     #         },
+    #         request_attributes: {
+    #           "String" => "String",
+    #         },
     #         input_text: "Text", # required
     #       }
     #
@@ -373,77 +390,55 @@ module Aws::Lex
     #   @return [String]
     #
     # @!attribute [rw] user_id
-    #   The ID of the client application user. The application developer
-    #   decides the user IDs. At runtime, each request must include the user
-    #   ID. Typically, each of your application users should have a unique
-    #   ID. Note the following considerations:
+    #   The ID of the client application user. Amazon Lex uses this to
+    #   identify a user's conversation with your bot. At runtime, each
+    #   request must contain the `userID` field.
+    #
+    #   To decide the user ID to use for your application, consider the
+    #   following factors.
+    #
+    #   * The `userID` field must not contain any personally identifiable
+    #     information of the user, for example, name, personal
+    #     identification numbers, or other end user personal information.
     #
     #   * If you want a user to start a conversation on one device and
-    #     continue the conversation on another device, you might choose a
-    #     user-specific identifier, such as a login or Amazon Cognito user
-    #     ID (assuming your application is using Amazon Cognito).
+    #     continue on another device, use a user-specific identifier.
     #
     #   * If you want the same user to be able to have two independent
-    #     conversations on two different devices, you might choose a
-    #     device-specific identifier, such as device ID, or some globally
-    #     unique identifier.
+    #     conversations on two different devices, choose a device-specific
+    #     identifier.
+    #
+    #   * A user can't have two independent conversations with two
+    #     different versions of the same bot. For example, a user can't
+    #     have a conversation with the PROD and BETA versions of the same
+    #     bot. If you anticipate that a user will need to have conversation
+    #     with two different versions, for example, while testing, include
+    #     the bot alias in the user ID to separate the two conversations.
     #   @return [String]
     #
     # @!attribute [rw] session_attributes
-    #   By using session attributes, a client application can pass
-    #   contextual information in the request to Amazon Lex For example,
-    #
-    #   * In Getting Started Exercise 1, the example bot uses the `price`
-    #     session attribute to maintain the price of the flowers ordered
-    #     (for example, "Price":25). The code hook (the Lambda function)
-    #     sets this attribute based on the type of flowers ordered. For more
-    #     information, see [Review the Details of Information Flow][1].
-    #
-    #   * In the BookTrip bot exercise, the bot uses the
-    #     `currentReservation` session attribute to maintain slot data
-    #     during the in-progress conversation to book a hotel or book a car.
-    #     For more information, see [Details of Information Flow][2].
-    #
-    #   * You might use the session attributes (key, value pairs) to track
-    #     the requestID of user requests.
-    #
-    #   Amazon Lex simply passes these session attributes to the Lambda
-    #   functions configured for the intent.
-    #
-    #   In your Lambda function, you can also use the session attributes for
-    #   initialization and customization (prompts and response cards). Some
-    #   examples are:
-    #
-    #   * Initialization - In a pizza ordering bot, if you can pass the user
-    #     location as a session attribute (for example, `"Location" : "111
-    #     Maple street"`), then your Lambda function might use this
-    #     information to determine the closest pizzeria to place the order
-    #     (perhaps to set the storeAddress slot value).
-    #
-    #   * Personalize prompts - For example, you can configure prompts to
-    #     refer to the user name. (For example, "Hey \[FirstName\], what
-    #     toppings would you like?"). You can pass the user name as a
-    #     session attribute (`"FirstName" : "Joe"`) so that Amazon Lex can
-    #     substitute the placeholder to provide a personalize prompt to the
-    #     user ("Hey Joe, what toppings would you like?").
-    #
-    #   <note markdown="1"> Amazon Lex does not persist session attributes.
-    #
-    #    If you configure a code hook for the intent, Amazon Lex passes the
-    #   incoming session attributes to the Lambda function. If you want
-    #   Amazon Lex to return these session attributes back to the client,
-    #   the Lambda function must return them.
-    #
-    #    If there is no code hook configured for the intent, Amazon Lex
-    #   simply returns the session attributes back to the client
+    #   Application-specific information passed between Amazon Lex and a
+    #   client application.
+    #
+    #   For more information, see [Setting Session Attributes][1].
+    #
+    #
+    #
+    #   [1]: http://docs.aws.amazon.com/lex/latest/dg/context-mgmt.html#context-mgmt-session-attribs
+    #   @return [Hash<String,String>]
+    #
+    # @!attribute [rw] request_attributes
+    #   Request-specific information passed between Amazon Lex and a client
     #   application.
     #
-    #    </note>
+    #   The namespace `x-amz-lex:` is reserved for special attributes.
+    #   Don't create any request attributes with the prefix `x-amz-lex:`.
+    #
+    #   For more information, see [Setting Request Attributes][1].
     #
     #
     #
-    #   [1]: http://docs.aws.amazon.com/lex/latest/dg/gs-bp-details-after-lambda.html
-    #   [2]: http://docs.aws.amazon.com/lex/latest/dg/book-trip-detail-flow.html
+    #   [1]: http://docs.aws.amazon.com/lex/latest/dg/context-mgmt.html#context-mgmt-request-attribs
     #   @return [Hash<String,String>]
     #
     # @!attribute [rw] input_text
@@ -457,6 +452,7 @@ module Aws::Lex
       :bot_alias,
       :user_id,
       :session_attributes,
+      :request_attributes,
       :input_text)
       include Aws::Structure
     end
@@ -466,8 +462,19 @@ module Aws::Lex
     #   @return [String]
     #
     # @!attribute [rw] slots
-    #   The intent slots (name/value pairs) that Amazon Lex detected so far
-    #   from the user input in the conversation.
+    #   The intent slots that Amazon Lex detected from the user input in the
+    #   conversation.
+    #
+    #   Amazon Lex creates a resolution list containing likely values for a
+    #   slot. The value that it returns is determined by the
+    #   `valueSelectionStrategy` selected when the slot type was created or
+    #   updated. If `valueSelectionStrategy` is set to `ORIGINAL_VALUE`, the
+    #   value provided by the user is returned, if the user value is similar
+    #   to the slot values. If `valueSelectionStrategy` is set to
+    #   `TOP_RESOLUTION` Amazon Lex returns the first value in the
+    #   resolution list or, if there is no resolution list, null. If you
+    #   don't specify a `valueSelectionStrategy`, the default is
+    #   `ORIGINAL_VALUE`.
     #   @return [Hash<String,String>]
     #
     # @!attribute [rw] session_attributes
@@ -496,13 +503,13 @@ module Aws::Lex
     #   returns one of the following values as `dialogState`. The client can
     #   optionally use this information to customize the user interface.
     #
-    #   * `ElicitIntent` – Amazon Lex wants to elicit user intent.
+    #   * `ElicitIntent` - Amazon Lex wants to elicit user intent.
     #
     #     For example, a user might utter an intent ("I want to order a
     #     pizza"). If Amazon Lex cannot infer the user intent from this
     #     utterance, it will return this dialogState.
     #
-    #   * `ConfirmIntent` – Amazon Lex is expecting a "yes" or "no"
+    #   * `ConfirmIntent` - Amazon Lex is expecting a "yes" or "no"
     #     response.
     #
     #     For example, Amazon Lex wants user confirmation before fulfilling
@@ -515,7 +522,7 @@ module Aws::Lex
     #     crust type slot value, or change intent from OrderPizza to
     #     OrderDrink).
     #
-    #   * `ElicitSlot` – Amazon Lex is expecting a slot value for the
+    #   * `ElicitSlot` - Amazon Lex is expecting a slot value for the
     #     current intent.
     #
     #     For example, suppose that in the response Amazon Lex sends this
@@ -525,13 +532,13 @@ module Aws::Lex
     #     thick crust pizza"). Amazon Lex can process such additional
     #     information appropriately.
     #
-    #   * `Fulfilled` – Conveys that the Lambda function configured for the
+    #   * `Fulfilled` - Conveys that the Lambda function configured for the
     #     intent has successfully fulfilled the intent.
     #
-    #   * `ReadyForFulfillment` – Conveys that the client has to fulfill the
+    #   * `ReadyForFulfillment` - Conveys that the client has to fulfill the
     #     intent.
     #
-    #   * `Failed` – Conveys that the conversation with the user failed.
+    #   * `Failed` - Conveys that the conversation with the user failed.
     #
     #     This can happen for various reasons including that the user did
     #     not provide an appropriate response to prompts from the service

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-lex
 version: !ruby/object:Gem::Version
-  version: 1.1.0
+  version: 1.2.0
 platform: ruby
 authors:
 - Amazon Web Services
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-09-01 00:00:00.000000000 Z
+date: 2017-09-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-core