Operations | Monitoring | ITSM | DevOps | Cloud

Being alerted to an issue with your application before your customers experience undue interruption is a goal of every development and operations team. While methods for identifying problems exist in many forms, including uptime checks and application tracing, alerts on logs is a prominent method for issue detection. Previously, Cloud Logging only supported alerts on error logs and log-based metrics, but that was not robust enough for most application teams.

AWS Step Functions is a powerful orchestration service that lets you model even the most complex business workflows. It packs a great visualization tool (which you can also use to design your workflows visually now!) and can integrate with many AWS services directly, including Lambda, DynamoDB, and API Gateway. It’s one of my favorite AWS services and I often use it to model complex or business-critical workflows.

For a successful cloud migration, creating (and later refining), a cloud migration strategy tailored to your organization’s goals, available resources, workloads, and priorities is an absolute necessity. So here, we’ll take a look at a simple list of the areas you’ll need to quantify and understand to build that strategy and then improve it as you move forward through the cloud migration process.

Governance, risk, and compliance (GRC) are major inhibitors for organizations moving to the cloud—and for good reason. Cloud environments are complex, and even a single misconfigured security group can result in a serious data breach. In fact, misconfigurations were the leading cause of cloud security breaches in 2020. This puts a lot of pressure on developer and operations teams to properly secure their services and maintain regulatory compliance.