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): This release adds support for Data Message Extraction for decompressed CloudWatch logs, and to use a custom file extension or time zone for S3 destinations.
* <p>We strongly recommend that you use the user name and password you provide
94
-
* exclusively with Kinesis Data Firehose, and that the permissions for the account are
94
+
* exclusively with Firehose, and that the permissions for the account are
95
95
* restricted for Amazon Redshift <code>INSERT</code> permissions.</p>
96
96
* </li>
97
97
* </ul>
98
-
* <p>Kinesis Data Firehose assumes the IAM role that is configured as part of the
99
-
* destination. The role should allow the Kinesis Data Firehose principal to assume the role,
98
+
* <p>Firehose assumes the IAM role that is configured as part of the
99
+
* destination. The role should allow the Firehose principal to assume the role,
100
100
* and the role should have permissions that allow the service to deliver the data. For more
101
-
* information, see <a href="https://docs.aws.amazon.com/firehose/latest/dev/controlling-access.html#using-iam-s3">Grant Kinesis Data
102
-
* Firehose Access to an Amazon S3 Destination</a> in the <i>Amazon Kinesis Data
103
-
* Firehose Developer Guide</i>.</p>
101
+
* information, see <a href="https://docs.aws.amazon.com/firehose/latest/dev/controlling-access.html#using-iam-s3">Grant Firehose Access to an Amazon S3 Destination</a> in the <i>Amazon Firehose Developer Guide</i>.</p>
104
102
* @example
105
103
* Use a bare-bones client and the command you need to make an API call.
* <p>To check the state of a delivery stream, use <a>DescribeDeliveryStream</a>. You can delete a delivery stream only if it is in one of the following states:
32
+
* <p>You can delete a delivery 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
34
* <code>DELETING_FAILED</code>. You can't delete a delivery stream that is in the
35
-
* <code>CREATING</code> state. While the deletion request is in process, the delivery
36
-
* stream is in the <code>DELETING</code> state.</p>
37
-
* <p>While the delivery stream is in the <code>DELETING</code> state, the service might
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
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
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
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
43
+
* to be removed. </p>
41
44
* @example
42
45
* Use a bare-bones client and the command you need to make an API call.
0 commit comments