--- sourceDocument: Brazil IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Amazon S3 data input configuration fields # Amazon S3 data input configuration fields {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Description of the fields on the Amazon S3 data input configuration form. {#hla-data-input-s3-ref__table_rdw_xvb_x4b__entry__2} | Field | Description | |-|-| | Name | Name of the new data input. This field is required. | | Description | Optional description of the data input. | | Execute on | Option to select whether to use a specific MID Server or a specific MID Server cluster. This field is required. | | MID | (Only when the Execute on field is set to Specific MID Server) The MID Server to which log data from Amazon S3 is pulled. This field is required. Note: * The default maximum number of data inputs streaming logs to a single MID Server is 10. You can modify this number in the MID Server properties. * If log ingestion is not enabled for the selected MID Server, Health Log Analytics enables it automatically. {#hla-data-input-s3-ref__ul_hqb_zjj_nsb} | | MID Server Cluster | (Only when Execute on is set to Specific MID Server cluster.) The MID Server cluster to which the log data is pulled. This field is required. The data input runs on a single MID Server in the cluster until that MID Server fails. The system then moves all the data input tasks to the next available MID Server in the cluster according to the configured order. Note: * Health Log Analytics supports only failover MID Server clusters. In these clusters, multiple MID Servers are grouped together for failover protection. When selecting a cluster from the data input or integration form, the MID Server clusters list displays only failover clusters. * Log ingestion must be enabled for each MID Server in the cluster. If log ingestion is not enabled for the active MID Server, Health Log Analytics enables it automatically. * The default maximum number of data inputs or integrations streaming logs to a single MID Server is 10. A cluster passes capacity validation if it contains at least one MID Server with fewer than 10 data inputs or integrations running on it. This is true even when that MID Server is down. {#hla-data-input-s3-ref__ul_htt_wdq_dwb} For more information about MID Server clusters, see [Configure a MID Server cluster](https://www.servicenow.com/docs/access?context=t_ConfigureAMIDServerCluster&version=brazil&pubname=brazil-servicenow-platform&ft:locale=en-US). | | Service instance | The service instance to which to bind the log data. This field is required. Selecting the service instance enables HLA to correlate CIs and service instances in the CMDB for root cause analysis. Note: If no appropriate service instance exists, create one, add CIs to it, and set its status to Operational. For more information, see [Create a Service instance (application service)](https://www.servicenow.com/docs/access?context=create-it-services&version=brazil&pubname=brazil-servicenow-platform&ft:locale=en-US). | [ ] {#hla-data-input-s3-ref__table_rdw_xvb_x4b} {#hla-data-input-s3-ref__table_x1v_nlt_y4b__entry__2} | Field | Description | |-|-| | Status | Status of the data input. This field is read-only. | | Transport | Protocol used to stream the log data. This field is read-only. This data input uses Amazon S3 to stream log data to your instance. | | Sources count | The number of log sources this data input has created. This field is read-only. | | Disabled since | Time when the data input stopped or failed. This field is read-only. | | MID last receiving time | Time when the last log streamed in the data input. | | Error message | The streaming error. This field is populated automatically. It displays only when a streaming error has occurred. | | Advanced | Option to display the Advanced tab for advanced configuration. | [ ] {#hla-data-input-s3-ref__table_x1v_nlt_y4b} {#hla-data-input-s3-ref__table_glh_4nt_y4b__entry__3} | Field | Description | Example | |-|-|-| | From/To | Starting and ending dates and time for reading the data. This field is required. * From: Data older than this date and time is not read. Note: Setting this value to a past date might require the system to read large amounts of data, causing congestion. * To: Data newer than this date and time is not read. For live data, set this date far into the future. {#hla-data-input-s3-ref__ul_xcq_r4x_hnb} | From: Now -1 week To: 2300-01-01 15:59:59 | | Bucket name | The Amazon S3 bucket to stream. This field is required. | my-s3-bucket | | Prefix | Prefix for the objects to be fetched. The data input fetches only objects that begin with this prefix. This field is typically used to fetch only specific folders in a bucket. | /only/this/folder/ | | Include | File or object to include when the system performs pattern matching. | .\*include-me.\* | | Exclude | File or object to exclude when the system performs pattern matching. | .\*skip-me.\* | [Table 1. Query settings tab] {#hla-data-input-s3-ref__table_glh_4nt_y4b} {#hla-data-input-s3-ref__table_arg_1pt_y4b__entry__2} | Field | Description | |-|-| | AWS credentials | Field that refers to the AWS Credentials list (aws_credentials.list). The list contains the AWS access and secret access keys. | | Region | The AWS region where the Amazon S3 bucket is located, for example, us-west-1. This field is required. For a list of AWS regions, see | [Table 2. Transport tab] {#hla-data-input-s3-ref__table_arg_1pt_y4b} {#hla-data-input-s3-ref__table_n5c_nv3_x4b__entry__3} | Field | Description | Default value | |-|-|-| | Anonymous | Option to force accessing the Amazon S3 bucket without credentials, while ignoring default credentials if they exist. | False | | Traverse | Option to access each directory in the bucket. | False | | Object sorted by Last Modified Time | Option to fetch objects if the objects in the bucket are sorted by time. | False | | Connection timeout | The number of milliseconds to wait before timing out the attempt to establish a connection to AWS. | 100 | | Threadpool size | The number of concurrent threads that are downloading files from the bucket. | 1 | | Buffer size | Size of the download buffer, in bytes. | 100MB | | Socket timeout | The number of milliseconds to wait before timing out data transfer over an established connection. | 10000 | | Max retry per file | The maximum number of times to retry file processing in case of failure. | 10 | | Default timezone | The default time zone used when a log doesn't include time zone information. | GMT | | Sub sample drop ratio | The number of events to batch together, out of which one will be discarded. This setting is used to reduce the number of fetched events. | -1 | | Sub sample receive ratio | The number of events to batch together, out of which all but one will be discarded. This setting is used to decrease the number of received events. | -1 | | Max length in bytes | The maximum length, in bytes, of events. | 32766 | | Character encoding | The character encoding for this data input. This field is read-only. | UTF-8 | | Sleep interval (seconds) | The interval, in seconds, to wait before querying again after a query has returned no events. | 60 | | Polling interval | The interval, in seconds, to wait before polling for new events. | 0 | | Drop if queue is full | Option to discard logs if many processes are waiting in the queue to access the MID Server. | Clear | [Table 3. Advanced tab] {#hla-data-input-s3-ref__table_n5c_nv3_x4b}