You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(client-firehose): Amazon Data Firehose / Features : Adds support for a new DeliveryStreamType, DatabaseAsSource. DatabaseAsSource hoses allow customers to stream CDC events from their RDS and Amazon EC2 hosted databases, running MySQL and PostgreSQL database engines, to Iceberg Table destinations.
* <p>By default, you can create up to 50 delivery streams per Amazon Web Services
35
+
* <p>Creates a Firehose stream.</p>
36
+
* <p>By default, you can create up to 50 Firehose streams per Amazon Web Services
37
37
* Region.</p>
38
38
* <p>This is an asynchronous operation that immediately returns. The initial status of the
39
-
* delivery stream is <code>CREATING</code>. After the delivery stream is created, its status
40
-
* is <code>ACTIVE</code> and it now accepts data. If the delivery stream creation fails, the
39
+
* Firehose stream is <code>CREATING</code>. After the Firehose stream is created, its status
40
+
* is <code>ACTIVE</code> and it now accepts data. If the Firehose stream creation fails, the
41
41
* status transitions to <code>CREATING_FAILED</code>. Attempts to send data to a delivery
42
42
* stream that is not in the <code>ACTIVE</code> state cause an exception. To check the state
43
-
* of a delivery stream, use <a>DescribeDeliveryStream</a>.</p>
44
-
* <p>If the status of a delivery stream is <code>CREATING_FAILED</code>, this status
43
+
* of a Firehose stream, use <a>DescribeDeliveryStream</a>.</p>
44
+
* <p>If the status of a Firehose stream is <code>CREATING_FAILED</code>, this status
45
45
* doesn't change, and you can't invoke <code>CreateDeliveryStream</code> again on it.
46
46
* However, you can invoke the <a>DeleteDeliveryStream</a> operation to delete
47
47
* it.</p>
48
-
* <p>A Firehose delivery stream can be configured to receive records directly
48
+
* <p>A Firehose stream can be configured to receive records directly
49
49
* from providers using <a>PutRecord</a> or <a>PutRecordBatch</a>, or it
50
50
* can be configured to use an existing Kinesis stream as its source. To specify a Kinesis
51
51
* data stream as input, set the <code>DeliveryStreamType</code> parameter to
52
52
* <code>KinesisStreamAsSource</code>, and provide the Kinesis stream Amazon Resource Name
53
53
* (ARN) and role ARN in the <code>KinesisStreamSourceConfiguration</code>
54
54
* parameter.</p>
55
-
* <p>To create a delivery stream with server-side encryption (SSE) enabled, include <a>DeliveryStreamEncryptionConfigurationInput</a> in your request. This is
55
+
* <p>To create a Firehose stream with server-side encryption (SSE) enabled, include <a>DeliveryStreamEncryptionConfigurationInput</a> in your request. This is
56
56
* optional. You can also invoke <a>StartDeliveryStreamEncryption</a> to turn on
57
-
* SSE for an existing delivery stream that doesn't have SSE enabled.</p>
58
-
* <p>A delivery stream is configured with a single destination, such as Amazon Simple
57
+
* SSE for an existing Firehose stream that doesn't have SSE enabled.</p>
58
+
* <p>A Firehose stream is configured with a single destination, such as Amazon Simple
* <p>You can delete a delivery stream only if it is in one of the following states:
31
+
* <p>Deletes a Firehose stream and its data.</p>
32
+
* <p>You can delete a Firehose stream only if it is in one of the following states:
33
33
* <code>ACTIVE</code>, <code>DELETING</code>, <code>CREATING_FAILED</code>, or
34
-
* <code>DELETING_FAILED</code>. You can't delete a delivery stream that is in the
35
-
* <code>CREATING</code> state. To check the state of a delivery stream, use <a>DescribeDeliveryStream</a>. </p>
36
-
* <p>DeleteDeliveryStream is an asynchronous API. When an API request to DeleteDeliveryStream succeeds, the delivery stream is marked for deletion, and it goes into the
37
-
* <code>DELETING</code> state.While the delivery stream is in the <code>DELETING</code> state, the service might
34
+
* <code>DELETING_FAILED</code>. You can't delete a Firehose stream that is in the
35
+
* <code>CREATING</code> state. To check the state of a Firehose stream, use <a>DescribeDeliveryStream</a>. </p>
36
+
* <p>DeleteDeliveryStream is an asynchronous API. When an API request to DeleteDeliveryStream succeeds, the Firehose stream is marked for deletion, and it goes into the
37
+
* <code>DELETING</code> state.While the Firehose stream is in the <code>DELETING</code> state, the service might
38
38
* continue to accept records, but it doesn't make any guarantees with respect to delivering
39
39
* the data. Therefore, as a best practice, first stop any applications that are sending
40
-
* records before you delete a delivery stream.</p>
41
-
* <p>Removal of a delivery stream that is in the <code>DELETING</code> state is a low priority operation for the service. A stream may remain in the
40
+
* records before you delete a Firehose stream.</p>
41
+
* <p>Removal of a Firehose stream that is in the <code>DELETING</code> state is a low priority operation for the service. A stream may remain in the
42
42
* <code>DELETING</code> state for several minutes. Therefore, as a best practice, applications should not wait for streams in the <code>DELETING</code> state
* <p>Describes the specified delivery stream and its status. For example, after your
36
-
* delivery stream is created, call <code>DescribeDeliveryStream</code> to see whether the
37
-
* delivery stream is <code>ACTIVE</code> and therefore ready for data to be sent to it. </p>
38
-
* <p>If the status of a delivery stream is <code>CREATING_FAILED</code>, this status
35
+
* <p>Describes the specified Firehose stream and its status. For example, after your
36
+
* Firehose stream is created, call <code>DescribeDeliveryStream</code> to see whether the
37
+
* Firehose stream is <code>ACTIVE</code> and therefore ready for data to be sent to it. </p>
38
+
* <p>If the status of a Firehose stream is <code>CREATING_FAILED</code>, this status
39
39
* doesn't change, and you can't invoke <a>CreateDeliveryStream</a> again on it.
40
40
* However, you can invoke the <a>DeleteDeliveryStream</a> operation to delete it.
41
41
* If the status is <code>DELETING_FAILED</code>, you can force deletion by invoking <a>DeleteDeliveryStream</a> again but with <a>DeleteDeliveryStreamInput$AllowForceDelete</a> set to true.</p>
0 commit comments