Add a Sonar Project

note

This tutorial uses the CloudFormation template for connecting an AWS account, which is the recommended method for configuring project resources. For more information on the resources being created and the permissions granted to Dremio, see the annotated CloudFormation Template.

If you want to manually create cloud and project resources for AWS instead, see Configuring Your Cloud Resources Manually.

If you have already created a project with Dremio, move on to Create a Table & Add Dataset Info.

After you have addressed the prerequisites, follow these steps to create your first Sonar project:

1. On your organization homepage, click Add Sonar Project on the Sonar card.

2. In the Add Sonar Project dialog, for Project name, specify a name to identify your project. You can change the name of the project after creation.

3. For Arctic catalog name, specify a name to identify the primary catalog in your project. The name cannot be changed once the catalog has been created.

4. Select your cloud provider.

5. Select the region in which compute resources and the project store will be created. For a list of supported regions, see Supported Regions.

6. (Optional) Add one or more tags to help you identify compute resources for this project in your cloud provider account.

7. Click Next.

To continue the configuration, follow the steps for your cloud provider.

AWS

8. Click Launch CloudFormation Template, which will open the AWS console in a new browser tab.


9. On the “Quick create stack” page in the AWS Console, for Stack name, enter a name to identify the stack. This name must be unique to your AWS account and cannot include underscores.


10. For VPC, select the VPC in which compute resources will be created.


11. For Subnets, select one or more subnets where compute resources will be created.


12. For Project Store, a unique name has been generated for the S3 bucket that will be created in your AWS account as the metadata store for your project. You can specify a different name here but it must be unique across AWS.


13. For Encryption Type, SSE-S3 is the default encryption mechanism for the project store S3 bucket. You can select SSE-KMS (AWS Managed Key) or SSE-KMS (Customer Managed Key) for additional encryption. If you select SSE-KMS (Customer Managed Key), specify the KMS Key ARN.


14. Check I acknowledge that AWS CloudFormation might create IAM resources.


15. Click Create stack.

It will take about 5 minutes to create the required storage and compute resources for the project.

When stack creation has completed in the AWS Console, return to the Dremio Console to start querying sample data and creating your first table.

Azure

8. For Tenant ID, paste the ID of the Azure tenant.


9. For Project Store, paste the name of the storage container that you want to use for the project store.


10. For Account Name, paste the name of the storage account that you want to use for the project store.


11. For Client ID, paste the application (client) ID of the registered application.


12. For Client Secret, paste the value of the client secret that you created in the registered application.


13. Click Validate for the policy JSON.


14. For Tenant ID, paste the ID of the Azure tenant.


15. For Subscription ID, paste the ID of your Azure subscription.


16. For Client ID, paste the application (client) ID of the registered application.


17. For Client Secret, paste the value of the client secret that you created in the registered application.


18. For Resource Group, paste the name of the resource group.


19. For Subnet, paste the name of the subnet.


20. (Optional) For Network Security Group, paste the name of the security network group.


21. For Virtual Network, paste the name of the virtual network.


22. Click Validate.


23. Click Done.

It will take 4-5 minutes for your first project to complete the setup process.

note

If you encounter errors during resource creation for AWS, see Dremio Cloud Troubleshooting for AWS.

Next: Create a Table & Add Dataset Info