Investigate the source of unexpected objects in OSS - Object Storage Service - Alibaba Cloud - Object Storage Service

Overview

This topic describes how to troubleshoot abnormal objects in an Object Storage Service (OSS) bucket.

Check whether the files are log files

Check whether logging is enabled for the bucket.
1. Log on to the OSS console.
2. In the navigation pane on the left, click Buckets, and then click the name of the target bucket.
3. In the navigation pane on the left, choose Log Management > Log Storage and enable log storage. For more information, see Configure log storage.
4. Click the Real-time Query tab and enable the real-time log query service to help you identify problems. For more information, see Real-time log query.
Check whether the names of the abnormal objects follow the OSS log record naming convention: [$TargetPrefix][$SourceBucket]YYYY-mm-DD-HH-MM-SS-[$UniqueString].
- If the abnormal objects follow the OSS log record naming convention and their content format matches the OSS log field format, the objects are OSS log files.
- For more information about the OSS log format, see Configure access logging.

The files are not OSS log files

Analyze the OSS logs to find the IP address and the service that uploaded the resources. Then, determine whether the service activity is normal.
If the resources were not uploaded by a normal service operation:
1. Check whether the bucket permission is set to public-read-write. If it is, change the permission to public-read or private.
2. If the bucket permission is set to private, check whether your AccessKey secret has been exposed. If so, create a new AccessKey pair and replace the old one. To obtain an AccessKey pair:
  1. Log on to the Resource Access Management (RAM) console.
  2. In the navigation pane on the left, choose Identity Management > Users. Click a user's logon name and find the AccessKey information in the AccessKey section.
    Note
    To create a new AccessKey, click Create AccessKey.