Feature Request: Folder-Based Organization for State Machines in AWS Step Functions (Beyond Tags)

Question

**Feature Request:** Folder-Based Organization for State Machines in AWS Step Functions (Beyond Tags)

**Problem:**
While AWS Step Functions supports tagging, it does not provide a way to visually organize or group state machines in the console. As the number of workflows grows, managing and navigating them becomes increasingly difficult.

**Current Behavior:**
* State machines are displayed in a flat list
* Tags can be applied, but:
* They are not visually represented as folders
* They do not provide hierarchical organization
* They require manual filtering instead of intuitive navigation

**Impact:**
* Difficult to manage large-scale environments with many workflows
* Slower navigation and reduced productivity
* Increased cognitive load for developers and operators
* Tags alone are insufficient for organizing workflows in a user-friendly way

**Why Tags Are Not Enough:**
Tags are useful for metadata and filtering, but they:
* Do not provide a folder-like browsing experience
* Do not support hierarchy (e.g., Project → Service → Workflow)
* Are not optimized for quick navigation in the console

**Proposed Solution:**
Introduce a folder-based (or grouping) system in the AWS Step Functions console.

**Features could include:**
* Create folders to group related state machines
* Optional nested folders (hierarchical organization)
* Drag-and-drop or assignment of workflows to folders
* Folder-based navigation in the UI
* Optional integration with tags (e.g., auto-group by tag)

**Example:**
Instead of a flat list:
* OrderWorkflow
* PaymentWorkflow
* ETLPipeline1
* ETLPipeline2

**Provide:**

```
Microservices/
├── OrderWorkflow
├── PaymentWorkflow

Data-Pipelines/
├── ETLPipeline1
├── ETLPipeline2
```

**Use Case:**
* Enterprise environments with 50–500+ state machines
* Microservices orchestration
* Data engineering pipelines
* Multi-team projects

**Why it matters:**
* Improves discoverability and navigation
* Enhances developer experience
* Reduces operational errors
* Aligns with common UI patterns used in other systems (e.g., file explorers, project structures)

**Additional Suggestion:**
If full folder support is not feasible, consider:
* Native UI grouping by tags
* Saved views or collections based on tags

Thank you for considering this improvement.

re:Post Agent · Answer

Thank you for your detailed feature request regarding folder-based organization for state machines in AWS Step Functions. I appreciate you taking the time to outline the problem, impact, and proposed solution.

Currently, AWS Step Functions does support tagging as a way to help track and manage resources associated with your state machines. Tags can assist with organizing workflows, managing costs, and providing better security in IAM policies. However, as you've correctly noted, the console displays state machines in a list format, and while tags can be applied for filtering and metadata purposes, they don't provide the hierarchical, folder-like visual organization you're describing.

Your feedback about the challenges of managing large-scale environments with many workflows is valuable. The need for improved navigation, reduced cognitive load, and a more intuitive browsing experience—especially in enterprise environments with dozens or hundreds of state machines—is well articulated.

While I cannot implement features or make commitments about future AWS service capabilities, I can confirm that your use case for better organization in microservices orchestration, data engineering pipelines, and multi-team projects is a common scenario where Step Functions is deployed.

For feature requests like this, I recommend submitting your feedback through official AWS channels:
- AWS Support (if you have a support plan)
- The AWS Step Functions service team through your AWS account team
- AWS re:Post community where AWS service teams monitor customer feedback

Your suggestion about alternative approaches, such as native UI grouping by tags or saved views based on tags, shows thoughtful consideration of different implementation options that could address the core need while potentially being easier to implement.

Thank you again for sharing this detailed feedback about improving the developer and operator experience with AWS Step Functions.  
**Sources**  
[Developing workflows in Step Functions Workflow Studio - AWS Step Functions](https://docs.aws.amazon.com/step-functions/latest/dg/workflow-studio.html)

Feature Request: Folder-Based Organization for State Machines in AWS Step Functions (Beyond Tags)

Add your answer

Relevant content