AWS Config vs. Azure Cloud Services

It's really good if your infrastructure services is all in AWS, that means everything could be audited and monitored using AWS config. You also can create alarms to notify you or your team about any changes on your AWS resources which is very useful to prevent abuse if you have a fairly large team. It's also very useful whenever some third party wants to audit your AWS resources, if you have a fairly comprehensive AWS config configured, the auditing process will be easy since they only need to look at your AWS config setup.

Incentivized

Microsoft Azure Cloud services is a good choice for hosting web applications, based on requirements it can be simple websites or complex web services as well as it provides automating application development and deployment pipeline. It's less appropriate in case of cost-effective option for organizations with tight budget constraints. For very basic static websites, Microsoft Azure's offerings might be seen as overkill.

• The ability to track changes in AWS is paramount, AWS config allows you to do this
• Allows the auditing of an AWS account
• Can view history of an account that has AWS config enabled

Incentivized

• Effective service management and performance monitoring capability.
• Reliable security management with excellent access controls.
• Best orchestration and easy configuration management.
• Easy on compatibility testing and change management.

• It's only AWS, no third party.
• Not the most intuitive interface, but with a little getting used to it is OK.

Incentivized

• Latency and bandwidth as we often see gap here
• There were many challenges as a developer while migrating our DB from on prem to cloud
• System downtime is also one issue that can be improved

Incentivized

As a certificate developer and consultant, I love using Azure, it's interface is developer friendly with well guidance and support. Also there are a lot of service for any work, Azure ecosystem is sufficient to complete your all developments needs. So based on that I feel Azure is good and gives better developer experience.

Incentivized

Would rate lower for other workloads but for AWS workloads its simple to set up, cost effective and customisable. Primary use case is compliance from a governance perspective.

Incentivized

I do not know or have used any other product in AWS cloud space that matches what AWS Config provides. We have some custom built monitoring and governance, however that is there because AWS Config does not provide it currently.

Incentivized

I feel AWS offers a robust and versatile platform for cloud infrastructure and services. It's scalability, reliability array of tools make it a top choice for businesses of all sizes. AWS has better open source communities such as Linux, Jenkins and GitHub in comparison to Azure service cloud

• Enforcing audit requirements
• Easy to set up alerting when there are rule breaches
• Auto remediation reduces the manual policing of such breaches

Incentivized

• Azure's services and automation capabilities contribute to operational efficiency.
• Azure's scalability ensures optimal performance during peak demand periods and cost savings during off-peak times