If you want to perform operations such as real-time processing, synchronization, listening, business triggering, and logging for object changes, you can set event notification rules in the Object Storage Service (OSS) console to customize specific objects. OSS event notifications automatically push event messages to a Simple Message Queue (SMQ, formerly MNS) queue or topic whenever matching object changes occur. Your application consumes those messages and runs the appropriate business logic.
How it works
You set event notification rules in the OSS console to customize specific objects. The rule specifies which object changes to monitor and which SMQ destination receives the events.
When a matching change occurs, OSS pushes an event message to the designated SMQ queue or topic.
Your application consumes the message from the queue or topic and runs downstream logic.
Choosing between a queue and a topic:
| Destination | Pattern | When to use |
|---|---|---|
| Queue | Point-to-point | A single consumer processes each event. Use this for sequential workflows where each event needs exactly one handler. |
| Topic | Publish-subscribe | Multiple subscribers receive the same event. Use this when several independent systems need to react to the same object change. |
Use cases
| Scenario | Description |
|---|---|
| Real-time processing | Process object changes as they happen. |
| Synchronization | Keep dependent systems in sync with object changes. |
| Listening | Monitor objects for specific changes. |
| Business triggering | Start downstream business workflows when specific object events occur. |
| Logging | Record object-level operations for review. |
Configure event notification rules
You can configure OSS event notification rules from either the SMQ console or the OSS console.
| Method | Guide |
|---|---|
| SMQ console | Create an OSS event notification rule |
| OSS console | Tutorial: Use SMQ to send notifications of OSS events |