亚马逊 Data Firehose 以前被称为亚马逊 Kinesis Data Firehose
本文属于机器翻译版本。若本译文内容与英语原文存在差异，则一律以英文原文为准。
使用日志监控亚马逊数据 Firehose CloudWatch
Amazon Data Firehose 与亚马逊 CloudWatch 日志集成，因此当用于数据转换或数据传输的 Lambda 调用失败时，您可以查看特定的错误日志。在创建 Firehose 直播时，你可以启用 Amazon Data Firehose 错误日志记录。
如果您在亚马逊数据 Firehose 控制台中启用 Amazon Data Firehose 错误记录，则会代表您为 Firehose 流创建日志组和相应的日志流。日志组名称的格式为/aws/kinesisfirehose/，其中delivery-stream-namedelivery-stream-nameDestinationDelivery是创建的日志流，用于记录与传送到主要目标相关的所有错误。只有在为目标启用了 S3 备份时，才会创建另一个名为 BackupDelivery 的日志流。BackupDelivery 日志流用于记录与传输到 S3 备份相关的任何错误。
例如，如果您创建了一个以 Amazon Redshift 为目标的 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 日志。在交付失败率很高的情况下，Amazon Data Firehose 会先对传送错误日志进行采样，然后再将其发送到 CloudWatch 日志。
发送到 CloudWatch Logs 的错误日志会收取象征性的费用。有关更多信息，请参阅 Amazon CloudWatch 定价
内容
数据传输错误
以下是每个 Amazon Data Firehose 目标的数据传输错误代码和消息列表。每个错误消息还描述了修复问题所应采取的适当操作。
错误
Amazon S3 数据传输错误
Amazon Data Firehose 可以将以下与亚马逊 S3 相关的错误发送到日志。 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。确保所提供的 IAM 角色的信任策略允许 Amazon Data Firehose 担任该角色，并且访问策略允许访问 S3 存储桶。” |
S3.AccountProblem |
“您的 Amazon 账户存在问题，导致操作无法成功完成。Contact Amazon Support." |
S3.AllAccessDisabled |
"Access to the account provided has been disabled。请联系 S Amazon upport。” |
S3.InvalidPayer |
"Access to the account provided has been disabled。请联系 S Amazon upport。” |
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。将重试交付；如果错误仍然存在，则会将其报告给以 Amazon 寻求解决。” |
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. 增加 Firehose 流缓冲区的大小或减少来自其他应用程序的 put 请求。” |
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. 配置您的 KMS MasterKey ID，或者禁用 S3 存储桶的加密。” |
S3.KMS.AsymmetricCMKNotSupported |
"Amazon S3 supports only symmetric 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. 请在与 s3 存储桶相同的区域创建 Firehose 流，或者在支持全局终端节点的区域中使用 s3 存储桶。” |
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." |
Amazon Redshift 数据传输错误
Amazon Data Firehose 可以将以下与亚马逊 Redshift 相关的错误发送到日志。 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. 请注意，如果亚马逊 Redshift 表不存在，则亚马逊 Data Firehose 不会创建该表。 |
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。确保所提供的 IAM 角色的信任策略允许 Amazon Data Firehose 担任该角色。” |
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. 确保安全设置允许 Amazon Data Firehose 连接，确保在 Amazon Redshift 目标配置或 JDBC URL 中指定的集群或数据库正确，并且集群可用。” |
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。将重试交付；如果错误仍然存在，则会将其报告给以 Amazon 寻求解决。” |
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 |
“找不到在 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 with error \"Invalid JSONPath format. Array index is out of range\". Please rectify the JSONPath expression." |
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 |
"Invalid JSONPath Format." |
Redshift.TooManyConnectionsException |
"Too many connections to Redshift." |
Redshift.PSQLException |
“PS 从 Redshift 中QlException 观察到。” |
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 相关的错误发送到日志。 CloudWatch
| 错误代码 | 错误消息和信息 |
|---|---|
Snowflake.InvalidUrl |
“Firehose 无法连接到 Snowflake。请确保在 Snowflake 目标配置中正确指定了账户网址。” |
Snowflake.InvalidUser |
“Firehose 无法连接到 Snowflake。请确保在 Snowflake 目标配置中正确指定了用户。” |
Snowflake.InvalidRole |
“指定的雪花角色不存在或未获得授权。请确保该角色已授予指定的用户” |
Snowflake.InvalidTable |
“提供的表不存在或未经授权” |
Snowflake.InvalidSchema |
“提供的架构不存在或未经授权” |
Snowflake.InvalidDatabase |
“提供的数据库不存在或未经授权” |
Snowflake.InvalidPrivateKeyOrPassphrase |
“指定的私钥或密码无效。请注意，提供的私钥应该是有效的 PEM RSA 私钥” |
Snowflake.MissingColumns |
“由于输入有效载荷中缺少列，插入请求被拒绝。确保为所有不可为空的列都指定了值” |
Snowflake.ExtraColumns |
“由于列数过多，插入请求被拒绝。不应指定表中不存在的列” |
Snowflake.InvalidInput |
“由于输入格式无效，交付失败。确保提供的输入有效载荷采用可接受的 JSON 格式” |
Snowflake.IncorrectValue |
“由于输入有效载荷中的数据类型不正确，交付失败。确保输入负载中指定的 JSON 值符合 Snowflake 表定义中声明的数据类型” |
Splunk 数据传输错误
Amazon Data Firehose 可以将以下与 Splunk 相关的错误发送到日志。 CloudWatch
| 错误代码 | 错误消息和信息 |
|---|---|
Splunk.ProxyWithoutStickySessions |
“如果您在 Amazon Data Firehose 和 HEC 节点之间有代理（ELB 或其他），则必须启用粘性会话才能支持 HEC ACK。” |
Splunk.DisabledToken |
"The HEC token is disabled。Enable the token to allow data delivery to Splunk." |
Splunk.InvalidToken |
"The HEC token is invalid。使用有效的 HEC 令牌更新 Amazon Data Firehose。” |
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. 如果您的亚马逊数据 Firehose 中的重试持续时间大于 0，Amazon Data Firehose 将重试发送数据。如果所有重试都失败，Amazon Data Firehose 会将数据备份到亚马逊 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 在确认超时已过期的亚马逊 S3 数据中进行备份。” |
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 会将数据备份到亚马逊 S3。” |
Splunk.InvalidEndpoint |
"Could not connect to the HEC endpoint。确保 HEC 终端节点网址有效且可通过 Amazon Data Firehose 访问。” |
Splunk.ConnectionClosed |
"Unable to send data to Splunk due to a connection failure。This might be a transient error。在您的 Amazon Data Firehose 配置中增加重试持续时间可以防止此类暂时失败。” |
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 日志。
| 错误代码 | 错误消息和信息 |
|---|---|
ES.AccessDenied |
"Access was denied。Ensure that the provided IAM role associated with firehose is not deleted." |
ES.ResourceNotFound |
“指定的 Amazon Elasticsearch 域不存在。” |
HTTPS 端点数据传输错误
Amazon Data Firehose 可以将以下与 HTTP 端点相关的错误发送到日志。 CloudWatch 如果这些错误均与您遇到的问题不匹配，则默认错误如下："An internal error occurred while attempting to deliver data. 将重试交付；如果错误仍然存在，则会将其报告给以 Amazon 寻求解决。”
| 错误代码 | 错误消息和信息 |
|---|---|
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 |
“由于 URI 中的输入无效，HttpEndpoint 请求失败。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." |
亚马逊 OpenSearch 服务数据传送错误
对于 OpenSearch 服务目标，Amazon Data Firehose 会在服务返回错误时向 CloudWatch 日志发送错误。 OpenSearch
除了可能从 OpenSearch 集群返回的错误外，您还可能遇到以下两个错误：
-
尝试向目标 OpenSearch 服务群集传送数据时发生身份验证/授权错误。这可能是由于任何权限问题和/或当您的 Amazon Data Firehose 目标 OpenSearch 服务域配置被修改时出现间歇性的。Please check the cluster policy and role permissions.
-
由于身份验证/授权失败，无法将数据传送到目标 OpenSearch 服务集群。这可能是由于任何权限问题和/或当您的 Amazon Data Firehose 目标 OpenSearch 服务域配置被修改时出现间歇性的。Please check the cluster policy and role permissions.
| 错误代码 | 错误消息和信息 |
|---|---|
OS.AccessDenied |
"Access was denied。确保所提供的 IAM 角色的信任策略允许 Firehose 担任该角色，并且访问策略允许访问亚马逊 OpenSearch 服务 API。” |
OS.AccessDenied |
"Access was denied。确保所提供的 IAM 角色的信任策略允许 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 |
“指定的亚马逊 OpenSearch 服务域不存在。” |
OS.ResourceNotFound |
“指定的亚马逊 OpenSearch 服务域不存在。” |
OS.AccessDenied |
"Access was denied。确保所提供的 IAM 角色的信任策略允许 Firehose 担任该角色，并且访问策略允许访问亚马逊 OpenSearch 服务 API。” |
OS.RequestTimeout |
“对 Amazon Serv OpenSearch ice 集群或 OpenSearch 无服务器集合的请求超时。Ensure that the cluster or collection has sufficient capacity for the current workload." |
OS.ClusterError |
“Amazon OpenSearch 服务集群返回了一个未指明的错误。” |
OS.RequestTimeout |
“对 Amazon OpenSearch 服务集群的请求超时。Ensure that the cluster has sufficient capacity for the current workload." |
OS.ConnectionFailed |
“连接到 Amazon OpenSearch 服务集群或 OpenSearch 无服务器集合时出现问题。Ensure that the cluster or collection is healthy and reachable." |
OS.ConnectionReset |
“无法与亚马逊 OpenSearch 服务集群或 OpenSearch 无服务器集合保持连接。Contact the owner of the cluster or collection to resolve this issue." |
OS.ConnectionReset |
“无法与 Amazon OpenSearch 服务集群或 OpenSearch 无服务器集合保持连接。Ensure that the cluster or collection is healthy and has sufficient capacity for the current workload." |
OS.ConnectionReset |
“无法与 Amazon OpenSearch 服务集群或 OpenSearch 无服务器集合保持连接。Ensure that the cluster or collection is healthy and has sufficient capacity for the current workload." |
OS.AccessDenied |
"Access was denied。确保 Amazon S OpenSearch ervice 集群上的访问策略授予对已配置的 IAM 角色的访问权限。” |
OS.ValidationException |
“集 OpenSearch 群返回了一个 ES ServiceException。原因之一是集群已升级到操作系统 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 |
“确保在亚马逊服务集群上将 rest.action.multi.allow_explicit_index 设置为 true。” OpenSearch |
OS.ClusterError |
“Amazon Serv OpenSearch ice 集群或 OpenSearch 无服务器集合返回了一个未指明的错误。” |
OS.ClusterBlockException |
“集群返回了 ClusterBlockException. It may be overloaded." |
OS.InvalidARN |
“提供的亚马逊 OpenSearch 服务 ARN 无效。请检查您的 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. 将重试交付；如果错误仍然存在，则会将其报告给以 Amazon 寻求解决。” |
OS.AliasWithMultipleIndicesNotAllowed |
"Alias has more than one indices associated with it. Ensure that the alias has only one index associated with it." |
OS.UnsupportedVersion |
“亚马逊 Data Firehose 目前不支持亚马逊 OpenSearch 服务 6.0。如需更多信息，请联系 Amazon 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 |
“目前不支持 VPC 内的亚马逊 OpenSearch 服务域。” |
OS.ConnectionError |
“http 服务器意外关闭了连接，请验证亚马逊 OpenSearch 服务集群或 OpenSearch 无服务器集合的运行状况。” |
OS.LargeFieldData |
“Amazon S OpenSearch ervice 集群中止了请求，因为它包含的字段数据大于允许值。” |
OS.BadGateway |
“Amazon Serv OpenSearch ice 集群或 OpenSearch 无服务器集合中止了请求，结果是：502 Bad Gateway。” |
OS.ServiceException |
“从 Amazon OpenSearch 服务集群或 OpenSearch 无服务器集合收到错误。If the cluster or collection is behind a VPC, ensure network configuration allows connectivity." |
OS.GatewayTimeout |
“Firehose 在连接到亚马逊 OpenSearch 服务集群或 OpenSearch 无服务器集合时遇到了超时错误。” |
OS.MalformedData |
“亚马逊数据 Firehose 不支持 Firehose 记录中的亚马逊 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 调用错误发送到日志。 CloudWatch
| 错误代码 | 错误消息和信息 |
|---|---|
Lambda.AssumeRoleAccessDenied |
"Access was denied。确保所提供的 IAM 角色的信任策略允许 Amazon Data Firehose 担任该角色。” |
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. 确保返回的记录符合 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 returns unique record IDs for each record." 有关更多信息，请参阅 数据转换和状态模型。 |
Lambda.MissingRecordId |
"One or more record IDs were not returned。Ensure that the Lambda function returns all received record 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 为 Lambda 函数设置 VPC 访问权限，因为一个或多个已配置的子网没有可用的 IP 地址。Increase the IP address limit." 有关更多信息，请参阅《Amazon VPC 用户指南》中的 Amazon VPC 限制：VPC 和子网。 |
Lambda.ENILimitReachedException |
“Amazon Lambda 由于已达到网络接口的限制，无法在 Lambda 函数配置中指定的 VPC 中创建弹性网络接口 (ENI)。Increase the network interface limit." 有关更多信息，请参阅《Amazon VPC 用户指南》中的 Amazon VPC 限制：网络接口。 |
|
Lambda。 FunctionTimedOut |
The Lambda function invocation timed out. Increase the Timeout setting in the Lambda function. 有关更多信息，请参阅配置函数超时。 |
|
Lambda。 FunctionError |
This can be due to any of the following errors:
|
|
Lambda。 FunctionRequestTimedOut |
Amazon Data Firehose 在调用 Lambda 时遇到请求未完成之前出现请求超时配置错误。Revisit the Lambda code to check if the Lambda code is menat to run beyond the configured timeout. If so, consider tuning Lambda configuration settings, including memory, timeout. 有关更多信息，请参阅配置 Lambda 函数选项。 |
|
Lambda。 TargetServerFailedToRespond |
Amazon Data Firehose 遇到了错误。目标服务器在调用 Amazon Lambda 服务时未能响应错误。 |
|
Lambda。 InvalidZipFileException |
Amazon Data Firehose InvalidZipFileException 在调用 Lambda 函数时遇到了问题。Check your Lambda function configuration settings and the Lambda code zip file. |
|
Lambda。 InternalServerError |
“Firehose 在调用 Lambda 服务 InternalServerError时遇到了亚马逊 D Amazon ata Firehose。Amazon Data Firehose 将按固定次数重试发送数据。You can specify or override the retry options using the |
|
Lambda。 ServiceUnavailable |
Amazon Data Firehose ServiceUnavailableException 在调用 Lambda Amazon 服务时遇到了问题。Amazon Data Firehose 将按固定次数重试发送数据。You can specify or override the retry options using the |
|
Lambda。 InvalidSecurityToken |
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:
|
|
Lambda。 JsonMappingException |
There was an error parsing returned records from the Lambda function. Ensure that data field is base-64 encoded. |
Kinesis 调用错误
Amazon Data Firehose 可以将以下 Kinesis 调用错误发送到日志。 CloudWatch
| 错误代码 | 错误消息和信息 |
|---|---|
Kinesis.AccessDenied |
"Access was denied when calling Kinesis. Ensure the access policy on the IAM role used allows access to the appropriate 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. 如果 Firehose 是 DirectPut 这种类型，那么 Firehose 可能已经不存在了。” |
Kinesis.SubscriptionRequired |
"Access was denied when calling Kinesis. 确保为访问 Kinesis 直播而传递的 IAM 角色已订阅 Kinesis Amazon 。” |
Kinesis.Throttling |
"Throttling error encountered when calling Kinesis. 这可能是由于其他应用程序调用了与 Firehose 直播相同的 API，也可能是因为你创建了太多 Firehose 直播与源相同的 Kinesis 流。” |
Kinesis.Throttling |
"Throttling error encountered when calling Kinesis. 这可能是由于其他应用程序调用了与 Firehose 直播相同的 API，也可能是因为你创建了太多 Firehose 直播与源相同的 Kinesis 流。” |
Kinesis.AccessDenied |
"Access was denied when calling Kinesis. Ensure the access policy on the IAM role used allows access to the appropriate Kinesis APIs." |
Kinesis.AccessDenied |
"Access was denied while trying to call apis 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 调用错误发送到日志。 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 调用错误发送到日志。 CloudWatch
| 错误代码 | 错误消息和信息 |
|---|---|
DataFormatConversion.InvalidSchema |
"The schema is invalid." |
DataFormatConversion.EntityNotFound |
"The specified table/database could not be found. Please ensure that the table/database exists and that the values provided in the schema configuration are correct, especially with regards to casing." |
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 在您指定的区域尚不可用；请指定其他区域。” |
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. 如果您有大量的 Glue 表格版本，请添加 “glue:GetTableVersion” 权限（推荐）或删除未使用的表格版本。如果您在 Glue 中没有大量表格，请联系 Su Amazon pport。” |
DataFirehose.InternalError |
"Timed out while retrieving table from Glue. 如果您有大量的 Glue 表格版本，请添加 “glue:GetTableVersion” 权限（推荐）或删除未使用的表格版本。如果您在 Glue 中没有大量表格，请联系 Su Amazon pport。” |
DataFormatConversion.GlueEncryptionException |
"There was an error retrieving the master key. Ensure that the key exists and state is correct." |
DataFormatConversion 调用错误
Amazon Data Firehose 可以将以下 DataFormatConversion 调用错误发送到日志。 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 whitespaces 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 |
"The specified table/database could not be found. Please ensure that the table/database exists and that the values provided in the schema configuration are correct, especially with regards to casing." |
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 在您指定的区域尚不可用；请指定其他区域。” |
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. 如果您有大量的 Glue 表格版本，请添加 “glue:GetTableVersion” 权限（推荐）或删除未使用的表格版本。如果您在 Glue 中没有大量表格，请联系 Su Amazon pport。” |
DataFirehose.InternalError |
"Timed out while retrieving table from Glue. 如果您有大量的 Glue 表格版本，请添加 “glue:GetTableVersion” 权限（推荐）或删除未使用的表格版本。如果您在 Glue 中没有大量表格，请联系 Su Amazon pport。” |
DataFormatConversion.MalformedData |
"One or more fields have incorrect format." |