Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
All solutions
    • All solutions for DataProc
    • DataProc cluster is in the Unknown state immediately after creation
    • Resolving the error of access to S3 buckets from a DataProc 1.4 cluster

In this article:

  • Issue description
  • Solution
  1. DataProc
  2. Resolving the error of access to S3 buckets from a DataProc 1.4 cluster

Resolving the error of access to S3 buckets from a DataProc 1.4 cluster

Written by
Yandex Cloud
Updated at December 16, 2024
  • Issue description
  • Solution

Issue descriptionIssue description

When attempting to access S3 buckets from a DataProc 1.4 cluster, you see this error:

ls: doesBucketExist on yc-mdb-examples: com.amazonaws.AmazonClientException:
No AWS Credentials provided by ComputeMetadataCredentialsProvider : com.amazonaws.AmazonServiceException: Bad Request (Service: null; Status Code: 400; Error Code: null; Request ID: null)

Meanwhile, the cluster hosts have network access to S3.

SolutionSolution

Create a new cluster with DataProc version 2.0 or higher: the specified error does not occur there, and the connection to the bucket is valid.

Note

To establish a connection, use the ubuntu login rather than root.

Was the article helpful?

Previous
DataProc cluster is in the Unknown state immediately after creation
Next
All solutions for DataSphere
Yandex project
© 2025 Yandex.Cloud LLC