AWS Cloud Operations & Migrations Blog

Category: Advanced (300)

Centralized multi-account and multi-Region patching with AWS Systems Manager Automation

Update 01/2023: AWS Systems Manager announces Patch Policies, enabling cross account and cross Region patching. Patch Policies provide a user experience in a single console to easily define and enforce patch compliance across accounts and Regions with a few clicks. For more information, see Centrally deploy patching operations across your AWS Organization using Systems Manager […]

Monitor tag changes on AWS resources with serverless workflows and Amazon CloudWatch Events

Introduction Amazon CloudWatch Events now supports tag changes on AWS resources. Using this new CloudWatch Event type, you can build CloudWatch event rules to match tag changes and route them to one or more targets like an AWS Lambda function to trigger automated workflows. In this blog post, I’ll provide an example for using AWS […]

Building a portfolio of self-service databases with AWS Service Catalog and AWS CloudFormation

Modern distributed applications are moving towards a “purpose-built” database strategy. This means that the selection of database type, size, and configuration should match the problem the database is trying to solve. AWS customers are also requiring that these databases have the appropriate level of security control and organizational governance to operate in customer environments. AWS […]

Resolving circular dependency in provisioning of Amazon S3 buckets with AWS Lambda event notifications

Overview AWS CloudFormation provides a common language for you to describe and provision all of the infrastructure resources in your cloud environment. CloudFormation allows you to use a simple text file to model and provision, in an automated and secure manner, all the resources needed for your applications across all AWS Regions and accounts. It […]

Create a security partition for your applications using AWS Service Catalog and AWS Lambda

Some of the customers I work with want to create complete application separation for each application. They don’t want any two applications running on AWS to communicate using APIs or to network with each other’s AWS resources. In other words, they want each application to “stay in its own lane” as competitive swimmers do. In […]