Google Cloud Platform Cloud Identity-Aware Proxy Reviews

The solution can be used for building the infrastructure on the cloud.

The solution's security should be improved.

I have been working with Google Cloud Platform Cloud Identity-Aware Proxy for a few months.

The solution's stability seems good.

Google Cloud Platform Cloud Identity-Aware Proxy is a scalable solution.

Before Google Cloud Platform Cloud Identity, I worked with AWS and Azure. I switched to Google Cloud Platform Cloud Identity because of the client's needs.

Google Cloud Platform Cloud Identity-Aware Proxy is a cloud-based solution.

Overall, I rate the solution a seven out of ten.

We use the solution for continuous integration and deployment of applications on databases.

The solution's most valuable features are Google domains, UI setup, easy server access, and intuitive dashboards.

The solution's naming conventions feature needs improvement. We encounter issues while setting up emails as well. They should improve this particular area. Also, they should integrate the solution with more applications.

I have been using the solution for six months.

The solution's stability is good.

We have five solution users in our organization. It is expensive to scale up the solution.

The solution's initial setup was fine. However, it took a lot of work to name the features. The process involves setting up the server, connecting to the gateway, and setting up user access and security codes.

The implementation of the solution was done natively on the platform.

The solution generates a good return on investment.

We pay for the solution’s compute engine every month.

I rate the solution as an eight. I advise others to go through the documentation before deploying it. They can set up a small cluster to practice before implementing it.

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.

This is a service. We use it for our business, for operations. 

This can be deployed easily. 

The solution is stable. It's reliable. 

There is good documentation available. There is a lot of information available online to help new users. 

It is hard to find expertise, ad most people deal with AWS. 

The solution is quite expensive. 

We'd like the solution to continue to make security features more robust. We need to protect against data leaks and also need to protect customer information. 

We've been using the solution for less than a year now. We're a new company.

This is a stable, reliable product. It does not have bugs or glitches. It doesn't crash or freeze. 

We're a new company. This solution hasn't been used for too long, and we haven't really launched anything yet. Right now, it is still just internally dealt with. Likely less than 100 people deal with it right now. 

The support could be better. There needs to be more knowledgeable. It could be that there aren't enough people with a good knowledge base in our country. Most people are comfortable with AWS, and not necessarily with GCP. However, I don't typically deal with technical support. 

We also use AWS, which is what most companies use. 

The solution is very easy to set up and deploy. It's not a complex process. We can easily deploy applications, APIs, et cetera. However, I did not handle the initial setup myself and therefore cannot speak from firsthand experience. 

We do find it to be more expensive than AWS. 

I'm not sure what version of the solution we're using. 

I'd recommend the solution to others. There's not a problem with deploying it. The business decision comes more about the deployment and support costs and if that makes sense to everyone in the company. It's higher than AWS, which is something that needs to be considered, especially since most people are more familiar with AWS. 

I'd rate the solution eight out of ten. It's well documented and does have available support. 

We are a customer and end-user. 

The solution should have better integration. 

The solution is stable. 

The solution is scalable.

The technical support is up to par. 

As with AWS, the solution is easy to install. 

50 or 60 days are needed for the deployment. 

Around three or four people are needed for the deployment and maintenance. 

The customer purchases an annually sponsored license. 

We have a maximum of around 20 customers making use of the solution. 

We support Azure, AWS and Google Cloud Platform Cloud Identity-Aware Proxy, depending on the customer's architecture. 

For the most part, I would not recommend the solution to others, as our expertise is more with AWS and Azure.

I rate Google Cloud Platform Cloud Identity-Aware Proxy as an eight 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%.

We use GCP for many resources, including Google Kubernetes cluster (GK), monitoring with Stackdriver and Work Explorer, Cloud Insight, Cloud Storage for backup, Container Registry, VPC, complete VM, Memory Store, and Redis. We also use Robitankyo and the message query.

For me, the most valuable feature is JKS and Kubernetes Cluster on managed service. Moreover, the latest versions of the managed Kubernetes clusters are good. 

There is room for improvement. For instance, we encountered some issues with a potential cluster on GCP last month. Although we use GCP for all our resources, we experienced some difficulties. So, I think this aspect needs to be addressed and improved upon. And from what I can tell, GCP is working on addressing this issue.

I have been using this solution for two years. 

I would rate the stability a seven out of ten. 

I would rate the scalability of the solution an eight out of ten. 

We used global IT for the support. 

Overall, I would rate the solution an eight out of ten. 

 I'm working with GCP, managing approximately 15 GCP clusters on Kubernetes. I have strong experience with Google Cloud and am a solution architect on AWS.

It's a cloud-based solution, so it's always the latest version. We use it for identity management, monitor resources, and to monitor the cloud resources. The number of users are small, but the number of resources being managed is large. We plan to roll it out to about 30,000 people.

There is a certain accessibility feature that I can set using a cloud identity, which is really valuable to us.

I think that the documentation could be a bit better in terms of what is presented on the screen versus what actually happens. There's a little bit of confusion under your resource discovery you get in a search bar having to do with the level of complexity of the product design. But I think the documentation could be better.

We have been using Google Cloud Platform Cloud Identity-Aware Proxy for about a year.

It is very stable.

It scales well, in fact, it's quite relevant. We've not put it to an extreme level of scale, but we use it at a medium level of scalability. It's working well.

Google's technical support is really good. In fact, I've only been in touch through email and they've been really responsive. In fact, most of our responses happen in minutes.

The setup is straightforward. I don't think it's a function of how long it takes to set up. it's a continuous deployment. At the time it was a new resource that has to be reconfigured. The initial set up was a few days, but after that its incremental changes that we do.

We've evaluated Microsoft.

I would rate Google Cloud Platform Cloud Identity-Aware Proxy at an eight out of ten.