AWS Certificate Manager vs. Google Cloud DNS

I would always recommend AWS Certificate Manager for anyone using AWS cloud services. The perfect scenario would be with your domain managed by AWS Route 53 as you can obtain auto renewal of certificates with really good security for all your public facing application that uses CloudFront, ALB or API Gateway.

Incentivized

Google cloud is well suited to access and collaborate on documents where more than 2 people are required to contribute and in instances where feedback from individuals is captured on the document itself. If a team is working on an end of year report for funders, a few key members may need to finalise a report by offering suggestions that can be viewed and resolved by other team members. Housing documents on Google Cloud is the most appropriate platform I have ever used for tasks like these. If minimal collaboration needs engagement from just 2 individuals, it may be easier to simply email the information between each other, rather than using time to create a folder, ensure access control and upload the information to Google Cloud for collaborative input

Incentivized

• Issue, Renew and Validate SSL Certificates.
• Allows us to integrate it with other AWS Services.

• Interface is user friendly
• It is safe , Secure and reliable
• It has lower pricing plans
• They have good customer support
• They do have good documentation to have fair ideas on their offerings

Incentivized

• Sometimes ACM certificates don't work with ELB.
• No automatic alert on certificate expiration.

Incentivized

• It is hard for first time user to get used to it.
• Support is restricted for 3rd party services who uses it
• Sometimes the support people take more than 24hrs to reply to our queries, But it is not for all issues.
• Search function could have been made easy to search records

Incentivized

AWS historically has had very confusing interfaces. But in recent times they have improved them. AWS Certificate Manager is a clear sample of this. The interface is clear and straightforward, with no useless or cryptic options. Really I can't think of a way the interface could be better with the actual options available.

Incentivized

This is exceptionally simple to utilize in the event that you are as of now utilizing Google Cloud Services or you are important for the Google Ecosystem as of now. I accept this is likely the primary goal of Google Cloud DNS, to give a more complete set-up of devices to Google Cloud clients. Consequently, I would rate convenience a 9.

They do a great job.

Incentivized

In the event that you are utilizing Google Cloud Platform as your cloud supplier, Google Cloud DNS is unquestionably the DNS supplier to utilize.

I haven't required help for it yet, notwithstanding, in my experience, Google Support is incredible.

Easy to implement within a few clicks, or even from command line, the alternatives doesn't integrate that easy with AWS Application Load Balancers or AWS CloudFront

Incentivized

Amazon Route 53 offers almost equal or slightly more features than Google Cloud DNS; we selected Google Cloud DNS because the rest of our projects use Google Cloud Platform.

Also, since AWS is a bigger service provider, their pricing is also higher; since Google Cloud DNS pricing is better, we went for it.

Incentivized

• We're saving our spent on SSL certificates As it dosen't costs at all.
• Limited to AWS only, Certificates issued by ACM can be used with AWS managed services only.
• It doesn't support automatic domain verification with other DNS management systems.

• We use GCP for all our projects so Google Cloud DNS fits perfectly
• It is proving to scale well so good for us since we are a growing company
• It is easy to use and doesn't require a separate team to maintain

Incentivized