Steps to resolve: To determine the root cause of this issue:

• Check that permissions have been set properly on the Amazon S3 bucket.
• Verify that the Amazon S3 bucket name has not been changed.

To determine if the cause of the issue is misconfiguration, look at the Telemetry Publisher logs. A failure message in the log such as the following means that the Amazon S3 bucket has either not been properly identified, or that the correct permissions have not been set:

...Metadata export failed com.amazonaws.services.s3.model.AmazonS3Exception: The specified bucket does not exist
  (Service: Amazon S3; Status Code: 404; Error Code: NoSuchBucket; Request ID: D28543E2494BD521), S3 Extended Request ID: 
...

Error message:

No serializer found

Workaround: This workaround does not resolve the issue, but provides additional information as to the actual source of the underlying error.

1. Log in to the Cloudera Navigator console.
2. Enable Navigator API logging.
3. Perform your action on the Audits page that raised the error message and see if the underlying issue is caught in the API log. If the Navigator API logging reveals no additional information, turn on API logging for Cloudera Manager:
   • Log in to the Cloudera Manager Admin Console.
   • Select Administrator > Settings
   • Select Advanced for the Category filter.
   • Click the Enable Debugging of API check box to select it. The server log will contain all API calls. Try your request again and see if the source error message displays in the response.