An Atlas Stream Processing workspace provides a context for all of your operations on streaming data. The procedures in this page walk you through creating and configuring your stream processing workspaces.
Prerequisites
To create and configure a stream processing workspace, you must have the following:
An Atlas project
An Atlas user with the
Project Owner, theProject Stream Processing Owner, or theProject Data Access Adminrole to manage a Stream Processing Workspace.Note
While the
Project Owner,Project Stream Processing Owner, andProject Data Access Adminroles all grant the privileges to create, view, edit, and delete stream processing workspaces, theProject Ownerrole also allows users to perform tasks such as creating database deployments, managing project access, and more.See Project Roles to learn more about the differences between these roles.
Considerations
You must set a default tier when you create a stream processing workspace. Stream processors that you create in this workspace default to this tier. You can optionally set a max tier size as well. You can't create stream processors larger than the max tier in this workspace.
Defaults:
default tier:
SP10max tier size: unset
You can configure the default and max stream processing workspace tiers only from the Atlas control plane (UI, API, Terraform, or CLI). You can't configure the default and tiers from the data plane (mongosh).
View stream processing workspaces
To view your stream processing workspaces:
Create a stream processing workspace
To create a new stream processing workspace:
Delete a stream processing workspace
To delete a stream processing workspace:
Edit a stream processing workspace
To edit an stream processing workspace:
Trigger stream processing workspace Failover
Atlas Stream Processing supports processor failover at the workspace level. When you trigger workspace-level failover, all stream processors within that workspace shift processing to their configured failover processors simultaneously.
Download Audit Logs
To download your stream processing workspace audit logs: