Feature Request Overview (mandatory - Complete while in New status){_}
{}What user goal or problem do you need to solve?{_} 

Customers using Dell ECS (or any S3-compatible object storage exposing a Swift API) as their OpenStack object storage backend cannot fully manage object storage resources through Horizon. Specifically, Horizon requires selecting a Swift Storage Policy when creating buckets/containers, even when an external Swift-compatible backend does not use or expose Swift Storage Policies.
This prevents customers from performing all CRUD operations from Horizon and forces them to rely on alternative tools (Dell ECS WebUI or CLI), resulting in fragmented workflows and increased operational complexity.

Business justification (mandatory - Complete while in New status)
How would this feature benefit the customer?

• It enables customers using Dell ECS or other Swift-compatible object storage systems to manage buckets directly in Horizon without needing an OpenStack Swift cluster.

• It eliminates the operational overhead of running and maintaining both OpenStack Swift and an external object storage solution solely to satisfy Horizon’s UI requirements.

• It improves user experience by allowing a single, unified interface for object storage management, reducing training, context switching, and errors.

• It strengthens Red Hat OpenStack’s value proposition by supporting heterogeneous storage backends commonly used by enterprise customers who already rely on S3-compatible platforms.

• It enhances ecosystem flexibility and increases OpenStack adoption in environments where Swift is no longer the preferred or strategic object storage solution.

Functional requirements (mandatory - Complete while in New status){_}
{}What do you want the result of this feature to be? Add as many requirements as needed.{_}

• Horizon must allow bucket/container creation without requiring a Swift Storage Policy, when the backend object store is Swift-compatible but does not implement Swift policies (e.g., Dell ECS).

• Horizon must detect or allow configuration of non-Swift backends that expose the Swift API, avoiding Swift-specific validation that blocks CRUD operations.

• All bucket CRUD operations (create, list, delete) must be supported through the Horizon UI for Swift-compatible backends.

• Horizon should expose a configuration toggle that:

• • Disables mandatory Swift policy selection, or

• • Allows selecting “No policy / external backend,” or

• • Dynamically hides the policy selector if the backend does not provide policy listings.

• The Horizon UI should provide consistent error handling and messaging when interacting with Swift-compatible backends that do not support native Swift features.

Describe the customer impact

Because Horizon does not currently allow bucket creation without selecting a Swift Storage Policy, customers cannot use OpenStack’s primary management interface for object storage operations.
This bottleneck forces operational teams and end users to switch to external interfaces (Dell ECS UI, CLI, etc.) for basic tasks, causing:

• Increased complexity and inconsistent workflows

• Higher training overhead

• Risk of configuration drift

• Reduced usability of OpenStack for developers and tenants

• Requirement to deploy and maintain Swift only to satisfy UI limitations, even when the customer does not use Swift for object storage

This limitation leads to avoidable operational costs and reduces the overall value of Red Hat OpenStack in mixed-backend environments.

IMPORTANT: Do not include customer names.

• Provide links to the account project
• Provide links to any related support tickets (open or closed)

For details on connecting Jira issues to an account, see Connecting Jira Issues to Accounts.

(Optional) Point of contact

• Provide any additional points of contact for this feature request, such as an account executive, SA, or TAM: 
•  

(Optional) Additional links

Click More > Link to add any links to issues, such as an outcome, that are related to this feature request.