Data Quality

Bytes Ingested

The amount of data ingested by DataBee measured in mB/GB

Feed Bandwidth

The rate of log processing measured in logs/sec (or MB/sec)

Owner

The owner specified when the data source was configured

Records Ingested

The number of individual records ingested by DataBee

Feed Mapping Efficiency

The percentage of records that were able to be mapped out of the total ingested

Records Mapped

The number of records that were mapped to an OCSF event or object table

Data Last Ingested

The last date that the feed was successfully run

Your authentication token has expired and needs to be refreshed.

Request a new authentication token from your AWS service. Check token expiration handling in your code.

You don't have permission to perform this operation on the S3 resource.

Verify IAM roles and permissions. Check bucket policies and ACLs. Ensure your credentials have the required permissions.

The bucket must be empty before it can be deleted.

Remove all objects from the bucket first, or use the force delete option if available in your SDK.

The specified bucket name is not valid or follows incorrect naming conventions.

Ensure bucket name follows S3 naming rules: lowercase letters, numbers, dots, and hyphens only. Must be 3-63 characters long.

The requested operation cannot be performed on the object in its current state.

Check if object is in Glacier storage. Verify object lock settings. Ensure object is not being modified by another operation.

The specified bucket does not exist.

Verify bucket name and region. Check if bucket was deleted or never created. Ensure you're using the correct AWS account.

The specified file or object could not be found in the bucket.

Verify object key path. Check if file was deleted. Ensure correct bucket and folder structure.

One or more preconditions you specified for the operation did not hold.

Check ETag matches and conditional headers. Verify if object was modified since last retrieval.

Please reduce your request rate as you are sending too many requests.

Implement exponential backoff. Add request rate limiting. Consider using S3 Transfer Acceleration for better performance.

An unexpected error occurred while processing your S3 request.

Check AWS service health dashboard. Review CloudWatch logs. Contact AWS support if persistent.

ExpiredToken: The security token included in the request is expired

2400

SQS_ExpiredToken

Your authentication token for accessing SQS has expired and needs to be renewed.

Request a new authentication token from AWS and update your application's credentials.

You don't have the necessary permissions to perform this operation on the SQS queue.

Check IAM roles and policies, ensure your credentials have the required SQS permissions.

One or more parameters provided in your SQS request have invalid values.

Review API documentation for correct parameter formats and validate all input values.

A required parameter is missing from your SQS request.

Check API documentation for required parameters and ensure all are included in your request.

The message you're trying to process is not currently in flight or being processed.

Verify message receipt handle is valid and message hasn't exceeded visibility timeout.

You have exceeded the maximum allowed limit for this SQS operation.

Implement request throttling or contact AWS support to increase your quota limits.

You cannot create a queue with this name because it was recently deleted.

Wait 60 seconds before recreating a queue with the same name, or use a different queue name.

The specified SQS queue does not exist.

Verify queue URL/name and region, ensure queue hasn't been deleted.

The message content contains invalid characters or exceeds size limits.

Check message format and size, ensure it meets SQS message requirements.

An unexpected error occurred while processing your SQS request.

Check AWS service health, review CloudWatch logs, and contact AWS support if persistent.

The authentication information provided for accessing the Azure Blob storage is invalid or malformed.

Verify your connection string, access keys, or SAS token are correct and not expired.

The blob or block data you're trying to access or modify is invalid or corrupted.

Check the blob name, size limits, and ensure data integrity during upload/download operations.

Your account lacks the necessary permissions to perform this operation on the blob storage.

Review and update your Azure role assignments and access policies for the storage account.

The request was not authorized to perform this operation on the blob resource.

Check your shared access signature (SAS) permissions and storage account access policies.

The requested blob could not be found in the specified container.

Verify the blob name and path, ensure the blob hasn't been deleted or moved.

The specified container does not exist in the storage account.

Check the container name and ensure it exists in the correct storage account.

The requested Azure Blob storage resource could not be found.

Verify the resource path, name, and ensure the storage account is correctly configured.

A blob with this name already exists in the container.

Use a different blob name or implement logic to handle existing blobs (overwrite/skip).

A container with this name already exists in the storage account.

Choose a different container name or handle existing container scenarios appropriately.

One or more query parameters in your blob storage request are invalid.

Review the API documentation and validate all query parameters meet the required format.

The specified Azure Storage queue could not be found.

Verify the queue name and ensure it exists in the correct storage account.

The queue service is currently disabled for this storage account.

Enable the queue service in your storage account settings or use an alternative storage account.

An unexpected error occurred while accessing Azure Blob storage.

Check Azure service health, review application logs, and contact Azure support if the issue persists.

The redirect URL provided in your request is not valid or properly formatted.

Check the redirect URL format, ensure it matches the allowed URLs in your API settings, and verify it's properly encoded.

The request is missing a required redirect URL parameter.

Add a valid redirect URI to your request parameters as specified in the API documentation.

The authorization code provided has expired or is not valid.

Request a new authorization code and ensure you're using it promptly before it expires.

The refresh token provided is not valid or has been revoked.

Initiate a new authentication flow to obtain a fresh refresh token.

The refresh token has exceeded its lifetime and is no longer valid.

Perform a new authentication flow to obtain new access and refresh tokens.

The client is not authorized to request an authorization code.

Verify your client credentials and ensure your application has the necessary permissions.

The response type specified in the authorization request is not supported.

Use one of the supported response types (usually 'code' or 'token') as specified in the API documentation.

The grant type specified in the token request is not supported.

Use one of the supported grant types (e.g., 'authorization_code', 'refresh_token') as specified in the API documentation.

The request is missing a required parameter or contains an invalid parameter value.

Review the API documentation and ensure all required parameters are included with valid values.

The access token provided is not valid or has been revoked.

Obtain a new access token using your refresh token or perform a new authentication flow.

The access token has exceeded its lifetime and is no longer valid.

Use your refresh token to obtain a new access token, or perform a new authentication flow if the refresh token is also expired.

The access token has not been approved or was rejected by the authorization server.

Check if the user has granted all required permissions and initiate a new authentication flow if necessary.

The access token does not have the required permissions to perform this operation.

Request additional scopes during the authentication process or use a token with the necessary permissions.