Google Cloud Platform Cloud Identity-Aware Proxy Reviews

I use Google Cloud Platform Cloud Identity-Aware Proxy in my company for BNB Chain.

The most valuable feature of the solution is that it is a very simple solution. Google Cloud Platform Identity-Aware Proxy is cheaper than AWS and allows users to keep tabs on factors like location and timelines.

I think the product is easy to use on any server. If I want to use the product or open it on other systems, I think it's very easy.

The UI of the solution is an area with certain shortcomings where improvements are required. The product needs to be made user-friendly.

I have been using Google Cloud Platform Cloud Identity-Aware Proxy for two or three years.

It is a very stable solution. Stability-wise, I rate the solution a ten out of ten.

It is a scalable solution.

Around three people in my company, consisting of the cloud manager and cloud engineer, use the product to set up a website.

I think that the product's initial setup phase was straightforward.

Not many steps are required to take care of the deployment phase of the product. In a few steps, one can finish the deployment of the product.

Two engineers are required to take care of the deployment and maintenance processes of the product.

The solution can be deployed in ten minutes.

The solution can be deployed by myself in my company.

I wouldn't recommend the product to other users.

I rate the overall tool a ten out of ten.

The product helps to connect VMs and servers. 

I am impressed with the product's security. 

The solution should be more user-friendly and should have descriptive manuals on the page website. 

I have been using the product for one and a half years. 

The product is stable. 

My company has more than 10 users for the solution. 

The solution's price is normal. 

I would rate the product a nine out of ten. 

We use the solution for data engineering, data preparation, and AI.

The tool is really good, especially for ease of implementation and having many options. We can build complex data pipelines and AI models, like web-based AI assistants or chatbots.

Google Cloud Platform Cloud Identity-Aware Proxy should improve stability. 

I rate the tool's stability a nine out of ten. 

My company has 10-15 users. 

Support is good, and there is lots of material available online. We usually don't need to call someone, but if we do, it's okay.

straightforward to set up and easy to learn. There are lots of training materials and hands-on labs, making it easy to onboard new team members. Our engineers really like the platform.

There are different pricing plans depending on data volumes and services, but it's comparable to other providers. The value and benefits depend on what we're developing and the specific use case.

I rate Google Cloud Platform Cloud Identity-Aware Proxy an eight out of ten. I'd recommend it. We use both Azure and GCP, and they're both really good. It depends on client preference.

We use the product to migrate the data from the center to the cloud.

The platform’s most valuable features include storage, machine, and cloud functionality.

The product’s migration process could be easier to understand.

We have been using Google Cloud Platform Cloud for two to three years.

The platform has good stability.

It is a scalable product. Yet, the complexity depends on the amount of data and workload.

Google has good technical support services.

The initial setup process is straightforward.

I rate Google Cloud Platform Cloud an eight out of ten.

Our use case is to plug platforms, especially applications that are 
based on website micro services such as containers. 

From our perspective this is a good solution that functions well and has good features. 

We are based in France and it's difficult to find people with sufficient training to assist us. I'd like to see companies with the right level of expertise to help my customers to move their projects from the traditional information system or infrastructures on premise to cloud but it's very difficult to find that here. Google is not well supported in France. 

The initial setup was not so easy. The average deployment time is between one and two years. It requires an initial feasibility study to understand the scope. Once that's established you need to find the path to help set up the right security parameters. The migration is done through scripting and codes. The deployment requires project managers and engineers.

I recommend this solution but it's important to find the right partner and be sure you have a suitable use case. I rate this solution eight out of 10. 

The most valuable features of Google Cloud Platform are the Kubernetes engine, CI/CD, and BigQuery. 

Apigee is a good feature because we analyzed and changed the computer-associated AP to Apigee. We compared the features and created the clusters to change the solution to Apigee. It's a good option on the Google Cloud Platform. And I like BigQuery, which is a fantastic database on the SaaS model. The hard part is creating the pack because our applications are in Azure Data Proxy, Data Fabric, and Data Factory. Our team used these tools in Azure, but in the future, they will transition to GCP.

I've been using Google Cloud Platform for one year.

