Skip to main content

Regions, Zones and Resouces

Google Cloud Platform is organized into Regions and Zones

Regions are independent geographic areas that consist of zones

A zone is is a deployment area for Google Cloud Platform resources (like Compute Engine, VPC) with in region.Think of a zone as a single failure domain within a region. In order to deploy
fault-tolerant applications with high availability, you should deploy your applications
across multiple zones in a region to help protect against unexpected failures.

To protect against the loss of an entire region due to natural disaster, you should have
a disaster recovery plan and know how to bring up your application in the unlikely
event that your primary region is lost.

Zonal resources

Zonal resources operate within a single zone. If a zone becomes unavailable, all of the
zonal resources in that zone are unavailable until service is restored.
● Google Compute Engine VM instance resides within a specific zone.

Regional resources

Regional resources are deployed with redundancy within a region. This gives them
higher availability relative to zonal resources

Multi-regional resources

A few Google Cloud Platform services are managed by Google to be redundant and
distributed within and across regions.These services optimize availability,
performance, and resource efficiency. The following services have one or more multi-regional
deployments in addition to any regional deployments:
● Google App Engine and its features
● Google Cloud Datastore
● Google Cloud Storage
● Google BigQuery

Comments

Popular posts from this blog

Container and Container Orchestration

What is container? Container contain application code and dependencies into single Unit. So, what is Container orchestration? Container orchestration is about to managing life cycle of container. Container orchestration to control and automate task: Provisioning and deployment of container Scaling up and removing container as per application load Allocation the resource between Container Health check of container Kubernetes open Source is the example of Container Orchestration

Cloud Storage and Cloud IAM or ACLs or Signed URLs

Cloud Storage offers layers of increasingly granular access control. For most purposes, Cloud IAM is sufficient, and roles are inherited from project to bucket to object. Access control lists (ACL) offer finer control. And for detailed control, signed URLs provide a cryptographic key that gives time-limited access to a bucket or object. A signed policy document further refines the control by determining what kind of file can be uploaded by someone with a signed URL Cloud IAM Works with Cloud Storage just as with using Cloud IAM with any other resource. Project Owners are automatically granted Bucket Owner role for all buckets in the project. Note that ACLs and Cloud IAM are independent, so Project-level Cloud IAM permissions will not appear in bucket or object ACLs. Signed URLs A signed URL gives you the ability to grant access to a bucket without Cloud IAM user authentication for a limited period of time. e.g., when you don’t want to require users to have Goog...

Service Accounts

What if you want to give permissions to a Compute Engine virtual machine rather than to a person? That’s what service accounts are for. For instance, maybe you have an application running in a virtual machine that needs to store data in Google Cloud Storage. But you don’t want to let just anyone on the Internet have access to that data; only that virtual machine. So you’d create a service account to authenticate your VM to Cloud Storage. Service accounts are named with an email address, but instead of passwords they use cryptographic keys to access resources. Service Accounts control server-to-server interactions: Provide an identity for carrying out server-to-server interactions in a project Used to authenticate from one service to another Used to control privileges used by resources                 So that applications can perform actions on behalf of authenticated end users Identified with an ...