--- sourceDocument: Brazil Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # Create an Amazon S3 metadata collector # Create an Amazon S3 metadata collector {#ariaid-title1} Release version: Brazil Updated June 18, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read Use a metadata collector to import Amazon S3 bucket and object metadata into the data catalog. ## Before you begin * All prerequisite tasks must be complete. For more information, see [Prepare to run the Amazon S3 collector](https://www.servicenow.com/docs/Ft7JgBnhJNS5GKj4apSL~Q "Create an AWS IAM user with the permissions required for the metadata collector to harvest metadata from Amazon S3 buckets and objects."). * If you plan to run the collector on-premise, a MID Server is setup for the collector. For more information, see [MID Server for metadata collectors](https://www.servicenow.com/docs/2l_oawHD8jDgqUJN6Gaorw "When your source is behind a firewall or requires on-premises handling, deploy metadata collectors on a MID Server you host to harvest metadata from on-premises and privately networked data sources."). {#create-amazon-s3-metadata-collector__ul_an3_lrm_rjc} Role required: connection-admin. ## Procedure 1. Navigate to AllWorkflow Data FabricWorkflow Data Fabric Home. 2. Select the Connect Hub ![Connect Hub icon]() icon in the left sidebar. 3. Select CreateMetadata collector. 4. From the System list, select Amazon S3. 5. From the Connection type list, select one of the following: 1. Select New connection to configure a new connection. 2. Select Existing connection to reuse an existing connection and select an existing connection from the Connections list. The configuration form is filled with details from the existing connection. The name is appended with the word Copy and sensitive details like password aren't copied. {#create-amazon-s3-metadata-collector__substeps_lgh_q4y_jjc} 6. Complete the form. {#create-amazon-s3-metadata-collector__table_gkm_wgs_qhc__entry__2} | Field | Description | |-|-| | Connection name | Unique identifier for the connection. This field can't be modified once the connection is established. | | Short description | Purpose and details of the connection. | [Table 1. Amazon S3 metadata collector form] {#create-amazon-s3-metadata-collector__table_gkm_wgs_qhc} 7. Configure the connection options. {#create-amazon-s3-metadata-collector__table_s3_collector_props__entry__2} | Field | Description | |-|-| | Use MID server | Option to connect to the source system through a MID Server. When selected, the MID selection options appear. | | MID selection | MID Server routing option for the collector job. This field appears only when Use MID server is selected. * Auto-Select MID Server --- The system selects an available MID Server at job execution time. Default selection. * Specific MID Server --- The collector job runs on the selected MID Server. If the MID Server is offline at job execution time, the job fails with an error identifying the MID Server by name. * Specific MID Cluster --- The collector job runs on any available MID Server within the selected cluster. | | MID Server | MID Server to use for the collector job. This field appears only when Specific MID Server is selected. The selected MID Server is saved on the collector record and used for all subsequent collection runs until changed. | | MID Cluster | MID cluster to use for the collector job. This field appears only when Specific MID Cluster is selected. The selected cluster is saved on the collector record; any available MID Server within the cluster may serve the job. | | Capabilities | One or more capability labels that restrict auto-selection to MID Servers advertising those capabilities. This field appears only when Auto-Select MID Server is selected. | | MID application | MID Server application to use for the collector job. This field appears only when Auto-Select MID Server is selected. | | AWS Region | The AWS region used to start the S3 client. | [Table 2. Connection options] {#create-amazon-s3-metadata-collector__table_s3_collector_props} 8. Configure the authentication options. {#create-amazon-s3-metadata-collector__entry__24} | Field | Description | |-|-| | Authenticate using AWS Key/Secret | Specify the AWS Access Key ID and AWS Secret Access Key. | | Authenticate using IAM role | Specify the AWS IAM role ARN and AWS Role External ID. | [Table 3. Authentication options] 9. Configure the bucket and objects options. {#create-amazon-s3-metadata-collector__entry__30} | Field | Description | |-|-| | Excluded bucket | Specify the buckets to exclude. You can provide the bucket name or a regular expression to match. Use the parameter multiple times for multiple specific buckets. If multiple regular expressions are specified, the collector excludes buckets that match any of them. If both Include bucket and Excluded bucket are specified, Include bucket takes precedence. Note: If the bucket name includes special characters \[. , + , \* , ? , \^ , $ , ( , ) , \[ , \] , { , } , \| , \\\], use a backslash (\\) before the special character to escape it. For example, \\\[ | | Included bucket | Specify the buckets to collect. You can provide the bucket name or a regular expression to match. Use the parameter multiple times for multiple specific buckets. If multiple regular expressions are specified, the collector harvests buckets that match any of them. Note: If the bucket name includes special characters \[. , + , \* , ? , \^ , $ , ( , ) , \[ , \] , { , } , \| , \\\], use a backslash (\\) before the special character to escape it. For example, \\\[ | | Include object prefix | Specify the object prefix to harvest objects that begin with the specified prefix. | | Included object | Specify the objects to collect, using either an object name or a regular expression to match. Use the parameter multiple times for multiple specific objects. If multiple regular expressions are specified, the collector harvests objects that match any of them. If both Included object and Excluded object are specified, Included object takes precedence. Note: If the object name includes special characters \[. , + , \* , ? , \^ , $ , ( , ) , \[ , \] , { , } , \| , \\\], use a backslash (\\) before the special character to escape it. For example, \\\[ | | Excluded object | Specify the objects not to collect, using either an object name or a regular expression to match. Use the parameter multiple times for multiple specific objects. If multiple regular expressions are specified, the collector excludes objects that match any of them. If both Included object and Excluded object are specified, Included object takes precedence. Note: If the object name includes special characters \[. , + , \* , ? , \^ , $ , ( , ) , \[ , \] , { , } , \| , \\\], use a backslash (\\) before the special character to escape it. For example, \\\[ | [Table 4. Configuration options] 10. Configure the advanced options. {#create-amazon-s3-metadata-collector__entry__42} | Field | Description | |-|-| | Max objects per run | Maximum resources the collector will harvest, up to 10 million. If not specified, by default the collector will harvest a maximum of 10,000 resource. | [Table 5. Advanced options] 11. Select Save. ## Result The metadata collector is created and appears on the Connectors page with a Configured status. It is now ready to connect to the source system and harvest metadata. ## What to do next After creating the collector, you can perform any of the following tasks: * Run the collector manually to harvest metadata immediately. See [Run metadata collectors manually](https://www.servicenow.com/docs/aQKuJd5j3lCXk75ya17e~A "Execute a metadata collector on-demand to import metadata immediately."). * Automate metadata collection by scheduling regular collector runs. See [Schedule metadata collector runs](https://www.servicenow.com/docs/asZ0rH6fgXYHaoh9wK~UWw "Schedule a metadata collector to run automatically at a specified frequency."). * Monitor execution status and troubleshoot issues by viewing the runtime logs. See [View runtime logs for collector runs](https://www.servicenow.com/docs/k1TsyTx6kPU1XTWQB9VJdA "Access execution logs and download detailed log files for metadata collector runs."). * Discover and evaluate the harvested data assets in the Data Catalog. See [Governing the Data Catalog](https://www.servicenow.com/docs/0K_ULy_QruQwo4Xz2_VT8w "Data stewards add business context to catalog assets, making them more discoverable for catalog consumers. Governance tools include glossary terms, tags, domains, and direct asset updates."). {#create-amazon-s3-metadata-collector__ul_gjw_mym_rjc} *[\>]: and then