---
schema_version: "1"
id: 4eac19bb773504c429169c194c2127643817c4cd2539614593bf318225da99b7
title: Create an AWS Glue File Federation Data Stream
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/data-cloud/data-cloud-int/guides/awsglue/c360-a-set-up-awsglue-file-fed-data-stream.md
canonical_url: https://developer.salesforce.com/docs/data/data-cloud-int/guide/c360-a-set-up-awsglue-file-fed-data-stream.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 36132460b9b50c94b6ad9e22ea91dda70391cf6f1c6a9cfc828cb9743fdce8ab
products:
  - Data 360 Integration Guide
  - Data 360 Developer Documentation
---
# Create an AWS Glue File Federation Data Stream

Start the flow of data by creating a data stream for AWS Glue Data Catalog. The data stream creates a data lake object (DLO) in Data 360 that you can map to the Customer 360 Data Model to use across Data 360.

| User Permissions Needed |                    |
| ----------------------- | ------------------ |
| To create a connection: | Data 360 Architect |

Before you begin:

- Make sure that the required AWS Glue Data Catalog connection is set up.

1.  In Data Cloud, on the Data Streams tab, click **New**.

2.  Under Other Sources, select the AWS Glue Data Catalog connection source, and click **Next**.

3.  From the dropdown menus, select the connection and database to use.

4.  Under **Schemas**, select the schema to use.

5.  From the **Available Objects**, select the objects you want to include.

6.  Click **Next**.

**note:** You can't choose objects listed under **In Use Objects**.

7.  Enter the object name and object API name. For more information, see [Data Lake Object Naming Standards](https://help.salesforce.com/s/articleView?id=data.c360_a_data_lake_object_naming.htm&type=5).

8.  Select the category to specify the type of data to ingest. For more information, see [Category](https://help.salesforce.com/s/articleView?id=data.c360_a_category.htm&type=5).

9.  Select a primary key to uniquely identify the incoming records. For more information, see [Primary Key](https://help.salesforce.com/s/articleView?id=data.c360_a_primary_key.htm&type=5).
10. Select the source fields you want to ingest and click **Next**. Fields with convertible data types are listed under Supported Fields.

**note:** Fields whose data types are not supported in Data Cloud get listed under Unsupported Fields.

11. Select the relevant data space. Choose **Default** for data space if you don’t have any other data space provisioned in your org. For more information, see [Data Spaces](https://help.salesforce.com/s/articleView?id=data.c360_a_data_spaces.htm&type=5).
12. Click **Deploy**.

## See Also

- [Salesforce Help: Zero Copy Data Federation](https://help.salesforce.com/s/articleView?id=data.c360_a_byol_data_federation.htm&type=5)
- [Salesforce Help: Billing Considerations for Data Federation](https://help.salesforce.com/s/articleView?id=data.c360_a_billing_considerations_for_data_federation.htm&type=5)
- [Salesforce Help: Caching in Data Federation](https://help.salesforce.com/s/articleView?id=data.c360_a_accelerated_data_lake_objects.htm&type=5)
- [Salesforce Help: Data Stream Settings and Refresh Modes](https://help.salesforce.com/s/articleView?id=data.c360_a_data_stream_edit_settings.htm&type=5)
