---
sourceDocument: Australia ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/platform-administration

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Create connector

# Create an Amazon S3 external content connector {#ariaid-title1}

Release version: Australia  
Updated August 18, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 minutes to read  
Create an external content connector to retrieve searchable content from your Amazon S3 source system.

## Before you begin

A source system administrator must have already configured your Amazon S3 source system to allow access by the Amazon S3 external content connector. For the required source system configuration steps, see [Configure Amazon S3 for external content indexing](https://servicenow-prod.fluidtopics.net/ED9R4K9Qwap~jqXAUvGgAQ "Create an Identity and Access Management (IAM) user in the Amazon Web Services (AWS) Management Console. Define an access key for your new user to allow the Amazon S3 external content connector to access your Amazon S3 source system.").

Role required: sn_ext_conn.xcc_admin

## Procedure

1. Navigate to AllExternal Content ConnectorsExternal Content Admin Home.
2. If prompted, select Switch scope to switch to the External Content Connectors Admin scope.  
   You must be in this scope to create or edit external content connectors.
3. In the Connectors section, select New.
4. On the Choose source page, select the Amazon S3 tile, then select Next.
5. On the Connection settings page, fill in the connection settings.  
   {#create-ext-cont-connector-amazon-s3__table_uvz_jrv_sdc__entry__2}

   | Connection setting | Description |
   |-|-|
   | Connector name | Unique name for this Amazon S3 external content connector. |
   | Access Key Id | Access key ID for the Amazon Web Services (AWS) IAM user account used by the Amazon S3 external content connector. If you don't have this access key ID, ask your AWS administrator for it. |
   | Secret Access Key | Secret access key for the Amazon Web Services (AWS) IAM user account used by the Amazon S3 external content connector. If you don't have this secret access key, ask your AWS administrator for it. |
   | I agree to the following legal disclaimer | Option acknowledging that the Amazon S3 external content connector makes all crawled content accessible by all search users. Amazon S3 content access permissions don't rely on users' email addresses, as retrieved in user permission crawls. As a result, user permission crawls aren't supported for the Amazon S3 external content connector. |
   [Table 1. Connection settings]

   {#create-ext-cont-connector-amazon-s3__table_uvz_jrv_sdc}
6. **Optional:** Expand the Advanced connection settings section and fill in the fields.  
   {#create-ext-cont-connector-amazon-s3__table_u4x_znw_gkc__entry__2}

   |   |   |
   |-|-|
   | Endpoint resolution | Selection mode for the AWS endpoint to use for connection and authentication. Supported values: * Automatic: The connector uses the AWS SDK and your AWS region and Use FIPS compliant endpoints settings to automatically select the AWS endpoint to use. * Manual: The connector uses the AWS endpoint and region that you specify in the Endpoint and AWS region fields. {#create-ext-cont-connector-amazon-s3__ul_nvq_14w_gkc} |
   | Use FIPS compliant endpoints | Option to force connection and authentication operations to use an AWS endpoint host that conforms to the Federal Information Processing Standards. This option appears only when you set Endpoint resolution to Automatic. It's only accessible when the region specified in the AWS region field supports FIPS endpoints. |
   | Endpoint | URL for the AWS endpoint host you want the connector to use for connection and authentication. As an example, to make the connector use the s3.us-east-1.amazonaws.com endpoint with the HTTPS protocol, you might enter <kbd class="ph userinput">https://s3.us-east-1.amazonaws.com</kbd>. This field appears only when you set Endpoint resolution to Manual. For the full list of supported endpoints, see the [Amazon Simple Storage Service endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/s3.html) Amazon documentation resource. Note: The Amazon resource lists endpoint hostnames. This field's value must be a valid URL, with the HTTP or HTTPS protocol prefix included. |
   | AWS region | AWS region containing your Amazon S3 buckets. As an example, you might specify <kbd class="ph userinput">us-west-1</kbd>. When Endpoint resolution is set to Automatic, the connector uses this region and the Use FIPS compliant endpoints option to determine the correct AWS endpoint to use for connection and authentication. To view the list of AWS regions, see the [Amazon Simple Storage Service endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/s3.html) Amazon documentation resource. Note: For regulatory market compliance, specify a regulated market AWS region, such as <kbd class="ph userinput">us-gov-east-1</kbd> or <kbd class="ph userinput">us-gov-west-1</kbd>. |
   | Buckets | List of Amazon S3 buckets containing your content. Enter a bucket name and press Add to add it to the list. You must populate this field when using an AWS endpoint that doesn't support automatic bucket discovery, such as a FIPS endpoint or an Amazon S3 Outposts endpoint. For other endpoints, you can leave this field empty to enable auto-discovery of buckets. When this list is populated, the connector only retrieves searchable content and metadata from the specified Amazon S3 buckets. |
   [Table 2. Advanced connection settings]

   {#create-ext-cont-connector-amazon-s3__table_u4x_znw_gkc}
7. Save and validate your connection settings by selecting Validate Connection.  
   Note:  
   If validation of your connection settings fails, the system shows an error message. Verify your connection settings to ensure they're correct. If permissions required by the connector are missing or incorrectly configured in the source system, a warning message appears showing the permissions that must be corrected. Provide the information from this message to your source system administrator. {#create-ext-cont-connector-amazon-s3__new-connector-save-connection-settings-cmd}
8. On the Crawl settings page, modify any default crawl settings that you want to override for this connector, then select Next.  
   If you want to skip this step for now, select Skip instead of Next. You can modify the crawl settings for this connector from the External Content Admin Home page. For details on this procedure and the available crawl settings, see [Configure crawl settings for an Atlassian Confluence Cloud external content connector](https://servicenow-prod.fluidtopics.net/X~Zy3wKKLqVAFQsA0L2olw "Specify the spaces you want your Atlassian Confluence Cloud external content connector to crawl. Define inclusion or exclusion filters to dictate the types of content the crawl retrieves and feeds to AI Search for indexing.").
9. On the Create crawl page, create a content crawl for this connector by selecting a crawl scope (if supported) and any desired options, then select Next.  
   If you want to skip this step for now, select Skip instead of Next. You can create and run crawls for this connector from the External Content Admin Home page. For details on creating content crawls, see [Create a content crawl for an external content connector](https://servicenow-prod.fluidtopics.net/fFJ92ZYif96fkc2JA4HtyQ "Retrieve searchable content and metadata from your source system with a content crawl. Run the crawl as a one-time task or schedule it to run on a recurring basis.").
10. On the Connect search profile page, use the Connect to search profile field and Add button to add any search profiles that you want to connect this external content connector's default search source to, then select Save.  
    If you want to skip this step for now, select Skip instead of Next. You can connect search sources for this connector to search profiles from the External Content Admin Home page. For details on connecting an external content connector to search profiles, see [Connect an external content connector to a search profile](https://servicenow-prod.fluidtopics.net/O1_d0dPqWANwyTUPT43BrA "Make results from an external content connector searchable in your portals and search applications by connecting its search sources to your existing search profiles.").

    When you link a connector search source to a search profile in this step, the system automatically publishes the search profile to make the new link take
    effect.
{#create-ext-cont-connector-amazon-s3__steps_yxs_mnq_4fc}

## Result

Your new external content connector appears in the Connectors list on the External Content Admin Home page.

## What to do next

To retrieve searchable content with your new connector, you must configure and run content crawls for it. You can modify your new connector's crawl settings and create crawls for it from the External Content Admin Home page even if you skipped these steps during connector creation.

* To learn how to configure your new connector's crawl settings, see [Configure crawl settings for an Amazon S3 external content connector](https://servicenow-prod.fluidtopics.net/Va3JtkniX092nQx5f~kWMw "Define inclusion and exclusion filters to specify the buckets and file types you want your Amazon S3 external content connector to retrieve when running content crawls.").
* For details on creating crawls for your new connector, see [Create a content crawl for an external content connector](https://servicenow-prod.fluidtopics.net/fFJ92ZYif96fkc2JA4HtyQ "Retrieve searchable content and metadata from your source system with a content crawl. Run the crawl as a one-time task or schedule it to run on a recurring basis.").

{#create-ext-cont-connector-amazon-s3__ul_zkt_3qj_4fc}  
Important:  
All content the connector retrieves from your Amazon S3 buckets is treated as public content, searchable by everyone who has access to your configured AI Search experience.  
To make content crawled by your new connector searchable in portals and search applications, you must link one of its search sources to the search profile used by each portal or search application. You can use the connector's default search source or create your own custom search sources.

Default search source
:   By default, the system creates a search source that includes all content from your external content connector's indexed source.

Custom search sources
:   You can create your own search sources with filters to specify which content from the connector's indexed source is searchable. To view the connector's indexed source, navigate to AllAI SearchAI Search IndexIndexed Sources. For information about creating search sources, see [Search sources in AI Search](https://servicenow-prod.fluidtopics.net/BzYQ0BGXWlEpJrmmvXanyw "Define search sources to make your searchable content available in search experiences. Choose an indexed source and configure optional filter conditions to limit the content that users can search.").
You can link connector search sources to search profiles from the External Content Admin Home page. For details on this procedure, see [Connect an external content connector to a search profile](https://servicenow-prod.fluidtopics.net/O1_d0dPqWANwyTUPT43BrA "Make results from an external content connector searchable in your portals and search applications by connecting its search sources to your existing search profiles.").

*[\>]: and then


