All Things Patch: AWS Systems Manager | AWS Events

In this video, we will demonstrate how you can quickly enable patching operations at scale across your AWS accounts and Regions within your AWS Organization using AWS Systems Manager. You can enable patching operations for Amazon Elastic Compute Cloud (EC2) instances, edge devices, on premises servers, and virtual machines (VMs) in other cloud environments. Additionally, we will demonstrate how you can enable patch compliance reporting and create patch compliance dashboards using Amazon Athena and Amazon QuickSight.
You will learn how to
-Perform patching operations on Systems Manager managed nodes
-Setup standard patch scan and patch install operations across your AWS accounts and Regions
-Create a patch compliance reporting dashboard
Feature topics
-AWS Systems Manager
-Amazon Athena
-Amazon QuickSight
Learn more at: go.aws/45WPcIi
Subscribe:
More AWS videos: bit.ly/2O3zS75
More AWS events videos: bit.ly/316g9t4
ABOUT AWS
Amazon Web Services (AWS) hosts events, both online and in-person, bringing the cloud computing community together to connect, collaborate, and learn from AWS experts. AWS is the world’s most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally. Millions of customers-including the fastest-growing startups, largest enterprises, and leading government agencies-are using AWS to lower costs, become more agile, and innovate faster.
#AWS #CloudOps #AWSEvents

[@AloisioBilck]

What is the point of the workshop if it would be to show the use of AWS Systems Manager in the Organization, but it only shows one account and one region!
Use an environment that allows you to show how an Organization works.

[@RABWA333]

good explanation guys and things are clear now . on my end the association status fails most of the time for some reason, the multi-organization setup fails to start, Im not sure if I have to create the cross-account role first, also I see what I can consider a bug , when first crated patch policy, then I deleted it because of naming convention I follow and created a new one with the correct name , then in the compliance report I you will see the old name alongside with the new name which is quite confusing and no need to see that policy I deleted, even If I run a new patch , I still see the old name

[@cocnitive]

Nice

[@vivekkadam-vv7eq]

I did not get success status after I did association now option 1:40:00

[@awssupport]

Hi Vivek. We would suggest asking your detailed question to our helpful community at re:Post. You can reach out to them through this link, here: go.aws/aws-repost. ^ZP