本文属于机器翻译版本。若本译文内容与英语原文存在差异，则一律以英文原文为准。
使用日志监控 Amazon Data Firehose CloudWatch
Amazon Data Firehose 与 Amazon L CloudWatch ogs 集成，以便您可以在数据转换或数据传输的 Lambda 调用失败时查看特定错误日志。当您创建 Firehose 流时，可以启用 Amazon Data Firehose 错误日志记录。
在 Amazon Data Firehose 控制台中启用 Amazon Data Firehose 错误日志记录时，系统会代表您为 Firehose 流创建日志组和相应的日志流。日志组名称的格式为 /aws/kinesisfirehose/，其中 delivery-stream-namedelivery-stream-nameDestinationDelivery 是创建的日志流，用于日志记录与传输到主要目的地相关的所有错误。只有在为目标启用了 S3 备份时，才会创建另一个名为 BackupDelivery 的日志流。BackupDelivery 日志流用于记录与传输到 S3 备份相关的任何错误。
例如，如果您以 Amazon Redsift 为目标创建了 Firehose 流 MyStream “”，并启用 Amazon Data Firehose 错误日志记录，则代表您创建以下内容：名为的日志组和两个aws/kinesisfirehose/MyStream名为和的日志流。DestinationDelivery BackupDelivery在本例中，DestinationDelivery 用于记录与传输到 Amazon Redshift 目标以及中间 S3 目标相关的任何错误。如果启用了 S3 备份，BackupDelivery 用来记录与传输到 S3 备份存储桶相关的任何错误。
您可以通过 Amazon CLI、API 或， Amazon CloudFormation 使用配置来启用 Amazon Data Firehose 错误日志记录。CloudWatchLoggingOptions为此，请提前创建日志组和日志流。建议保留该日志组和日志流用于 Amazon Data Firehose 错误日志记录。此外，还要确保关联的 IAM policy 拥有 "logs:putLogEvents" 权限。有关更多信息，请参阅 使用 Amazon Data Firehose 控制访问权限。
请注意，Amazon Data Firehose 不保证所有传输错误日志都发送到 CloudWatch Logs。传输失败率较高的情况下，在将传输错误日志发送到 Logs 之前，Amazon Data Firehose 会对日志进行 CloudWatch 采样。
对于传输到 Logs 的错误日志，会收取一 CloudWatch 定的费用。有关更多信息，请参阅 Amazon CloudWatch 定价
内容
数据传输错误
以下是每个 Amazon Data Firehose 目的地的数据传输错误代码和消息的列表。每个错误消息还描述了修复问题所应采取的适当操作。
错误
Amazon S3 数据传输错误
Amazon Data Firehose 可以将以下 Amazon S3 相关错误发送到 Logs。 CloudWatch
| 错误代码 | 错误消息和信息 |
|---|---|
S3.KMS.NotFoundException |
“找不到提供的 Amazon KMS 密钥。如果您使用的是您认为有效的 Amazon KMS 密钥和正确的角色，请检查关联 Amazon KMS 密钥的账户是否存在问题。” |
S3.KMS.RequestLimitExceeded |
"The KMS request per second limit was exceeded while attempting to encrypt S3 objects。Increase the request per second limit." 有关更多信息，请参阅《Amazon Key Management Service 开发人员指南》中的限制。 |
S3.AccessDenied |
"Access was denied。Ensure that the trust policy for the provided IAM role allows Amazon Data Firehose to assume the role, and the access policy allows access to the S3 bucket." |
S3.AccountProblem |
“您的存在问题 Amazon ，导致无法成功完成操作。Contact Amazon Support." |
S3.AllAccessDisabled |
"Access to the account provided has been disabled。联系 Su Amazon pport.” |
S3.InvalidPayer |
"Access to the account provided has been disabled。联系 Su Amazon pport.” |
S3.NotSignedUp |
"The account is not signed up for Amazon S3. Sign the account up or use a different account." |
S3.NoSuchBucket |
"The specified bucket does not exist。Create the bucket or use a different bucket that does exist." |
S3.MethodNotAllowed |
"The specified method is not allowed against this resource。Modify the bucket’s policy to allow the correct Amazon S3 operation permissions." |
InternalError |
"An internal error occurred while attempting to deliver data。Delivery will be retried; if the error persists, it will Amazon be retried |
S3.KMS.KeyDisabled |
"The provided KMS key is disabled. Enable the key or use a different key." |
S3.KMS.InvalidStateException |
"The provided KMS key is in an invalid state. Please use a different key." |
KMS.InvalidStateException |
"The provided KMS key is in an invalid state. Please use a different key." |
KMS.DisabledException |
"The provided KMS key is disabled. Please fix the key or use a different key." |
S3.SlowDown |
"The rate of put request to the specified bucket was too high. Increase Firehose stream buffer size or reduce put requests from other applications." |
S3.SubscriptionRequired |
"Access was denied when calling S3. Ensure that the IAM role and the KMS Key (if provided) passed in has Amazon S3 subscription." |
S3.InvalidToken |
"The provided token is malformed or otherwise invalid. Please check the credentials provided." |
S3.KMS.KeyNotConfigured |
"KMS key not configured. 配置您的 KMSMaster KeyID, 或针对该存储桶禁用加密。” |
S3.KMS.AsymmetricCMKNotSupported |
“Amazon S3 仅支持对称 CMKs。You cannot use an asymmetric CMK to encrypt your data in Amazon S3. 要获取 CMK 的类型，请使用 KMS DescribeKey 操作。” |
S3.IllegalLocationConstraintException |
"Firehose currently uses s3 global endpoint for data delivery to the configured s3 bucket. The region of the configured s3 bucket doesn't support s3 global endpoint. Please create a Firehose stream in the same region as the s3 bucket or use s3 bucket in the region that supports global endpoint." |
S3.InvalidPrefixConfigurationException |
"The custom s3 prefix used for the timestamp evaluation is invalid. Check your s3 prefix contains valid expressions for the current date and time of the year." |
DataFormatConversion.MalformedData |
"Illegal character found between tokens." |
Apache Iceberg 表数据传输错误
有关 Apache Iceberg 表数据传输错误，请参阅使用 Amazon Data Firehose 将数据传输到 Apache Iceberg 表。
Amazon Redshift 数据传输错误
Amazon Data Firehose 可以将以下 Amazon Redshift 相关错误发送到 Logs。 CloudWatch
| 错误代码 | 错误消息和信息 |
|---|---|
Redshift.TableNotFound |
"The table to which to load data was not found。Ensure that the specified table exists." The destination table in Amazon Redshift to which data should be copied from S3 was not found. Note that Amazon Data Firehose does not create the Amazon Redshift table if it does not exist. |
Redshift.SyntaxError |
"The COPY command contains a syntax error。Retry the command." |
Redshift.AuthenticationFailed |
"The provided user name and password failed authentication。Provide a valid user name and password." |
Redshift.AccessDenied |
"Access was denied。Ensure that the trust policy for the provided IAM role allows Amazon Data Firehose to assume the role." |
Redshift.S3BucketAccessDenied |
"The COPY command was unable to access the S3 bucket。Ensure that the access policy for the provided IAM role allows access to the S3 bucket." |
Redshift.DataLoadFailed |
"Loading data into the table failed。Check STL_LOAD_ERRORS system table for details." |
Redshift.ColumnNotFound |
"A column in the COPY command does not exist in the table。Specify a valid column name." |
Redshift.DatabaseNotFound |
"The database specified in the Amazon Redshift destination configuration or JDBC URL was not found. Specify a valid database name." |
Redshift.IncorrectCopyOptions |
"Conflicting or redundant COPY options were provided。Some options are not compatible in certain combinations。Check the COPY command reference for more info." 有关更多信息，请参阅《Amazon Redshift 数据库开发人员指南》中的 Amazon Redshift COPY 命令。 |
Redshift.MissingColumn |
"There is a column defined in the table schema as NOT NULL without a DEFAULT value and not included in the column list。Exclude this column, ensure that the loaded data always provides a value for this column, or add a default value to the Amazon Redshift schema for this table." |
Redshift.ConnectionFailed |
"The connection to the specified Amazon Redshift cluster failed. Ensure that security settings allow Amazon Data Firehose connections, that the cluster or database specified in the Amazon Redshift destination configuration or JDBC URL is correct, and that the cluster is available." |
Redshift.ColumnMismatch |
"The number of jsonpaths in the COPY command and the number of columns in the destination table should match。Retry the command." |
Redshift.IncorrectOrMissingRegion |
"Amazon Redshift attempted to use the wrong region endpoint for accessing the S3 bucket. Either specify a correct region value in the COPY command options or ensure that the S3 bucket is in the same region as the Amazon Redshift database." |
Redshift.IncorrectJsonPathsFile |
"The provided jsonpaths file is not in a supported JSON format。Retry the command." |
Redshift.MissingS3File |
"One or more S3 files required by Amazon Redshift have been removed from the S3 bucket. Check the S3 bucket policies to remove any automatic deletion of S3 files." |
Redshift.InsufficientPrivilege |
"The user does not have permissions to load data into the table。Check the Amazon Redshift user permissions for the INSERT privilege." |
Redshift.ReadOnlyCluster |
"The query cannot be executed because the system is in resize mode。Try the query again later." |
Redshift.DiskFull |
"Data could not be loaded because the disk is full。Increase the capacity of the Amazon Redshift cluster or delete unused data to free disk space." |
InternalError |
"An internal error occurred while attempting to deliver data。Delivery will be retried; if the error persists, it will Amazon be retried |
Redshift.ArgumentNotSupported |
"The COPY command contains unsupported options." |
Redshift.AnalyzeTableAccessDenied |
"Access denied. Copy from S3 to Redshift is failing because analyze table can only be done by table or database owner." |
Redshift.SchemaNotFound |
“The schema the Amazon Redshift 目标配置中指定的架构未找到。 DataTableName Specify a valid schema name." |
Redshift.ColumnSpecifiedMoreThanOnce |
"There is a column specified more than once in the column list. Ensure that duplicate columns are removed." |
Redshift.ColumnNotNullWithoutDefault |
"There is a non-null column without DEFAULT that is not included in the column list. Ensure that such columns are included in the column list." |
Redshift.IncorrectBucketRegion |
"Redshift attempted to use a bucket in a different region from the cluster. Please specify a bucket within the same region as the cluster." |
Redshift.S3SlowDown |
"High request rate to S3. Reduce the rate to avoid getting throttled." |
Redshift.InvalidCopyOptionForJson |
"Please use either auto or a valid S3 path for json copyOption." |
Redshift.InvalidCopyOptionJSONPathFormat |
“COPY failed failed with JSONPath format Array index is out of range\". Please check JSONPath your the |
Redshift.InvalidCopyOptionRBACAclNotAllowed |
"COPY failed with error \"Cannot use RBAC acl framework while permission propagation is not enabled.\" |
Redshift.DiskSpaceQuotaExceeded |
"Transaction aborted due to disk space quota exceed. Free up disk space or request increased quota for the schema(s)." |
Redshift.ConnectionsLimitExceeded |
"Connection limit exceeded for user." |
Redshift.SslNotSupported |
"The connection to the specified Amazon Redshift cluster failed because the server does not support SSL. Please check your cluster settings." |
Redshift.HoseNotFound |
"The hose has been deleted. Please check the status of your hose." |
Redshift.Delimiter |
"The copyOptions delimiter in the copyCommand is invalid. Ensure that it is a single character." |
Redshift.QueryCancelled |
"The user has canceled the COPY operation." |
Redshift.CompressionMismatch |
"Hose is configured with UNCOMPRESSED, but copyOption includes a compression format." |
Redshift.EncryptionCredentials |
"The ENCRYPTED option requires credentials in the format: 'aws_iam_role=...;master_symmetric_key=...' or 'aws_access_key_id=...;aws_secret_access_key=...[;token=...];master_symmetric_key=...'" |
Redshift.InvalidCopyOptions |
"Invalid COPY configuration options." |
Redshift.InvalidMessageFormat |
"Copy command contains an invalid character." |
Redshift.TransactionIdLimitReached |
"Transaction ID limit reached." |
Redshift.DestinationRemoved |
"Please verify that the redshift destination exists and is configured correctly in the Firehose configuration." |
Redshift.OutOfMemory |
"The Redshift cluster is running out of memory. Please ensure the cluster has sufficient capacity." |
Redshift.CannotForkProcess |
"The Redshift cluster is running out of memory. Please ensure the cluster has sufficient capacity." |
Redshift.SslFailure |
"The SSL connection closed during the handshake." |
Redshift.Resize |
"The Redshift cluster is resizing. Firehose will not be able to deliver data while the cluster is resizing." |
Redshift.ImproperQualifiedName |
"The qualified name is improper (too many dotted names)." |
Redshift.InvalidJsonPathFormat |
“ JSONPath 格式无效。” |
Redshift.TooManyConnectionsException |
"Too many connections to Redshift." |
Redshift.PSQLException |
“Redsh PSQl ift from Redshift from |
Redshift.DuplicateSecondsSpecification |
"Duplicate seconds specification in date/time format." |
Redshift.RelationCouldNotBeOpened |
"Encountered Redshift error, relation could not be opened. Check Redshift logs for the specified DB." |
Redshift.TooManyClients |
"Encountered too many clients exception from Redshift. Revisit max connections to the database if there are multiple producers writing to it simultaneously." |
Snowflake 数据传输错误
Firehose 可以将以下 Snowflake 相关错误发送到 Logs。 CloudWatch
| 错误代码 | 错误消息和信息 |
|---|---|
Snowflake.InvalidUrl |
"Firehose is unable to connect to Snowflake. Please make sure that Account url is specified correctly in Snowflake destination configuration." |
Snowflake.InvalidUser |
"Firehose is unable to connect to Snowflake. Please make sure that User is specified correctly in Snowflake destination configuration." |
Snowflake.InvalidRole |
"The specified snowflake role does not exist or is not authorized. Please make sure that the role is granted to the user specified" |
Snowflake.InvalidTable |
"The supplied table does not exist or is not authorized" |
Snowflake.InvalidSchema |
"The supplied schema does not exist or is not authorized" |
Snowflake.InvalidDatabase |
"The supplied database does not exist or is not authorized" |
Snowflake.InvalidPrivateKeyOrPassphrase |
"The specified private key or passphrase is not valid. Note that the private key provided should be a valid PEM RSA private key" |
Snowflake.MissingColumns |
"The insert request is rejected due to missing columns in input payload. Make sure that values are specified for all non-nullable columns" |
Snowflake.ExtraColumns |
"The insert request is rejected due to extra columns. Columns not present in table shouldn't be specified" |
Snowflake.InvalidInput |
"Delivery failed due to invalid input format. Make sure that the input payload provided is in the JSON format acceptable" |
Snowflake.IncorrectValue |
"Delivery failed due to incorrect data type in the input payload. Make sure that the JSON values specified in input payload adhere to the datatype declared in Snowflake table definition" |
Splunk 数据传输错误
Amazon Data Firehose 可以将以下 Splunk 相关错误发送到 Logs。 CloudWatch
| 错误代码 | 错误消息和信息 |
|---|---|
Splunk.ProxyWithoutStickySessions |
“If you have a proxy (ELB or other) betweeen the Amazon Data Firehose 和 HEC 节点之间存在问题，则必须启用粘性会话来支持 HEC。” ACKs |
Splunk.DisabledToken |
"The HEC token is disabled。Enable the token to allow data delivery to Splunk." |
Splunk.InvalidToken |
"The HEC token is invalid。Update Amazon Data Firehose with a valid HEC token." |
Splunk.InvalidDataFormat |
"The data is not formatted correctly。To see how to properly format data for Raw or Event HEC endpoints, see Splunk Event Data |
Splunk.InvalidIndex |
"The HEC token or input is configured with an invalid index。Check your index configuration and try again." |
Splunk.ServerError |
"Data delivery to Splunk failed due to a server error from the HEC node. Amazon Data Firehose will retry sending the data if the retry duration in your Amazon Data Firehose is greater than 0. If all the retries fail, Amazon Data Firehose backs up the data to Amazon S3." |
Splunk.DisabledAck |
"Indexer acknowledgement is disabled for the HEC token。Enable indexer acknowledgement and try again。For more info, see Enable indexer acknowledgement |
Splunk.AckTimeout |
"Did not receive an acknowledgement from HEC before the HEC acknowledgement timeout expired。Despite the acknowledgement timeout, it's possible the data was indexed successfully in Splunk. Amazon Data Firehose backs up in Amazon S3 data for which the acknowledgement timeout expired." |
Splunk.MaxRetriesFailed |
"Failed to deliver data to Splunk or to receive acknowledgment。Check your HEC health and try again." |
Splunk.ConnectionTimeout |
"The connection to Splunk timed out。This might be a transient error and the request will be retried. Amazon Data Firehose backs up the data to Amazon S3 if all retries fail." |
Splunk.InvalidEndpoint |
"Could not connect to the HEC endpoint。Make sure that the HEC endpoint URL is valid and reachable from Amazon Data Firehose." |
Splunk.ConnectionClosed |
"Unable to send data to Splunk due to a connection failure。This might be a transient error。Increasing the retry duration in your Amazon Data Firehose configuration might guard against such transient failures." |
Splunk.SSLUnverified |
"Could not connect to the HEC endpoint。主机与对等项提供的证书不匹配。请确保证书和主机是有效的。 |
Splunk.SSLHandshake |
"Could not connect to the HEC endpoint。请确保证书和主机是有效的。 |
Splunk.URLNotFound |
"The requested URL was not found on the Splunk server. Please check the Splunk cluster and make sure it is configured correctly." |
Splunk.ServerError.ContentTooLarge |
"Data delivery to Splunk failed due to a server error with a statusCode: 413, message: the request your client sent was too large. See splunk docs to configure max_content_length." |
Splunk.IndexerBusy |
"Data delivery to Splunk failed due to a server error from the HEC node. Make sure HEC endpoint or the Elastic Load Balancer is reachable and is healthy." |
Splunk.ConnectionRecycled |
"The connection from Firehose to Splunk has been recycled. Delivery will be retried." |
Splunk.AcknowledgementsDisabled |
"Could not get acknowledgements on POST. Make sure that acknowledgements are enabled on HEC endpoint." |
Splunk.InvalidHecResponseCharacter |
"Invalid characters found in HEC response, make sure to check to the service and HEC configuration." |
ElasticSearch 数据传输错误
Amazon Data Firehose 可以将以下 ElasticSearch 错误发送到 CloudWatch Logs。
| 错误代码 | 错误消息和信息 |
|---|---|
ES.AccessDenied |
"Access was denied。Ensure that the provided IAM role associated with firehose is not deleted." |
ES.ResourceNotFound |
“The Amazon specified.” |
HTTPS 端点数据传输错误
Amazon Data Firehose 可以将以下 HTTP 端点相关错误发送到 Logs。 CloudWatch 如果这些错误均与您遇到的问题不匹配，则默认错误如下："An internal error occurred while attempting to deliver data. Delivery will be retried; if the error ported the error res Amazon olution.”
| 错误代码 | 错误消息和信息 |
|---|---|
HttpEndpoint.RequestTimeout |
The delivery timed out before a response was received and will be retried. If this error persists, contact the Amazon Firehose service team. |
HttpEndpoint.ResponseTooLarge |
"The response received from the endpoint is too large. Contact the owner of the endpoint to resolve this issue." |
HttpEndpoint.InvalidResponseFromDestination |
"The response received from the specified endpoint is invalid. Contact the owner of the endpoint to resolve the issue." |
HttpEndpoint.DestinationException |
"The following response was received from the endpoint destination." |
HttpEndpoint.ConnectionFailed |
"Unable to connect to the destination endpoint. Contact the owner of the endpoint to resolve this issue." |
HttpEndpoint.ConnectionReset |
"Unable to maintain connection with the endpoint. Contact the owner of the endpoint to resolve this issue." |
HttpEndpoint.ConnectionReset |
"Trouble maintaining connection with the endpoint. Please reach out to the owner of the endpoint." |
HttpEndpoint.ResponseReasonPhraseExceededLimit |
"The response reason phrase received from the endpoint exceed the configured limit of 64 characters." |
HttpEndpoint.InvalidResponseFromDestination |
"The response received from the endpoint is invalid. See Troubleshooting HTTP Endpoints in the Firehose documentation for more information. Reason: " |
HttpEndpoint.DestinationException |
"Delivery to the endpoint was unsuccessful. See Troubleshooting HTTP Endpoints in the Firehose documentation for more information. Response received with status code " |
HttpEndpoint.InvalidStatusCode |
"Received an invalid response status code." |
HttpEndpoint.SSLHandshakeFailure |
"Unable to complete an SSL Handshake with the endpoint. Contact the owner of the endpoint to resolve this issue." |
HttpEndpoint.SSLHandshakeFailure |
"Unable to complete an SSL Handshake with the endpoint. Contact the owner of the endpoint to resolve this issue." |
HttpEndpoint.SSLFailure |
"Unable to complete TLS handshake with the endpoint. Contact the owner of the endpoint to resolve this issue." |
HttpEndpoint.SSLHandshakeCertificatePathFailure |
"Unable to complete an SSL Handshake with the endpoint due to invalid certification path. Contact the owner of the endpoint to resolve this issue." |
HttpEndpoint.SSLHandshakeCertificatePathValidationFailure |
"Unable to complete an SSL Handshake with the endpoint due to certification path validation failure. Contact the owner of the endpoint to resolve this issue." |
HttpEndpoint.MakeRequestFailure.IllegalUriException |
“HttpEndpoint 请求失败，原因是 URI 中的输入错误。Please make sure all the characters in the input URI are valid." |
HttpEndpoint.MakeRequestFailure.IllegalCharacterInHeaderValue |
“HttpEndpoint 请求失败，原因是非法响应错误。Illegal character '\n' in header value." |
HttpEndpoint.IllegalResponseFailure |
“HttpEndpoint 请求失败，原因是非法响应错误。HTTP message must not contain more than one Content-Type header." |
HttpEndpoint.IllegalMessageStart |
“HttpEndpoint 请求失败，原因是非法响应错误。Illegal HTTP message start. See Troubleshooting HTTP Endpoints in the Firehose documentation for more information." |
Amazon S OpenSearch ervice 数据传输错误
对于 OpenSearch 服务目标，Amazon Data Firehose 在服务返回错误时，将错误发送到 CloudWatch Logs。 OpenSearch
除 OpenSearch 集群可能返回的错误外，您还可能遇到以下两种错误：
-
Authentication/authorization error occurs during attempt to deliver data to destination OpenSearch Service cluster. This can happen due to any permission issues and/or您的 Amazon Data Firehose 目标 OpenSearch 服务域配置被修改时，间歇性的存在问题。Please check the cluster policy and role permissions.
-
您的 Amazon Data Firehose 目标 OpenSearch 服务域authentication/authorization failures. This can happen due to any permission issues and/or配置发生问题，导致无法将数据传送至目标 OpenSearch 服务集群。Please check the cluster policy and role permissions.
| 错误代码 | 错误消息和信息 |
|---|---|
OS.AccessDenied |
"Access was denied。Ensure policy the the the the the the the the firehose policy the firehose 代入角色，并且访问策略允许访问亚马逊 OpenSearch 服务 API。” |
OS.AccessDenied |
"Access was denied。Ensure policy the the the the the the the the firehose policy the firehose 代入角色，并且访问策略允许访问亚马逊 OpenSearch 服务 API。” |
OS.AccessDenied |
"Access was denied。Ensure that the provided IAM role associated with firehose is not deleted." |
OS.AccessDenied |
"Access was denied。Ensure that the provided IAM role associated with firehose is not deleted." |
OS.ResourceNotFound |
“The specified Amazon OpenSearch 服务域不存在。” |
OS.ResourceNotFound |
“The specified Amazon OpenSearch 服务域不存在。” |
OS.AccessDenied |
"Access was denied。Ensure policy the the the the the the the the firehose policy the firehose 代入角色，并且访问策略允许访问亚马逊 OpenSearch 服务 API。” |
OS.RequestTimeout |
“Requ OpenSearch est to to to to to the Amazon Serv OpenSearch ice cluster Ensure that the cluster or collection has sufficient capacity for the current workload." |
OS.ClusterError |
“Amazon S OpenSearch ervice 集群返回了一个未指明错误。” |
OS.RequestTimeout |
“Request the s OpenSearch ervice 集群请求超时。Ensure that the cluster has sufficient capacity for the current workload." |
OS.ConnectionFailed |
“Trouble connecting to t OpenSearch rouble connect OpenSearch ing to to Ensure that the cluster or collection is healthy and reachable." |
OS.ConnectionReset |
“无法与 Amazon Serv OpenSearch ice cluster or OpenSearch Serverless collection Contact the owner of the cluster or collection to resolve this issue." |
OS.ConnectionReset |
“The Amazon Serv OpenSearch ice cluster or OpenSearch Serverless collec Ensure that the cluster or collection is healthy and has sufficient capacity for the current workload." |
OS.ConnectionReset |
“The Amazon Serv OpenSearch ice cluster or OpenSearch Serverless collec Ensure that the cluster or collection is healthy and has sufficient capacity for the current workload." |
OS.AccessDenied |
"Access was denied。Ensure that the Amazon S OpenSearch ervice cluster the Amazon Service clu |
OS.ValidationException |
“集 OpenSearch 群返回 ESService异常。原因之一是，集群已升级到 OS 2.x 或更高版本，但软管仍配置 TypeName 参数。通过将设置为空字符串 TypeName 来更新软管配置，或者将端点更改为支持 Type 参数的集群。” |
OS.ValidationException |
"Member must satisfy regular expression pattern: [a-z][a-z0-9\\-]+ |
OS.JsonParseException |
“亚马逊 OpenSearch 服务集群返回了 JsonParseException. Ensure that the data being put is valid." |
OS.AmazonOpenSearchServiceParseException |
“亚马逊 OpenSearch 服务集群返回了 AmazonOpenSearchServiceParseException. Ensure that the data being put is valid." |
OS.ExplicitIndexInBulkNotAllowed |
“Ensure rest.action.multi.allow_explicit_index is sexplicit_index is is set OpenSearch |
OS.ClusterError |
“The Amazon Serv OpenSearch ice cluster or OpenSearch Serverless collection s |
OS.ClusterBlockException |
“集群返回了 ClusterBlockException. It may be overloaded." |
OS.InvalidARN |
“The specifie OpenSearch d Amazon Service ARN filed. Please 检查 DeliveryStream 配置。” |
OS.MalformedData |
"One or more records are malformed. Please ensure that each record is single valid JSON object and that it does not contain newlines." |
OS.InternalError |
"An internal error occurred when attempting to deliver data. Delivery will be retried; it will be retried; it will Amazon be retried |
OS.AliasWithMultipleIndicesNotAllowed |
"Alias has more than one indices associated with it. Ensure that the alias has only one index associated with it." |
OS.UnsupportedVersion |
“Amazon Data Firehose 目前不支持亚马逊S OpenSearch ervice 6.0 is not supported by Contac Amazon t Support 了解更多详情。” |
OS.CharConversionException |
"One or more records contained an invalid character." |
OS.InvalidDomainNameLength |
"The domain name length is not within valid OS limits." |
OS.VPCDomainNotSupported |
“目前不支持其中的 VPCs Amazon S OpenSearch ervice domains will be |
OS.ConnectionError |
“http 服务器意外关闭了连接，请验证 Amazon Serv OpenSearch ice cluster or OpenSearch Serverless collection 的运行状况。” |
OS.LargeFieldData |
“The Amazon S OpenSearch ervice cluster aborted the request the request with a |
OS.BadGateway |
“The Amazon Serv OpenSearch ice cluster o OpenSearch r Serverless collection aborted the request abor |
OS.ServiceException |
“Error the Amazon Serv OpenSearch ice cluster or OpenSearch service If the cluster or collection is behind a VPC, ensure network configuration allows connectivity." |
OS.GatewayTimeout |
“Firehose 在连接亚马逊 OpenSearch 服务集群或 OpenSearch Serverless collection 时遇到了超时错误。” |
OS.MalformedData |
“Amazon Data Firehose 不支持 Firehose rehose record 中的亚马逊 OpenSearch 服务批量 API 命令。” |
OS.ResponseEntryCountMismatch |
"The response from the Bulk API contained more entries than the number of records sent. Ensure that each record contains only one JSON object and that there are no newlines." |
Lambda 调用错误
Amazon Data Firehose 可以将以下 Lambda 调用错误发送到 Logs。 CloudWatch
| 错误代码 | 错误消息和信息 |
|---|---|
Lambda.AssumeRoleAccessDenied |
"Access was denied。Ensure that the trust policy for the provided IAM role allows Amazon Data Firehose to assume the role." |
Lambda.InvokeAccessDenied |
"Access was denied。Ensure that the access policy allows access to the Lambda function." |
Lambda.JsonProcessingException |
"There was an error parsing returned records from the Lambda function. Ensure that the returned records follow the status model required by Amazon Data Firehose." 有关更多信息，请参阅 数据转换所需的参数。 |
Lambda.InvokeLimitExceeded |
"The Lambda concurrent execution limit is exceeded. Increase the concurrent execution limit." 有关更多信息，请参阅《Amazon Lambda 开发人员指南》中的 Amazon Lambda 限制。 |
Lambda.DuplicatedRecordId |
"Multiple records were returned with the same record ID。Ensure that the Lambda function retur IDs ns returns 有关更多信息，请参阅 数据转换所需的参数。 |
Lambda.MissingRecordId |
“没有返回一条或 IDs 多条记录。Ensure the Lambda function returns returns IDs 有关更多信息，请参阅 数据转换所需的参数。 |
Lambda.ResourceNotFound |
"The specified Lambda function does not exist. Use a different function that does exist." |
Lambda.InvalidSubnetIDException |
"The specified subnet ID in the Lambda function VPC configuration is invalid. Ensure that the subnet ID is valid." |
Lambda.InvalidSecurityGroupIDException |
"The specified security group ID in the Lambda function VPC configuration is invalid. Ensure that the security group ID is valid." |
Lambda.SubnetIPAddressLimitReachedException |
“Amazon Lambda 由于配置的一个或多个子网没有可用的 IP 地址，因此无法为 Lambda 函数设置 VPC 访问。Increase the IP address limit." 有关更多信息，请参阅《Amazon VPC 用户指南》中的 Amazon VPC 限制：VPC 和子网。 |
Lambda.ENILimitReachedException |
“Amazon Lambda 由于已达到网络接口限制，因此无法在 VPC 中创建指定为 Lambda 函数配置的一部分的弹性网络接口 (ENI)，因为已达到网络接口限制。Increase the network interface limit." 有关更多信息，请参阅《Amazon VPC 用户指南》中的 Amazon VPC 限制：网络接口。 |
|
|
The Lambda function invocation timed out. Increase the Timeout setting in the Lambda function. 有关更多信息，请参阅配置函数超时。 |
|
|
This can be due to any of the following errors:
|
|
|
Amazon Data Firehose encountered Request did not complete before the request timeout configuration error when invoking Lambda. Revisit the Lambda code to check if the Lambda code is meant to run beyond the configured timeout. If so, consider tuning Lambda configuration settings, including memory, timeout. 有关更多信息，请参阅配置 Lambda 函数选项。 |
|
|
Amazon Data Firehose encountered an error. 调用 Amazon Lambda service 时，目标服务器未能响应错误。 |
|
|
Amazon Data Firehose encountered the Lambda 函数 InvalidZipFileException时，即针对该函数遇到了。Check your Lambda function configuration settings and the Lambda code zip file. |
|
|
“Amazon Data Firehose encountered calling Lambda Amazon service InternalServerError 时，Amazon Data Firehose will retry sending data a fixed number of times. 您可以使用或指定或覆盖重试选项。 |
|
|
Amazon Data Firehose encountered th ServiceUnavailableException e Lambda Amazon service. Amazon Data Firehose will retry sending data a fixed number of times. 您可以使用或指定或覆盖重试选项。 |
|
|
Cannot invoke Lambda function due to invalid security token. Cross partition Lambda invocation is not supported. |
Lambda.InvocationFailure
|
This can be due to any of the following errors:
|
|
|
There was an error parsing returned records from the Lambda function. Ensure that data field is base-64 encoded. |
Kinesis 调用错误
Amazon Data Firehose 可以将以下 Kinesis 调用错误发送到 Logs。 CloudWatch
| 错误代码 | 错误消息和信息 |
|---|---|
Kinesis.AccessDenied |
"Access was denied when calling Kinesis. Ensure the access policy the IAM role 的访问策略允许访问相应的 Kinesis APIs。” |
Kinesis.ResourceNotFound |
"Firehose failed to read from the stream. If the Firehose is attached with Kinesis Stream, the stream may not exist, or the shard may have been merged or split. If you the Firehose is o DirectPut f type, Firehose 可能不再存在了。” |
Kinesis.SubscriptionRequired |
"Access was denied when calling Kinesis. Ensure the IAM ropersis the IAM ropersis for Kinesis subsc Amazon rist |
Kinesis.Throttling |
"Throttling error encountered when calling Kinesis. 这可能是由于其他应用程序调用了 Firehose 流的 APIs 相同操作，或者您创建的 Firehose 流与源流相同 Firehose 流的 Firehose 流太多。” |
Kinesis.Throttling |
"Throttling error encountered when calling Kinesis. 这可能是由于其他应用程序调用了 Firehose 流的 APIs 相同操作，或者您创建的 Firehose 流与源流相同 Firehose 流的 Firehose 流太多。” |
Kinesis.AccessDenied |
"Access was denied when calling Kinesis. Ensure the access policy the IAM role 的访问策略允许访问相应的 Kinesis APIs。” |
Kinesis.AccessDenied |
"Access was denied while trying to call API operations on the underlying Kinesis Stream. Ensure that the IAM role is propagated and valid." |
Kinesis.KMS.AccessDeniedException |
"Firehose does not have access to the KMS Key used to encrypt/decrypt the Kinesis Stream. Please grant the Firehose delivery role access to the key." |
Kinesis.KMS.KeyDisabled |
"Firehose is unable to read from the source Kinesis Stream because the KMS key used to encrypt/decrypt it is disabled. Enable the key so that reads can proceed." |
Kinesis.KMS.InvalidStateException |
"Firehose is unable to read from the source Kinesis Stream because the KMS key used to encrypt it is in an invalid state." |
Kinesis.KMS.NotFoundException |
"Firehose is unable to read from the source Kinesis Stream because the KMS key used to encrypt it was not found." |
Kinesis 调 DirectPut 用错误
Amazon Data Firehose 可以将以下 Kinesis DirectPut 调用错误发送到 Logs。 CloudWatch
| 错误代码 | 错误消息和信息 |
|---|---|
Firehose.KMS.AccessDeniedException |
"Firehose does not have access to the KMS Key. Please check the key policy." |
Firehose.KMS.InvalidStateException |
"Firehose is unable to decrypt the data because the KMS key used to encrypt it is in an invalid state." |
Firehose.KMS.NotFoundException |
"Firehose is unable to decrypt the data because the KMS key used to encrypt it was not found." |
Firehose.KMS.KeyDisabled |
"Firehose is unable to decrypt the data because the KMS key used to encrypt the data is disabled. Enable the key so that data delivery can proceed." |
Amazon Glue 调用错误
Amazon Data Firehose 可以将以下 Amazon Glue 调用错误发送到 Logs。 CloudWatch
| 错误代码 | 错误消息和信息 |
|---|---|
DataFormatConversion.InvalidSchema |
"The schema is invalid." |
DataFormatConversion.EntityNotFound |
“指定的table/database could not be found. Please ensure that the table/database存在问题，并且架构配置中提供的值是正确的，尤其是在大小写方面。” |
DataFormatConversion.InvalidInput |
"Could not find a matching schema from glue. Please make sure the specified database with the supplied catalog ID exists." |
DataFormatConversion.InvalidInput |
"Could not find a matching schema from glue. Please make sure the passed ARN is in the correct format." |
DataFormatConversion.InvalidInput |
"Could not find a matching schema from glue. Please make sure the catalogId provided is valid." |
DataFormatConversion.InvalidVersionId |
"Could not find a matching schema from glue. Please make sure the specified version of the table exists." |
DataFormatConversion.NonExistentColumns |
"Could not find a matching schema from glue. Please make sure the table is configured with a non-null storage descriptor containing the target columns." |
DataFormatConversion.AccessDenied |
"Access was denied when assuming role. Please ensure that the role specified in the data format conversion configuration has granted the Firehose service permission to assume it." |
DataFormatConversion.ThrottledByGlue |
"Throttling error encountered when calling Glue. Either increase the request rate limit or reduce the current rate of calling glue through other applications." |
DataFormatConversion.AccessDenied |
"Access was denied when calling Glue. Please ensure that the role specified in the data format conversion configuration has the necessary permissions." |
DataFormatConversion.InvalidGlueRole |
"Invalid role. Please ensure that the role specified in the data format conversion configuration exists." |
DataFormatConversion.InvalidGlueRole |
"The security token included in the request is invalid. Ensure that the provided IAM role associated with firehose is not deleted." |
DataFormatConversion.GlueNotAvailableInRegion |
“Amazon Glue is not you have specified; please specified a different |
DataFormatConversion.GlueEncryptionException |
"There was an error retrieving the master key. Ensure that the key exists and has the correct access permissions." |
DataFormatConversion.SchemaValidationTimeout |
"Timed out while retrieving table from Glue. If you have a large number of Glue table versists，请添加'glue: GetTableVersion 'permissists (recommm If you do not have large number of tables in Glue, ple Amazon ase cont |
DataFirehose.InternalError |
"Timed out while retrieving table from Glue. If you have a large number of Glue table versists，请添加'glue: GetTableVersion 'permissists (recommm If you do not have large number of tables in Glue, ple Amazon ase cont |
DataFormatConversion.GlueEncryptionException |
"There was an error retrieving the master key. Ensure that the key exists and state is correct." |
DataFormatConversion 调用错误
Amazon Data Firehose 可以将以下 DataFormatConversion 调用错误发送到 Logs。 CloudWatch
| 错误代码 | 错误消息和信息 |
|---|---|
DataFormatConversion.InvalidSchema |
"The schema is invalid." |
DataFormatConversion.ValidationException |
"Column names and types must be non-empty strings." |
DataFormatConversion.ParseError |
"Encountered malformed JSON." |
DataFormatConversion.MalformedData |
"Data does not match the schema." |
DataFormatConversion.MalformedData |
"Length of json key must not be greater than 262144" |
DataFormatConversion.MalformedData |
"The data cannot be decoded as UTF-8." |
DataFormatConversion.MalformedData |
"Illegal character found between tokens." |
DataFormatConversion.InvalidTypeFormat |
"The type format is invalid. Check the type syntax." |
DataFormatConversion.InvalidSchema |
"Invalid Schema. Please ensure that there are no special characters or white spaces in column names." |
DataFormatConversion.InvalidRecord |
"Record is not as per schema. One or more map keys were invalid for map<string,string>." |
DataFormatConversion.MalformedData |
"The input JSON contained a primitive at the top level. The top level must be an object or array." |
DataFormatConversion.MalformedData |
"The input JSON contained a primitive at the top level. The top level must be an object or array." |
DataFormatConversion.MalformedData |
"The record was empty or contained only whitespace." |
DataFormatConversion.MalformedData |
"Encountered invalid characters." |
DataFormatConversion.MalformedData |
"Encountered invalid or unsupported timestamp format. Please see the Firehose developer guide for supported timestamp formats." |
DataFormatConversion.MalformedData |
"A scalar type was found in the data but a complex type was specified on the schema." |
DataFormatConversion.MalformedData |
"Data does not match the schema." |
DataFormatConversion.MalformedData |
"A scalar type was found in the data but a complex type was specified on the schema." |
DataFormatConversion.ConversionFailureException |
"ConversionFailureException" |
DataFormatConversion.DataFormatConversionCustomerErrorException |
"DataFormatConversionCustomerErrorException" |
DataFormatConversion.DataFormatConversionCustomerErrorException |
"DataFormatConversionCustomerErrorException" |
DataFormatConversion.MalformedData |
"Data does not match the schema." |
DataFormatConversion.InvalidSchema |
"The schema is invalid." |
DataFormatConversion.MalformedData |
"Data does not match the schema. Invalid format for one or more dates." |
DataFormatConversion.MalformedData |
"Data contains a highly nested JSON structure that is not supported." |
DataFormatConversion.EntityNotFound |
“指定的table/database could not be found. Please ensure that the table/database存在问题，并且架构配置中提供的值是正确的，尤其是在大小写方面。” |
DataFormatConversion.InvalidInput |
"Could not find a matching schema from glue. Please make sure the specified database with the supplied catalog ID exists." |
DataFormatConversion.InvalidInput |
"Could not find a matching schema from glue. Please make sure the passed ARN is in the correct format." |
DataFormatConversion.InvalidInput |
"Could not find a matching schema from glue. Please make sure the catalogId provided is valid." |
DataFormatConversion.InvalidVersionId |
"Could not find a matching schema from glue. Please make sure the specified version of the table exists." |
DataFormatConversion.NonExistentColumns |
"Could not find a matching schema from glue. Please make sure the table is configured with a non-null storage descriptor containing the target columns." |
DataFormatConversion.AccessDenied |
"Access was denied when assuming role. Please ensure that the role specified in the data format conversion configuration has granted the Firehose service permission to assume it." |
DataFormatConversion.ThrottledByGlue |
"Throttling error encountered when calling Glue. Either increase the request rate limit or reduce the current rate of calling glue through other applications." |
DataFormatConversion.AccessDenied |
"Access was denied when calling Glue. Please ensure that the role specified in the data format conversion configuration has the necessary permissions." |
DataFormatConversion.InvalidGlueRole |
"Invalid role. Please ensure that the role specified in the data format conversion configuration exists." |
DataFormatConversion.GlueNotAvailableInRegion |
“Amazon Glue is not you have specified; please specified a different |
DataFormatConversion.GlueEncryptionException |
"There was an error retrieving the master key. Ensure that the key exists and has the correct access permissions." |
DataFormatConversion.SchemaValidationTimeout |
"Timed out while retrieving table from Glue. If you have a large number of Glue table versists，请添加'glue: GetTableVersion 'permissists (recommm If you do not have large number of tables in Glue, ple Amazon ase cont |
DataFirehose.InternalError |
"Timed out while retrieving table from Glue. If you have a large number of Glue table versists，请添加'glue: GetTableVersion 'permissists (recommm If you do not have large number of tables in Glue, ple Amazon ase cont |
DataFormatConversion.MalformedData |
"One or more fields have incorrect format." |