Skip to content

Commit fdbafa0

Browse files
Update README.md
1 parent 0190308 commit fdbafa0

File tree

1 file changed

+2
-2
lines changed
  • aws_sra_examples/solutions/patch_mgmt/patch_mgmt_org

1 file changed

+2
-2
lines changed

aws_sra_examples/solutions/patch_mgmt/patch_mgmt_org/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ Choose to deploy the Patch Manager solution from within the chosen deployment ty
130130

131131
### Viewing Node Compliance<!-- omit in toc -->
132132

133-
Navigate to 'Systems Manager' then 'Patch Manager'. From the Dashboard select the 'Compliance Reporting' tab. This will show you all your managed instances, the Compliance Status, and the Non-Compliant Count of patches.
133+
Navigate to `Systems Manager` then `Patch Manager`. From the Dashboard select the `Compliance Reporting` tab. This will show you all your managed instances, the Compliance Status, and the Non-Compliant Count of patches.
134134

135135
![Node-Compliance](./documentation/node-compliance.png)
136136

@@ -145,7 +145,7 @@ Selecting the link on Non-Compliant Count will show you the missing patches for
145145

146146
## Troubleshooting<!-- omit in toc -->
147147

148-
Q: Its been more than 24 hours and the Instances are still not appearing in Fleet Manager (and therefore not being scanned).
148+
Q: Its been more than 24 hours and the Instances are still not appearing in Fleet Manager (and therefore not being scanned).\
149149
A: Attach the `patch-mgr-ec2-profile` to the EC2 instances.
150150

151151
---

0 commit comments

Comments
 (0)