Linking a billing account
A billing account is used to identify a user who pays for computing resources, nodes, and storage of resources of all the community projects.
You can create a Yandex Cloud billing account in advance and link it when creating a community. In the DataSphere interface, you can also create a new billing account when selecting a billing account for the community.
Warning
If the selected billing account is suspended or has an overdue debt, you cannot link it to your DataSphere community. In this case, go to Yandex Cloud Billing
Only a community user with the datasphere.communities.editor
role or higher can link a billing account to a community. For operations with billing accounts, you also need the billing.accounts.editor
role or higher. If you are a community administrator but have no access to billing accounts in your organization, please contact your organization's administrator in Yandex Cloud.
Tip
You can only manage a billing account if you have a Yandex account. If you use Yandex Cloud through an identity federation, contact
Changing a community's billing account
Users with the Editor
or Admin
role can change the billing account used to pay for your community's projects and resources.
-
Open the DataSphere home page
. In the left-hand panel, select Communities. - Select a community and open the Settings tab.
- Under Billing, click
Edit. - Select an existing billing account or create a new billing account by following the prompts in the interface.
- Click Link.
Who pays for shared resources
How you pay for shared DataSphere resources depends on the resource type:
- Storing a dataset is paid from the billing account of the
parent
community whose project the dataset belongs to. - You can use secrets, Docker images, and aliases free-of-charge.
- S3 connectors are free of charge; however, storing objects in a Yandex Object Storage bucket is paid from the billing account linked to the cloud the bucket belongs to.
- You can use Yandex Data Processing templates free of charge. However, running a cluster automatically created from a template is paid from the billing account of the cloud that the cluster belongs to.