Google support is outstanding. It's effortless to contact Google engineers, who are all Brazilians. The work is well explained, and they participate in our technical meetings. 

I think the price of Google Cloud Platform is reasonable. However, Microsoft is the most cost-effective solution for us because of Azure's integration. And we already have licenses for Windows Server and the databases, so the price is attractive. And the price of AWS is higher, but we have only two big applications on the AWS. Still, I like Google so much, and my company thinks GCP is the best way to handle our workloads.

I rate Google Cloud Platform nine out of 10. I like the GCP so much because it's flexible. We have tools for similar tech drivers, and we can connect them in the other clouds, where I use the Anthos platform. I created an Anthos platform for similar tech drivers to administer all of the different cloud solutions on the same platform. So, for example, I can put the comments on Cloud Shell and create a resource in the other clouds.

I use Google Cloud IAP to secure my applications by verifying user identities.

I like Google Cloud IAP because it is easy to use and stable.

As an individual developer, I would like Google Cloud IAP to offer more flexibility, especially for smaller-scale usage.

I have been using  Google Cloud IAP for seven years.

I would rate the stability as a nine out of ten.

The support is very good.

I have previously used AWS, but Google is my preferred option.

I would recommend Google Cloud IAP for those starting, especially for individuals or smaller projects. While larger enterprises might lean towards AWS, I have found Google Cloud to be effective for my needs. Overall, I would rate Google Cloud IAP as a nine out of ten.

For Google Cloud Platform (GCP), we use it as our infrastructure. We host our infrastructures and create our machines, services and automation pipelines. For Google Cloud Identity, we use it as an identity portal for all of our applications. In addition, the internal application for the tools is used for monitoring the product.

The Cloud Identity in GCP is very good and reliable. It can be published fast. Also, Google Cloud Identity allows you to create groups and give access by group instead of by user. It allows you to create different access policies for every component of new infrastructure, and from a security perspective, this is good.

The Google Cloud UI has a lot of bugs, and they are working on enhancing it. There are a lot of things that need to be enhanced. For example, sometimes, the snapshot portal makes you have a schedule to create multiple snapshots when you have a huge infrastructure hosted on Google Cloud. Sometimes the browser or the UI hangs when looking for a specific snapshot. Also, Google Cloud support responds very quickly, but the UI still needs to have more enhancements related to the performance.

The integration of the solution for patching, updating, and installing the updates could be better. For example, they have a solution called "always patching," which needs to be enhanced. It is not purely a SaaS solution. It should be mostly platform as a solution, not software.

We have been using this solution for more than two years.

It is a stable solution. However, it would be more stable if Google cared more about the UI.

It is a scalable solution. Most of the teams in our company use this solution. The number of people needed for deployment and maintenance depends on whether it is a small or medium company solution. Only one person is needed for a small environment, while two or three are required for a medium environment. The team that supports the solution comprises network and security people. We plan to increase our usage of the solution as our customer base increases.

The technical support is good, and they are very responsive. I rate the technical support an eight out of ten.

I personally have used Azure and AWS in the past.

The initial setup was easy, and it was just plug-and-play. If you have a good understanding of infrastructure, this solution is perfect. It allows us to build an entire infrastructure for a startup or medium company in one hour. To do this, we need to try the script with the machines we need. Next, we need to define the CPU, memory and application we want to install on the machine. Then we can click and run the playbook or the tier forms script and go back after hours. By then, everything has been created, and we'll have an infrastructure that can handle a small startup.

The deployment depends on the complexity. If it is a small deployment, it might take less time, but a larger deployment will take more. For example, if we want to use a machine on GCP, it might take about two to three minutes, but if we have a huge deployment for multiple machines with multiple loop balances, records, and firewall rules, it might take 40 minutes to one hour. We completed the deployment in-house.

I rate this solution an eight out of ten. Regarding advice, I would recommend planning for everything and keeping it simple. It is also important to monitor consumption on the Google Cloud to ensure you are not paying for something you are not using.

Most cloud providers have the same features, but the main difference between them is the solution's availability and cost. Most of the features are only utilized at 30% or 50%.