Docs Menu

Create From the UI

On this page

  • Prerequisites
  • Procedure

This page describes how to deploy a federated database instance for accessing data in an HTTP data store.

Note
Beta

The support for HTTP data stores is available as a Beta feature. The feature and the corresponding documentation may change at any time during the Beta stage.

Before you begin, you will need to:

  • Create a MongoDB Atlas account, if you do not have one already.
  • Format your data store using one of the supported data formats.

    Note

    If your file format is CSV or TSV, you must include a header row in your data. See Comma-Separated and Tab-Separated Value Data Files for more information.

  • Make your data store accessible over the public internet.
Important
  • If your HTTP data store is not accessible over HTTPS, you must use the JSON Editor to configure your data store. In your JSON configuration, you must set the stores.[n].allowInsecure setting to true.
  • Atlas Data Federation does not support HTTP data store URLs that require authentication.
1
2
3
  • For your first federated database instance, click Create a Federated Database.
  • For subsequent federated database instances, click Create Federated Database.
4
  • For a guided experience, click Visual Editor.
  • To edit the raw JSON, click JSON Editor.
5
6
  1. (Optional) Click the for the:

    • Data Lake to specify a name for your federated database instance. Defaults to Data Lake[n].
    • Database to edit the database name. Defaults to Database[n].

      Corresponds to databases.[n].name JSON configuration setting.

    • Collection to edit the collection name. Defaults to Collection[n].

      Corresponds to databases.[n].collections.name JSON configuration setting.

    • View to edit the view name.

    You can click:

    • Create Database to add databases and collections.
    • associated with the database to add collections to the database.
    • associated with the collection to add views on the collection. To create a view, you must specify:

      • The name of the view.
      • The pipeline to apply to the view.

        Note

        The view definition pipeline cannot include the $out or the $merge stage. If the view definition includes nested pipeline stages such as $lookup or $facet, this restriction applies to those nested pipelines as well.

      To learn more about views, see:

    • associated with the database, collection, or view to remove it.
  2. Select External from the dropdown in the Datasets section.
  3. Drag and drop the data store to map with the collection.

    Corresponds to databases.[n].collections.[n].dataSources JSON configuration setting.

7
←  HTTP URLAtlas Data Lake Datasets →
Give Feedback
© 2022 MongoDB, Inc.

About

  • Careers
  • Investor Relations
  • Legal Notices
  • Privacy Notices
  • Security Information
  • Trust Center
© 2022 MongoDB, Inc.