{"id":92081,"date":"2023-11-22T23:42:32","date_gmt":"2023-11-23T05:12:32","guid":{"rendered":"https:\/\/www.whizlabs.com\/blog\/?p=92081"},"modified":"2023-11-22T23:42:32","modified_gmt":"2023-11-23T05:12:32","slug":"google-compute-vs-app-engine","status":"publish","type":"post","link":"https:\/\/www.whizlabs.com\/blog\/google-compute-vs-app-engine\/","title":{"rendered":"Comparison of Google Compute Engine vs App Engine"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">Google cloud platform (GCP) offers a broad range of services aiming to solve a plethora of user needs. Compute Engine and App Engine are two of them. These serverless computing tools allow developers to concentrate on the most crucial aspect of their work \u2013 development \u2013 without the need to concern themselves with the intricacies of infrastructure and upkeep. Additional advantages, like autoscaling, pay-as-you-go, and on-demand provisioning, make it an obvious choice for those creating stateless <strong>HTTP applications, web and mobile apps, IoT and sensor applications, data processing systems, chatbots,<\/strong> and more.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">But if you are new to the domain, these concepts can look overarching and similar but work differently when you use them for app development. So, it becomes critical to dive into the roots of these applications and understand how they will benefit you and which will best fit your app users&#8217; needs. This blog will cover these avenues and explore the <a href=\"https:\/\/www.whizlabs.com\/blog\/google-compute-engine-features-and-advantages\/#:~:text=Whizlabs%20provides%20high%20class%20online,Machines%20over%20the%20cloud%20infrastructure.\" target=\"_blank\" rel=\"noopener\">Google Compute Engine<\/a> vs App Engine debate. <\/span><\/p>\n<p><span style=\"font-weight: 400;\">Let&#8217;s dive in.\u00a0<\/span><\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_76 ez-toc-wrap-left counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #ea7e02;color:#ea7e02\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #ea7e02;color:#ea7e02\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.whizlabs.com\/blog\/google-compute-vs-app-engine\/#Google_Compute_Engine\" >Google Compute Engine<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.whizlabs.com\/blog\/google-compute-vs-app-engine\/#Google_App_Engine\" >Google App Engine\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.whizlabs.com\/blog\/google-compute-vs-app-engine\/#Compute_Engine_vs_App_Engine\" >Compute Engine vs App Engine<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.whizlabs.com\/blog\/google-compute-vs-app-engine\/#Google_Compute_Engine_vs_App_Engine_Things_to_consider\" >Google Compute Engine vs App Engine: Things to consider<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.whizlabs.com\/blog\/google-compute-vs-app-engine\/#Use_hands-on_labs_to_understand_the_difference\" >Use hands-on labs to understand the difference<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.whizlabs.com\/blog\/google-compute-vs-app-engine\/#Connecting_MongoDB_Atlas_to_Google_Cloud_Compute_Engine\" >Connecting MongoDB Atlas to Google Cloud Compute Engine<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.whizlabs.com\/blog\/google-compute-vs-app-engine\/#An_Overview_of_Google_Compute_Engine\" >An Overview of Google Compute Engine<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.whizlabs.com\/blog\/google-compute-vs-app-engine\/#Setting_up_IAP_on_Google_Compute_Engine\" >Setting up IAP on Google Compute Engine<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.whizlabs.com\/blog\/google-compute-vs-app-engine\/#Leveraging_Startup_and_Shutdown_Scripts_on_Google_Compute_Engine\" >Leveraging Startup and Shutdown Scripts on Google Compute Engine<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/www.whizlabs.com\/blog\/google-compute-vs-app-engine\/#Summary\" >Summary<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"Google_Compute_Engine\"><\/span><strong>Google Compute Engine<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">The <a href=\"https:\/\/cloud.google.com\/compute\/docs\" target=\"_blank\" rel=\"noopener\">Compute Engine<\/a> service is Google&#8217;s unmanaged computing service. Think of the Compute Engine as an Infrastructure as a Service (IaaS) offered by Google Cloud. Since this service is unmanaged, you must configure, administer, and monitor the system. On Google&#8217;s end, they&#8217;ll ensure that resources are available, reliable, and ready for use. The primary advantage of using Compute Engine is that you have complete control over the systems.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Here&#8217;s what you can do when you build on Compute Engine:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Create Virtual Instances, the most minor units in the GCP project.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Create instance groups to manage multiple instances together easily.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Create virtual machine images.<\/span><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">The virtual machine instances run in zones that are assigned to them. Zones are resources similar to data centers located within regions, which are geographical locations. The zones within a region are connected with <strong>low-latency, high-bandwidth network connections.<\/strong><\/span><\/p>\n<p><b>Pros<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Compute Engine provides users with total control over Virtual Machine instances. It offers a straightforward setup process, allowing you to launch a server in just a few minutes. Additionally, leveraging preemptive VMs can significantly cut costs by up to 80%. The service also offers a set of predefined VM configurations and images readily available for use based on your specific requirements.<\/span><\/p>\n<p><b>Cons\u00a0<\/b><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Utilizes a high level of expertise, as users are responsible for the installation and configuration of all components themselves.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Autoscaling is not as swift as with App Engine.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To enable monitoring, users must install packages into the VM instances; direct Stackdriver monitoring is not supported.<\/span><\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Google_App_Engine\"><\/span><span style=\"font-weight: 400;\"><strong>Google App Engine<\/strong>\u00a0<\/span><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">App Engine is Google&#8217;s Platform as a <strong>Service (PaaS)<\/strong> offering, providing a managed platform for running applications. This managed service allows you to focus solely on your application, leaving Google to handle the necessary resources for running it. While App Engine users have less to work, they also have less control over the compute resources. Applications hosted on App Engine are highly scalable and exhibit reliable performance even under heavy loads.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">App Engine supports the following languages:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Python<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Go<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Ruby<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">PHP<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Node.js<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Java<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">.NET<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">There are two runtime environments available within App Engine:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Standard Environment: This environment offers a secure, sandboxed space for running applications. It distributes requests across multiple servers to meet demand. Applications run independently of the underlying hardware, operating system, and server&#8217;s physical location.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Flexible Environment: The flexible environment provides more options and control for developers using App Engine without the language constraints of the standard environment. It utilizes Docker containers as the fundamental building blocks, allowing these containers to auto-scale according to the application&#8217;s load.<\/span><\/li>\n<\/ol>\n<p><b>Pros\u00a0<\/b><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">With App Engine, your primary focus is solely on the application code, as Google takes care of everything else, simplifying management.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It offers version management, making it easy to maintain and roll out different versions of applications.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">App Engine features faster autoscaling due to smaller instance sizes.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Deployment and monitoring are straightforward and user-friendly.<\/span><\/li>\n<\/ul>\n<p><b>Cons<\/b><span style=\"font-weight: 400;\">\u00a0<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">App Engine&#8217;s more minor instances allow for rapid autoscaling. Still, this constraint can pose challenges for more extensive applications requiring more significant instances.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Since it is a fully managed service, users have limited control over the underlying infrastructure, which may be necessary for complex applications.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">In the long term, App Engine can become costly as costs accumulate quickly.<\/span><\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Compute_Engine_vs_App_Engine\"><\/span><strong>Compute Engine vs App Engine<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">At first glance, several products and services within the Google Cloud platform may need clarification for non-technical users. However, grasping the distinctions between these tools used for app development can significantly enhance digital product management and increase the likelihood of success.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">There are crucial differences between Google App Engine and Google Compute Engine. Still, you only need to grasp one key differentiator: Google App Engine is a PaaS. At the same time, Google Compute Engine is an IaaS. Here are other noteworthy differences.\u00a0<\/span><\/p>\n<p><img decoding=\"async\" class=\"alignnone wp-image-92097 size-full\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Compute-Engine-vs-App-Engine-Info.webp\" alt=\"Compute Engine vs App Engine\" width=\"1300\" height=\"1380\" srcset=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Compute-Engine-vs-App-Engine-Info.webp 1300w, https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Compute-Engine-vs-App-Engine-Info-283x300.webp 283w, https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Compute-Engine-vs-App-Engine-Info-965x1024.webp 965w, https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Compute-Engine-vs-App-Engine-Info-768x815.webp 768w, https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Compute-Engine-vs-App-Engine-Info-150x159.webp 150w\" sizes=\"(max-width: 1300px) 100vw, 1300px\" \/><\/p>\n<blockquote><p>Know More : <a href=\"https:\/\/www.whizlabs.com\/blog\/google-cloud-professional-cloud-architect-labs\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">Top hands-on labs to prepare for Google Cloud Professional Cloud Architect<\/span><\/a><\/p><\/blockquote>\n<h2><span class=\"ez-toc-section\" id=\"Google_Compute_Engine_vs_App_Engine_Things_to_consider\"><\/span><strong>Google Compute Engine vs App Engine: Things to consider<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">When deciding between a Compute Engine and vs App Engine, several factors should be considered to ensure that the chosen platform aligns with your application needs and development preferences.<\/span><\/p>\n<h4><strong>Service Model<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">Firstly, consider the service model. Compute Engine operates as IaaS, providing greater control over virtual machine instances and infrastructure configurations. In contrast, App Engine is a PaaS offering emphasizing managed infrastructure and simplifying development.<\/span><\/p>\n<h4><strong>Control and Flexibility<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">Control and flexibility are crucial considerations. Compute Engine offers extensive control over virtual machine configurations, operating systems, and software installations, making it suitable for applications with specific customization requirements. On the other hand, the App Engine provides less control over the underlying infrastructure, prioritizing rapid development and scalability over customization.<\/span><\/p>\n<h4><strong>Scalability<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">Scalability is another critical factor. Compute Engine requires manual configuration for scaling. App Engine offers automatic scaling based on traffic, making it ideal for applications with fluctuating workloads.<\/span><\/p>\n<h4><strong>Language Support<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">Language support differs between the two. Compute Engine supports many programming languages and frameworks. However, App Engine is optimized for specific languages, such as Go, Python, Java, Node.js, PHP, and Ruby.<\/span><\/p>\n<h4><strong>Instance management<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">Instance management also varies. Compute Engine involves manual creation and control of virtual machines or instance groups. In contrast, App Engine automatically manages instances based on demand.<\/span><\/p>\n<h4><strong>Deployment and Configuration<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">Consider deployment and configuration processes. Compute Engine requires manual deployment and configuration of virtual machines. App Engine streamlines these processes, simplifying the overall development workflow<\/span><\/p>\n<h4><strong>Cost Consideration<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">Cost considerations play a role as well. Compute Engine provides flexibility in resource allocation but may require more management, leading to more predictable costs for steady usage. App Engine simplifies pricing and billing with automatic scaling, but prices can be more variable based on usage patterns.<\/span><\/p>\n<h4><strong>Use Case<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">The use case should align with your application requirements. Compute Engine is suitable for applications with specific needs or those requiring a high level of customization. At the same time, App Engine is ideal for modern web applications, scalable mobile backends, or projects prioritizing rapid development and scalability.<\/span><\/p>\n<h4><strong>Expertise Required<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">Consider the complexity and expertise required. Compute Engine demands a higher level of expertise in infrastructure management. At the same time, App Engine simplifies management. Still, it may need to be more suitable for applications with complex infrastructure needs.<\/span><\/p>\n<h4><strong>Integrations<\/strong><\/h4>\n<p><span style=\"font-weight: 400;\">Lastly, evaluate ecosystem integration. Compute Engine easily integrates with other Google Cloud services and tools. But App Engine offers seamless integration within the Google Cloud ecosystem. Carefully assessing these factors will guide your decision based on your application&#8217;s specific needs, your development team&#8217;s expertise, and your long-term goals.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Use_hands-on_labs_to_understand_the_difference\"><\/span><strong>Use hands-on labs to understand the difference<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Hands-on labs provide a straightforward way to grasp the fundamental differences between Google Compute Engine (GCE) and App Engine.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In the lab for GCE, you&#8217;ll dive into the hands-on experience of manually creating and managing virtual machines. This involves tinkering with settings such as machine types and storage configurations, giving you a feel for the platform&#8217;s granular control over infrastructure.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">On the other hand, the App Engine lab takes you through the effortless deployment of applications. Here, you won&#8217;t need to bother with the intricacies of the underlying infrastructure \u2013 the focus is on simplicity and speed in getting your applications up and running.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Here are some <\/span><a href=\"https:\/\/www.whizlabs.com\/labs\/library\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">hands-on labs<\/span><\/a><span style=\"font-weight: 400;\"> you can consider to begin learning Google&#8217;s compute engine and app engine.\u00a0<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"Connecting_MongoDB_Atlas_to_Google_Cloud_Compute_Engine\"><\/span><strong>Connecting MongoDB Atlas to Google Cloud Compute Engine<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">In this lab, our objective is to set up a Compute Engine alongside a MongoDB Atlas Cluster. The goal is to establish a connection between the Compute Engine and the MongoDB Cluster, configuring it to function as a backend database.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Task Details\u00a0<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Configure a Google Cloud Compute Engine instance.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Create a MongoDB Atlas cluster and set it up for compatibility with Google Cloud Compute Engine.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Establish a secure connection between the Compute Engine instance and the MongoDB Atlas cluster.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Test the connection from the Compute Engine to the MongoDB Atlas Cluster.<\/span><\/li>\n<\/ol>\n<h3><span class=\"ez-toc-section\" id=\"An_Overview_of_Google_Compute_Engine\"><\/span><strong>An Overview of Google Compute Engine<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">This lab guides you through the process of creating a VM instance on GCP Compute Engine, where you will set up an Ubuntu operating system with a graphical user interface (GUI).<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Task Details<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Log in to the GCP Console.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Create a VM instance.<\/span><\/li>\n<\/ol>\n<p><img decoding=\"async\" class=\"size-full wp-image-92083 aligncenter\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/GCP-Console.png\" alt=\"GCP-Console\" width=\"503\" height=\"360\" srcset=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/GCP-Console.png 503w, https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/GCP-Console-300x215.png 300w, https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/GCP-Console-150x107.png 150w\" sizes=\"(max-width: 503px) 100vw, 503px\" \/><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Access the instance through SSH.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Enable GUI mode by connecting through Remote Desktop Protocol (RDP).<\/span><\/li>\n<\/ol>\n<h3><span class=\"ez-toc-section\" id=\"Setting_up_IAP_on_Google_Compute_Engine\"><\/span><strong>Setting up IAP on Google Compute Engine<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">In this lab, we will establish a connection to a Compute Instance without utilizing an external IP address. This will be achieved through TCP protocol forwarding from IAP. To facilitate this, we&#8217;ll start by creating a new VPC network and launching an instance without an external IP. Subsequently, we will enable the IAP service to enable SSH access to the instance without the need for adding any public firewall rules from our source.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Task Details\u00a0<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Creating a VPC Network.<\/span><\/li>\n<\/ol>\n<p><img decoding=\"async\" class=\"size-full wp-image-92084 aligncenter\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/VPC-Network.png\" alt=\"VPC-Network\" width=\"714\" height=\"329\" srcset=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/VPC-Network.png 714w, https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/VPC-Network-300x138.png 300w, https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/VPC-Network-150x69.png 150w\" sizes=\"(max-width: 714px) 100vw, 714px\" \/><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Create a Compute Instance and try to SSH.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Go to the IAP service and check the SSH configuration.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Add the IAP default IP address range to a new firewall rule.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Verify the SSH access.<\/span><\/li>\n<\/ol>\n<h3><span class=\"ez-toc-section\" id=\"Leveraging_Startup_and_Shutdown_Scripts_on_Google_Compute_Engine\"><\/span><strong>Leveraging Startup and Shutdown Scripts on Google Compute Engine<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">In this lab, you will be guided on how to utilize Startup and Shutdown Scripts with Google Compute Engine.<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Log in to the GCP Console.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Create a VM Instance while implementing Startup and Shutdown Scripts.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Evaluate the functionality of the Startup and Shutdown Scripts.<\/span><\/li>\n<\/ol>\n<blockquote><p>Also Read : <a href=\"https:\/\/www.whizlabs.com\/blog\/top-google-cloud-hands-on-labs\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">Top Popular Hands on Labs for Google Cloud Platform (GCP)<\/span><\/a><\/p><\/blockquote>\n<h2><span class=\"ez-toc-section\" id=\"Summary\"><\/span><strong>Summary<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Hope this Compute Engine vs App Engine blog helps gain a holistic overview of the Google compute engine vs app engine. There is no one-size-fits-all answer for which GCP professionals should pick for their organizations. It will depend on numerous factors like the flexibility of infrastructure, the workforce&#8217;s capability, legacy software needs, and more. The best way to understand these requirements is to go for Google Cloud Platform certification, which imparts knowledge of critical components like the Compute Engine vs App Engine.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Speaking of which, <strong>Google Cloud Certified Professional Cloud Architect certification<\/strong> will help you upskill planning, building, deploying, and managing agile and secure cloud architectures on GCP. Whizlabs provides all the necessary training material to qualify for the cert exam. The detailed video lectures and practice tests will help you prepare for the exam and teach you how to use <strong>Google tools, like compute and app engines,<\/strong> to fit your organizational needs.\u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Google cloud platform (GCP) offers a broad range of services aiming to solve a plethora of user needs. Compute Engine and App Engine are two of them. These serverless computing tools allow developers to concentrate on the most crucial aspect of their work \u2013 development \u2013 without the need to concern themselves with the intricacies of infrastructure and upkeep. Additional advantages, like autoscaling, pay-as-you-go, and on-demand provisioning, make it an obvious choice for those creating stateless HTTP applications, web and mobile apps, IoT and sensor applications, data processing systems, chatbots, and more.\u00a0 But if you are new to the domain, [&hellip;]<\/p>\n","protected":false},"author":223,"featured_media":92226,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","site-sidebar-layout":"default","site-content-layout":"default","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"default","adv-header-id-meta":"","stick-header-meta":"default","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[12],"tags":[414],"class_list":["post-92081","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-google-cloud","tag-best-practices-on-gcp"],"uagb_featured_image_src":{"full":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Comparison-of-Google-Compute-Engine-vs-App-Engine-FI.webp",1280,720,false],"thumbnail":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Comparison-of-Google-Compute-Engine-vs-App-Engine-FI-150x150.webp",150,150,true],"medium":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Comparison-of-Google-Compute-Engine-vs-App-Engine-FI-300x169.webp",300,169,true],"medium_large":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Comparison-of-Google-Compute-Engine-vs-App-Engine-FI-768x432.webp",768,432,true],"large":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Comparison-of-Google-Compute-Engine-vs-App-Engine-FI-1024x576.webp",1024,576,true],"1536x1536":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Comparison-of-Google-Compute-Engine-vs-App-Engine-FI.webp",1280,720,false],"2048x2048":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Comparison-of-Google-Compute-Engine-vs-App-Engine-FI.webp",1280,720,false],"profile_24":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Comparison-of-Google-Compute-Engine-vs-App-Engine-FI.webp",24,14,false],"profile_48":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Comparison-of-Google-Compute-Engine-vs-App-Engine-FI.webp",48,27,false],"profile_96":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Comparison-of-Google-Compute-Engine-vs-App-Engine-FI.webp",96,54,false],"profile_150":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Comparison-of-Google-Compute-Engine-vs-App-Engine-FI.webp",150,84,false],"profile_300":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Comparison-of-Google-Compute-Engine-vs-App-Engine-FI.webp",300,169,false],"tptn_thumbnail":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Comparison-of-Google-Compute-Engine-vs-App-Engine-FI-250x250.webp",250,250,true],"web-stories-poster-portrait":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Comparison-of-Google-Compute-Engine-vs-App-Engine-FI-640x720.webp",640,720,true],"web-stories-publisher-logo":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Comparison-of-Google-Compute-Engine-vs-App-Engine-FI-96x96.webp",96,96,true],"web-stories-thumbnail":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2023\/11\/Comparison-of-Google-Compute-Engine-vs-App-Engine-FI-150x84.webp",150,84,true]},"uagb_author_info":{"display_name":"Dharmendra Digari","author_link":"https:\/\/www.whizlabs.com\/blog\/author\/dharmendrawhizlabs-com\/"},"uagb_comment_info":6,"uagb_excerpt":"Google cloud platform (GCP) offers a broad range of services aiming to solve a plethora of user needs. Compute Engine and App Engine are two of them. These serverless computing tools allow developers to concentrate on the most crucial aspect of their work \u2013 development \u2013 without the need to concern themselves with the intricacies&hellip;","_links":{"self":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts\/92081","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/users\/223"}],"replies":[{"embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/comments?post=92081"}],"version-history":[{"count":6,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts\/92081\/revisions"}],"predecessor-version":[{"id":92225,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts\/92081\/revisions\/92225"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/media\/92226"}],"wp:attachment":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/media?parent=92081"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/categories?post=92081"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/tags?post=92081"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}