Class: Aws::BedrockRuntime::Client

Inherits:
Seahorse::Client::Base
  • Object
show all
Includes:
ClientStubs
Defined in:
lib/aws-sdk-bedrockruntime/client.rb

Overview

An API client for BedrockRuntime. To construct a client, you need to configure a ‘:region` and `:credentials`.

client = Aws::BedrockRuntime::Client.new(
  region: region_name,
  credentials: credentials,
  # ...
)

For details on configuring region and credentials see the [developer guide](/sdk-for-ruby/v3/developer-guide/setup-config.html).

See #initialize for a full list of supported configuration options.

Class Attribute Summary collapse

API Operations collapse

Class Method Summary collapse

Instance Method Summary collapse

Constructor Details

#initialize(options) ⇒ Client

Returns a new instance of Client.

Parameters:

  • options (Hash)

Options Hash (options):

  • :credentials (required, Aws::CredentialProvider) —

    Your AWS credentials. This can be an instance of any one of the following classes:

    • ‘Aws::Credentials` - Used for configuring static, non-refreshing credentials.

    • ‘Aws::SharedCredentials` - Used for loading static credentials from a shared file, such as `~/.aws/config`.

    • ‘Aws::AssumeRoleCredentials` - Used when you need to assume a role.

    • ‘Aws::AssumeRoleWebIdentityCredentials` - Used when you need to assume a role after providing credentials via the web.

    • ‘Aws::SSOCredentials` - Used for loading credentials from AWS SSO using an access token generated from `aws login`.

    • ‘Aws::ProcessCredentials` - Used for loading credentials from a process that outputs to stdout.

    • ‘Aws::InstanceProfileCredentials` - Used for loading credentials from an EC2 IMDS on an EC2 instance.

    • ‘Aws::ECSCredentials` - Used for loading credentials from instances running in ECS.

    • ‘Aws::CognitoIdentityCredentials` - Used for loading credentials from the Cognito Identity service.

    When ‘:credentials` are not configured directly, the following locations will be searched for credentials:

    • ‘Aws.config`

    • The ‘:access_key_id`, `:secret_access_key`, and `:session_token` options.

    • ENV, ENV

    • ‘~/.aws/credentials`

    • ‘~/.aws/config`

    • EC2/ECS IMDS instance profile - When used by default, the timeouts are very aggressive. Construct and pass an instance of ‘Aws::InstanceProfileCredentails` or `Aws::ECSCredentials` to enable retries and extended timeouts. Instance profile credential fetching can be disabled by setting ENV to true.

  • :region (required, String) —

    The AWS region to connect to. The configured ‘:region` is used to determine the service `:endpoint`. When not passed, a default `:region` is searched for in the following locations:

  • :access_key_id (String)
  • :active_endpoint_cache (Boolean) — default: false —

    When set to ‘true`, a thread polling for endpoints will be running in the background every 60 secs (default). Defaults to `false`.

  • :adaptive_retry_wait_to_fill (Boolean) — default: true —

    Used only in ‘adaptive` retry mode. When true, the request will sleep until there is sufficent client side capacity to retry the request. When false, the request will raise a `RetryCapacityNotAvailableError` and will not retry instead of sleeping.

  • :client_side_monitoring (Boolean) — default: false —

    When ‘true`, client-side metrics will be collected for all API requests from this client.

  • :client_side_monitoring_client_id (String) — default: "" —

    Allows you to provide an identifier for this client which will be attached to all generated client side metrics. Defaults to an empty string.

  • :client_side_monitoring_host (String) — default: "127.0.0.1" —

    Allows you to specify the DNS hostname or IPv4 or IPv6 address that the client side monitoring agent is running on, where client metrics will be published via UDP.

  • :client_side_monitoring_port (Integer) — default: 31000 —

    Required for publishing client metrics. The port that the client side monitoring agent is running on, where client metrics will be published via UDP.

  • :client_side_monitoring_publisher (Aws::ClientSideMonitoring::Publisher) — default: Aws::ClientSideMonitoring::Publisher —

    Allows you to provide a custom client-side monitoring publisher class. By default, will use the Client Side Monitoring Agent Publisher.

  • :convert_params (Boolean) — default: true —

    When ‘true`, an attempt is made to coerce request parameters into the required types.

  • :correct_clock_skew (Boolean) — default: true —

    Used only in ‘standard` and adaptive retry modes. Specifies whether to apply a clock skew correction and retry requests with skewed client clocks.

  • :defaults_mode (String) — default: "legacy" —

    See DefaultsModeConfiguration for a list of the accepted modes and the configuration defaults that are included.

  • :disable_host_prefix_injection (Boolean) — default: false —

    Set to true to disable SDK automatically adding host prefix to default service endpoint when available.

  • :disable_request_compression (Boolean) — default: false —

    When set to ‘true’ the request body will not be compressed for supported operations.

  • :endpoint (String, URI::HTTPS, URI::HTTP) —

    Normally you should not configure the ‘:endpoint` option directly. This is normally constructed from the `:region` option. Configuring `:endpoint` is normally reserved for connecting to test or custom endpoints. The endpoint should be a URI formatted like:

    'http://example.com'
'https://example.com'
'http://example.com:123'
  • :endpoint_cache_max_entries (Integer) — default: 1000 —

    Used for the maximum size limit of the LRU cache storing endpoints data for endpoint discovery enabled operations. Defaults to 1000.

  • :endpoint_cache_max_threads (Integer) — default: 10 —

    Used for the maximum threads in use for polling endpoints to be cached, defaults to 10.

  • :endpoint_cache_poll_interval (Integer) — default: 60 —

    When :endpoint_discovery and :active_endpoint_cache is enabled, Use this option to config the time interval in seconds for making requests fetching endpoints information. Defaults to 60 sec.

  • :endpoint_discovery (Boolean) — default: false —

    When set to ‘true`, endpoint discovery will be enabled for operations when available.

  • :event_stream_handler (Proc) —

    When an EventStream or Proc object is provided, it will be used as callback for each chunk of event stream response received along the way.

  • :ignore_configured_endpoint_urls (Boolean) —

    Setting to true disables use of endpoint URLs provided via environment variables and the shared configuration file.

  • :input_event_stream_handler (Proc) —

    When an EventStream or Proc object is provided, it can be used for sending events for the event stream.

  • :log_formatter (Aws::Log::Formatter) — default: Aws::Log::Formatter.default —

    The log formatter.

  • :log_level (Symbol) — default: :info —

    The log level to send messages to the ‘:logger` at.

  • :logger (Logger) —

    The Logger instance to send log messages to. If this option is not set, logging will be disabled.

  • :max_attempts (Integer) — default: 3 —

    An integer representing the maximum number attempts that will be made for a single request, including the initial attempt. For example, setting this value to 5 will result in a request being retried up to 4 times. Used in ‘standard` and `adaptive` retry modes.

  • :output_event_stream_handler (Proc) —

    When an EventStream or Proc object is provided, it will be used as callback for each chunk of event stream response received along the way.

  • :profile (String) — default: "default" —

    Used when loading credentials from the shared credentials file at HOME/.aws/credentials. When not specified, ‘default’ is used.

  • :request_min_compression_size_bytes (Integer) — default: 10240 —

    The minimum size in bytes that triggers compression for request bodies. The value must be non-negative integer value between 0 and 10485780 bytes inclusive.

  • :retry_backoff (Proc) —

    A proc or lambda used for backoff. Defaults to 2**retries * retry_base_delay. This option is only used in the ‘legacy` retry mode.

  • :retry_base_delay (Float) — default: 0.3 —

    The base delay in seconds used by the default backoff function. This option is only used in the ‘legacy` retry mode.

  • :retry_jitter (Symbol) — default: :none —

    A delay randomiser function used by the default backoff function. Some predefined functions can be referenced by name - :none, :equal, :full, otherwise a Proc that takes and returns a number. This option is only used in the ‘legacy` retry mode.

    @see www.awsarchitectureblog.com/2015/03/backoff.html

  • :retry_limit (Integer) — default: 3 —

    The maximum number of times to retry failed requests. Only ~ 500 level server errors and certain ~ 400 level client errors are retried. Generally, these are throttling errors, data checksum errors, networking errors, timeout errors, auth errors, endpoint discovery, and errors from expired credentials. This option is only used in the ‘legacy` retry mode.

  • :retry_max_delay (Integer) — default: 0 —

    The maximum number of seconds to delay between retries (0 for no limit) used by the default backoff function. This option is only used in the ‘legacy` retry mode.

  • :retry_mode (String) — default: "legacy" —

    Specifies which retry algorithm to use. Values are:

    • ‘legacy` - The pre-existing retry behavior. This is default value if no retry mode is provided.

    • ‘standard` - A standardized set of retry rules across the AWS SDKs. This includes support for retry quotas, which limit the number of unsuccessful retries a client can make.

    • ‘adaptive` - An experimental retry mode that includes all the functionality of `standard` mode along with automatic client side throttling. This is a provisional mode that may change behavior in the future.

  • :sdk_ua_app_id (String) —

    A unique and opaque application ID that is appended to the User-Agent header as app/<sdk_ua_app_id>. It should have a maximum length of 50.

  • :secret_access_key (String)
  • :session_token (String)
  • :stub_responses (Boolean) — default: false —

    Causes the client to return stubbed responses. By default fake responses are generated and returned. You can specify the response data to return or errors to raise by calling ClientStubs#stub_responses. See ClientStubs for more information.

    ** Please note ** When response stubbing is enabled, no HTTP requests are made, and retries are disabled.

  • :token_provider (Aws::TokenProvider) —

    A Bearer Token Provider. This can be an instance of any one of the following classes:

    • ‘Aws::StaticTokenProvider` - Used for configuring static, non-refreshing tokens.

    • ‘Aws::SSOTokenProvider` - Used for loading tokens from AWS SSO using an access token generated from `aws login`.

    When ‘:token_provider` is not configured directly, the `Aws::TokenProviderChain` will be used to search for tokens configured for your profile in shared configuration files.

  • :use_dualstack_endpoint (Boolean) —

    When set to ‘true`, dualstack enabled endpoints (with `.aws` TLD) will be used if available.

  • :use_fips_endpoint (Boolean) —

    When set to ‘true`, fips compatible endpoints will be used if available. When a `fips` region is used, the region is normalized and this config is set to `true`.

  • :validate_params (Boolean) — default: true —

    When ‘true`, request parameters are validated before sending the request.

  • :endpoint_provider (Aws::BedrockRuntime::EndpointProvider) —

    The endpoint provider used to resolve endpoints. Any object that responds to ‘#resolve_endpoint(parameters)` where `parameters` is a Struct similar to `Aws::BedrockRuntime::EndpointParameters`

  • :http_continue_timeout (Float) — default: 1 —

    The number of seconds to wait for a 100-continue response before sending the request body. This option has no effect unless the request has “Expect” header set to “100-continue”. Defaults to ‘nil` which disables this behaviour. This value can safely be set per request on the session.

  • :http_idle_timeout (Float) — default: 5 —

    The number of seconds a connection is allowed to sit idle before it is considered stale. Stale connections are closed and removed from the pool before making a request.

  • :http_open_timeout (Float) — default: 15 —

    The default number of seconds to wait for response data. This value can safely be set per-request on the session.

  • :http_proxy (URI::HTTP, String) —

    A proxy to send requests through. Formatted like ‘proxy.com:123’.

  • :http_read_timeout (Float) — default: 60 —

    The default number of seconds to wait for response data. This value can safely be set per-request on the session.

  • :http_wire_trace (Boolean) — default: false —

    When ‘true`, HTTP debug output will be sent to the `:logger`.

  • :on_chunk_received (Proc) —

    When a Proc object is provided, it will be used as callback when each chunk of the response body is received. It provides three arguments: the chunk, the number of bytes received, and the total number of bytes in the response (or nil if the server did not send a ‘content-length`).

  • :on_chunk_sent (Proc) —

    When a Proc object is provided, it will be used as callback when each chunk of the request body is sent. It provides three arguments: the chunk, the number of bytes read from the body, and the total number of bytes in the body.

  • :raise_response_errors (Boolean) — default: true —

    When ‘true`, response errors are raised.

  • :ssl_ca_bundle (String) —

    Full path to the SSL certificate authority bundle file that should be used when verifying peer certificates. If you do not pass ‘:ssl_ca_bundle` or `:ssl_ca_directory` the the system default will be used if available.

  • :ssl_ca_directory (String) —

    Full path of the directory that contains the unbundled SSL certificate authority files for verifying peer certificates. If you do not pass ‘:ssl_ca_bundle` or `:ssl_ca_directory` the the system default will be used if available.

  • :ssl_ca_store (String) —

    Sets the X509::Store to verify peer certificate.

  • :ssl_timeout (Float) —

    Sets the SSL timeout in seconds

  • :ssl_verify_peer (Boolean) — default: true —

    When ‘true`, SSL peer certificates are verified when establishing a connection.



420
421
422
 
# File 'lib/aws-sdk-bedrockruntime/client.rb', line 420

def initialize(*args)
  super
end

Class Attribute Details

.identifier ⇒ Object (readonly)

This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future. 



846
847
848
 
# File 'lib/aws-sdk-bedrockruntime/client.rb', line 846

def identifier
  @identifier
end

Class Method Details

.errors_module ⇒ Object

This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future. 



849
850
851
 
# File 'lib/aws-sdk-bedrockruntime/client.rb', line 849

def errors_module
  Errors
end

Instance Method Details

#build_request(operation_name, params = {}) ⇒ Object

This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.

Parameters:

  • params ({}) (defaults to: {}) 


824
825
826
827
828
829
830
831
832
833
834
835
 
# File 'lib/aws-sdk-bedrockruntime/client.rb', line 824

def build_request(operation_name, params = {})
  handlers = @handlers.for(operation_name)
  context = Seahorse::Client::RequestContext.new(
    operation_name: operation_name,
    operation: config.api.operation(operation_name),
    client: self,
    params: params,
    config: config)
  context[:gem_name] = 'aws-sdk-bedrockruntime'
  context[:gem_version] = '1.7.0'
  Seahorse::Client::Request.new(handlers, context)
end

#invoke_model(params = {}) ⇒ Types::InvokeModelResponse

Invokes the specified Amazon Bedrock model to run inference using the prompt and inference parameters provided in the request body. You use model inference to generate text, images, and embeddings.

For example code, see *Invoke model code examples* in the *Amazon Bedrock User Guide*.

This operation requires permission for the ‘bedrock:InvokeModel` action.

Examples:

Request syntax with placeholder values


resp = client.invoke_model({
  body: "data", # required
  content_type: "MimeType",
  accept: "MimeType",
  model_id: "InvokeModelIdentifier", # required
  trace: "ENABLED", # accepts ENABLED, DISABLED
  guardrail_identifier: "GuardrailIdentifier",
  guardrail_version: "GuardrailVersion",
})

Response structure


resp.body #=> String
resp.content_type #=> String

Parameters:

  • params (Hash) (defaults to: {}) —

    ({})

Options Hash (params):

  • :body (required, String, StringIO, File) —

    The prompt and inference parameters in the format specified in the ‘contentType` in the header. To see the format and content of the request and response bodies for different models, refer to [Inference parameters]. For more information, see [Run inference] in the Bedrock User Guide.

    [1]: docs.aws.amazon.com/bedrock/latest/userguide/model-parameters.html [2]: docs.aws.amazon.com/bedrock/latest/userguide/api-methods-run.html

  • :content_type (String) —

    The MIME type of the input data in the request. The default value is ‘application/json`.

  • :accept (String) —

    The desired MIME type of the inference body in the response. The default value is ‘application/json`.

  • :model_id (required, String) —

    The unique identifier of the model to invoke to run inference.

    The ‘modelId` to provide depends on the type of model that you use:

    • If you use a base model, specify the model ID or its ARN. For a list of model IDs for base models, see [Amazon Bedrock base model IDs (on-demand throughput)] in the Amazon Bedrock User Guide.

    • If you use a provisioned model, specify the ARN of the Provisioned Throughput. For more information, see [Run inference using a Provisioned Throughput] in the Amazon Bedrock User Guide.

    • If you use a custom model, first purchase Provisioned Throughput for it. Then specify the ARN of the resulting provisioned model. For more information, see [Use a custom model in Amazon Bedrock] in the Amazon Bedrock User Guide.

    [1]: docs.aws.amazon.com/bedrock/latest/userguide/model-ids.html#model-ids-arns [2]: docs.aws.amazon.com/bedrock/latest/userguide/prov-thru-use.html [3]: docs.aws.amazon.com/bedrock/latest/userguide/model-customization-use.html

  • :trace (String) —

    Specifies whether to enable or disable the Bedrock trace. If enabled, you can see the full Bedrock trace.

  • :guardrail_identifier (String) —

    The unique identifier of the guardrail that you want to use. If you don’t provide a value, no guardrail is applied to the invocation.

    An error will be thrown in the following situations.

    • You don’t provide a guardrail identifier but you specify the ‘amazon-bedrock-guardrailConfig` field in the request body.

    • You enable the guardrail but the ‘contentType` isn’t ‘application/json`.

    • You provide a guardrail identifier, but ‘guardrailVersion` isn’t specified.

  • :guardrail_version (String) —

    The version number for the guardrail. The value can also be ‘DRAFT`.

Returns:

See Also:



528
529
530
531
 
# File 'lib/aws-sdk-bedrockruntime/client.rb', line 528

def invoke_model(params = {}, options = {})
  req = build_request(:invoke_model, params)
  req.send_request(options)
end

#invoke_model_with_response_stream(params = {}) ⇒ Types::InvokeModelWithResponseStreamResponse

Invoke the specified Amazon Bedrock model to run inference using the prompt and inference parameters provided in the request body. The response is returned in a stream.

To see if a model supports streaming, call [GetFoundationModel] and check the ‘responseStreamingSupported` field in the response.

<note markdown=“1”> The CLI doesn’t support ‘InvokeModelWithResponseStream`.

</note>

For example code, see *Invoke model with streaming code example* in the *Amazon Bedrock User Guide*.

This operation requires permissions to perform the ‘bedrock:InvokeModelWithResponseStream` action.

[1]: docs.aws.amazon.com/bedrock/latest/APIReference/API_GetFoundationModel.html

Examples:

EventStream Operation Example


You can process the event once it arrives immediately, or wait until the
full response is complete and iterate through the eventstream enumerator.

To interact with event immediately, you need to register #invoke_model_with_response_stream
with callbacks. Callbacks can be registered for specific events or for all
events, including error events.

Callbacks can be passed into the `:event_stream_handler` option or within a
block statement attached to the #invoke_model_with_response_stream call directly. Hybrid
pattern of both is also supported.

`:event_stream_handler` option takes in either a Proc object or
Aws::BedrockRuntime::EventStreams::ResponseStream object.

Usage pattern a): Callbacks with a block attached to #invoke_model_with_response_stream
  Example for registering callbacks for all event types and an error event

  client.invoke_model_with_response_stream( # params input# ) do |stream|
    stream.on_error_event do |event|
      # catch unmodeled error event in the stream
      raise event
      # => Aws::Errors::EventError
      # event.event_type => :error
      # event.error_code => String
      # event.error_message => String
    end

    stream.on_event do |event|
      # process all events arrive
      puts event.event_type
      ...
    end

  end

Usage pattern b): Pass in `:event_stream_handler` for #invoke_model_with_response_stream

  1) Create a Aws::BedrockRuntime::EventStreams::ResponseStream object
  Example for registering callbacks with specific events

    handler = Aws::BedrockRuntime::EventStreams::ResponseStream.new
    handler.on_chunk_event do |event|
      event # => Aws::BedrockRuntime::Types::chunk
    end
    handler.on_internal_server_exception_event do |event|
      event # => Aws::BedrockRuntime::Types::internalServerException
    end
    handler.on_model_stream_error_exception_event do |event|
      event # => Aws::BedrockRuntime::Types::modelStreamErrorException
    end
    handler.on_validation_exception_event do |event|
      event # => Aws::BedrockRuntime::Types::validationException
    end
    handler.on_throttling_exception_event do |event|
      event # => Aws::BedrockRuntime::Types::throttlingException
    end
    handler.on_model_timeout_exception_event do |event|
      event # => Aws::BedrockRuntime::Types::modelTimeoutException
    end

  client.invoke_model_with_response_stream( # params input #, event_stream_handler: handler)

  2) Use a Ruby Proc object
  Example for registering callbacks with specific events

  handler = Proc.new do |stream|
    stream.on_chunk_event do |event|
      event # => Aws::BedrockRuntime::Types::chunk
    end
    stream.on_internal_server_exception_event do |event|
      event # => Aws::BedrockRuntime::Types::internalServerException
    end
    stream.on_model_stream_error_exception_event do |event|
      event # => Aws::BedrockRuntime::Types::modelStreamErrorException
    end
    stream.on_validation_exception_event do |event|
      event # => Aws::BedrockRuntime::Types::validationException
    end
    stream.on_throttling_exception_event do |event|
      event # => Aws::BedrockRuntime::Types::throttlingException
    end
    stream.on_model_timeout_exception_event do |event|
      event # => Aws::BedrockRuntime::Types::modelTimeoutException
    end
  end

  client.invoke_model_with_response_stream( # params input #, event_stream_handler: handler)

Usage pattern c): Hybrid pattern of a) and b)

    handler = Aws::BedrockRuntime::EventStreams::ResponseStream.new
    handler.on_chunk_event do |event|
      event # => Aws::BedrockRuntime::Types::chunk
    end
    handler.on_internal_server_exception_event do |event|
      event # => Aws::BedrockRuntime::Types::internalServerException
    end
    handler.on_model_stream_error_exception_event do |event|
      event # => Aws::BedrockRuntime::Types::modelStreamErrorException
    end
    handler.on_validation_exception_event do |event|
      event # => Aws::BedrockRuntime::Types::validationException
    end
    handler.on_throttling_exception_event do |event|
      event # => Aws::BedrockRuntime::Types::throttlingException
    end
    handler.on_model_timeout_exception_event do |event|
      event # => Aws::BedrockRuntime::Types::modelTimeoutException
    end

  client.invoke_model_with_response_stream( # params input #, event_stream_handler: handler) do |stream|
    stream.on_error_event do |event|
      # catch unmodeled error event in the stream
      raise event
      # => Aws::Errors::EventError
      # event.event_type => :error
      # event.error_code => String
      # event.error_message => String
    end
  end

You can also iterate through events after the response complete.

Events are available at resp.body # => Enumerator
For parameter input example, please refer to following request syntax

Request syntax with placeholder values


resp = client.invoke_model_with_response_stream({
  body: "data", # required
  content_type: "MimeType",
  accept: "MimeType",
  model_id: "InvokeModelIdentifier", # required
  trace: "ENABLED", # accepts ENABLED, DISABLED
  guardrail_identifier: "GuardrailIdentifier",
  guardrail_version: "GuardrailVersion",
})

Response structure


All events are available at resp.body:
resp.body #=> Enumerator
resp.body.event_types #=> [:chunk, :internal_server_exception, :model_stream_error_exception, :validation_exception, :throttling_exception, :model_timeout_exception]

For :chunk event available at #on_chunk_event callback and response eventstream enumerator:
event.bytes #=> String

For :internal_server_exception event available at #on_internal_server_exception_event callback and response eventstream enumerator:
event.message #=> String

For :model_stream_error_exception event available at #on_model_stream_error_exception_event callback and response eventstream enumerator:
event.message #=> String
event.original_status_code #=> Integer
event.original_message #=> String

For :validation_exception event available at #on_validation_exception_event callback and response eventstream enumerator:
event.message #=> String

For :throttling_exception event available at #on_throttling_exception_event callback and response eventstream enumerator:
event.message #=> String

For :model_timeout_exception event available at #on_model_timeout_exception_event callback and response eventstream enumerator:
event.message #=> String

resp.content_type #=> String

Parameters:

  • params (Hash) (defaults to: {}) —

    ({})

Options Hash (params):

  • :body (required, String, StringIO, File) —

    The prompt and inference parameters in the format specified in the ‘contentType` in the header. To see the format and content of the request and response bodies for different models, refer to [Inference parameters]. For more information, see [Run inference] in the Bedrock User Guide.

    [1]: docs.aws.amazon.com/bedrock/latest/userguide/model-parameters.html [2]: docs.aws.amazon.com/bedrock/latest/userguide/api-methods-run.html

  • :content_type (String) —

    The MIME type of the input data in the request. The default value is ‘application/json`.

  • :accept (String) —

    The desired MIME type of the inference body in the response. The default value is ‘application/json`.

  • :model_id (required, String) —

    The unique identifier of the model to invoke to run inference.

    The ‘modelId` to provide depends on the type of model that you use:

    • If you use a base model, specify the model ID or its ARN. For a list of model IDs for base models, see [Amazon Bedrock base model IDs (on-demand throughput)] in the Amazon Bedrock User Guide.

    • If you use a provisioned model, specify the ARN of the Provisioned Throughput. For more information, see [Run inference using a Provisioned Throughput] in the Amazon Bedrock User Guide.

    • If you use a custom model, first purchase Provisioned Throughput for it. Then specify the ARN of the resulting provisioned model. For more information, see [Use a custom model in Amazon Bedrock] in the Amazon Bedrock User Guide.

    [1]: docs.aws.amazon.com/bedrock/latest/userguide/model-ids.html#model-ids-arns [2]: docs.aws.amazon.com/bedrock/latest/userguide/prov-thru-use.html [3]: docs.aws.amazon.com/bedrock/latest/userguide/model-customization-use.html

  • :trace (String) —

    Specifies whether to enable or disable the Bedrock trace. If enabled, you can see the full Bedrock trace.

  • :guardrail_identifier (String) —

    The unique identifier of the guardrail that you want to use. If you don’t provide a value, no guardrail is applied to the invocation.

    An error is thrown in the following situations.

    • You don’t provide a guardrail identifier but you specify the ‘amazon-bedrock-guardrailConfig` field in the request body.

    • You enable the guardrail but the ‘contentType` isn’t ‘application/json`.

    • You provide a guardrail identifier, but ‘guardrailVersion` isn’t specified.

  • :guardrail_version (String) —

    The version number for the guardrail. The value can also be ‘DRAFT`.

Yields:

  • (event_stream_handler)

Returns:

See Also:



797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
 
# File 'lib/aws-sdk-bedrockruntime/client.rb', line 797

def invoke_model_with_response_stream(params = {}, options = {}, &block)
  params = params.dup
  event_stream_handler = case handler = params.delete(:event_stream_handler)
    when EventStreams::ResponseStream then handler
    when Proc then EventStreams::ResponseStream.new.tap(&handler)
    when nil then EventStreams::ResponseStream.new
    else
      msg = "expected :event_stream_handler to be a block or "\
            "instance of Aws::BedrockRuntime::EventStreams::ResponseStream"\
            ", got `#{handler.inspect}` instead"
      raise ArgumentError, msg
    end

  yield(event_stream_handler) if block_given?

  req = build_request(:invoke_model_with_response_stream, params)

  req.context[:event_stream_handler] = event_stream_handler
  req.handlers.add(Aws::Binary::DecodeHandler, priority: 95)

  req.send_request(options, &block)
end

#waiter_names ⇒ Object

This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.

Deprecated. 


839
840
841
 
# File 'lib/aws-sdk-bedrockruntime/client.rb', line 839

def waiter_names
  []
end