diff --git a/docs/en/enterprise-edition/policy-reference/aws-policies/aws-logging-policies/bc-aws-logging-11.adoc b/docs/en/enterprise-edition/policy-reference/aws-policies/aws-logging-policies/bc-aws-logging-11.adoc
index 83d7bf256c..41b806271f 100644
--- a/docs/en/enterprise-edition/policy-reference/aws-policies/aws-logging-policies/bc-aws-logging-11.adoc
+++ b/docs/en/enterprise-edition/policy-reference/aws-policies/aws-logging-policies/bc-aws-logging-11.adoc
@@ -50,7 +50,7 @@ and for new clusters, you use either the Amazon ECS console, or the AWS CLI.
 
 . In the navigation pane, choose * Account Settings*.
 
-. To enable the Container Insights default opt-in, check the box at the bottom of the page.
+. To enable the Container Insights (or Container Insights with enhanced observability) default opt-in, check the box at the bottom of the page.
 
 
 * CLI Command* 
@@ -61,7 +61,7 @@ To do so, enter the following command.
 ----
 aws ecs put-account-setting
 --name "containerInsights"
---value "enabled"
+--value "enabled" # OR "enhanced"
 ----
 ////
 
@@ -82,7 +82,7 @@ resource "aws_ecs_cluster" "foo" {
   name = "white-hart"
 + setting {
 +   name  = "containerInsights"
-+   value = "enabled"
++   value = "enabled" # OR "enhanced"
 + }
 }
 ----
@@ -104,5 +104,5 @@ Resources:
       ...
 +     ClusterSettings:
 +       - Name: 'containerInsights'
-+         Value: 'enabled'
++         Value: 'enabled' # OR 'enhanced'
 ----