Billing in Google Cloud is set up at the project level. When you define a Google Cloud project you link a billing account to us. This billing account is where you will configure all your billing information including your payment option, you can link your billing account to one or more projects. Projects that don't link to a billing account can only use free Google Cloud services. Your billing account can be charged automatically and invoiced every month or at every threshold limit. You can separate project buildings by setting up billing some accounts. Some Google Cloud customers who resell Google Cloud services use subaccounts for each of it, their own clients. When you build an application on your arm premises infrastructure, you're responsible for the entire stack, security for the physical security of the hardware and the premise in which they're housed through the encryption of the data on disk, the integrity of your network and all the way up to securing the contents stored in those applications. But when you move an application to Google Cloud, Google handles many of the lower levels of security like physical security of the hardware in its premises, the encryption of the data on disk, and the integrity of the physical network. Because of its scale, Google can deliver a higher level of security at these levels that most customers can afford on their own. The upper layers of the security stack including the securing of data remain your responsibility. Google provides tools which help you implement the policies you define at these layers. The resource hierarchy we just explored is one of those tools. I am is another. You're probably thinking, how do I make sure I don't accidentally run up a big Google Cloud bill? Google Cloud provides three tools to help budgets and alerts, billing export, and reports. You can define budgets at the billing account level or at the project level. To be notified when costs approach your budget limit, you can create an alert, for example, with a budget limit of $20,000 an alert set at 90%. You will receive a notification alert when your expenses reach $18,000. You can also set up a web hook a way for an app to provide other applications with real time information to be called in response to an alert. This web hook can control automation based on billing alerts. For example, you could trigger a script to shut down resources when a billing alert occurs. Or you could use this web hook to file a trouble ticket for your team. Cloud billing export to BigQuery enables you to export detailed Google Cloud billing data, such as usage, cost estimates, and pricing data automatically throughout the day to a BigQuery data set that you specify. Then you can access your cloud billing data from BigQuery for detailed analysis, or use a tool like Google Data Studio to visualize your data. Note that the exporting of cloud billing data to file is now deprecated, and only available to existing customers using this feature. And reports is a visual tool in the council that allows you to monitor expenditure based on a project or services. Google Cloud also implements quotas which limits unforeseen extra billing charges, quotas are designed to prevent over consumption of resources because of an error or malicious attack. Quotas apply at the level of the Google Cloud project. There are two types of quotas, rate quotas and allocation quotas. Rate quotas reset after a specific time. For example, by default, the GKE service implements a quota of 1000 calls to its API from each Google Cloud project every 100 seconds. After that 100 seconds the limit then reset. This doesn't limit the rate of calls to your application running in GKE, but rather calls to the administrative configuration of your GKE clusters themselves. It would be very unusual to make that many calls in such a short period of time. The quota might well catch and stop erroneous behavior. Allocation quotas govern the number of resources that you can have in your projects. This count doesn't reset at intervals. Instead you need to free up resources to stay within them. For example, by default, each Google Cloud project has a quota, allowing no more than 5 virtual private cloud networks. These quotas are not the same for all projects, although projects start with the same quotas, you can change them by requesting an increase from Google Cloud support. Some quotas may increase automatically based on your use of a product, and you can use the Google Cloud console to explicitly lower some of them for your own projects. For example, if you want to put a more stringent cap on your consumption. Finally, some quotas are fixed for all Google Cloud customers, in addition to their benefits to customers, Google Cloud quotas also protect the community of Google Cloud users by reducing the risk of unforeseen spikes in usage.
