Update to version v2.1.1

Author: James Ma

CHANGELOG.md

@@ -5,6 +5,14 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.1.1] - 2023-12-05
+
+### Fixed
+
+- Fixed the issue that Log ingestion error in light engine when not specified time key in the log config #220
+- Fixed the issue that cannot deploy the Centralized Logging with OpenSearch solution in UAE region #221
+- Fixed the issue that EC2 instances should not be added to the same Instance Group #228
+
 ## [2.1.0] - 2023-11-15
 
 ### Added

docs/en/implementation-guide/applications/ec2-pipeline.md

@@ -73,7 +73,9 @@ You have created a log source for the log analytics pipeline. Now you are ready
 
 7. In the **Log Lifecycle** section, enter the number of days to manage the Amazon OpenSearch Service index lifecycle. The Centralized Logging with OpenSearch will create the associated [Index State Management (ISM)](https://opensearch.org/docs/latest/im-plugin/ism/index/) policy automatically for this pipeline.
 
-8. Choose **Next**.
+13. In the **Select log processor** section, please choose the log processor. 
+    - (Optional) OSI as log processor is now supported in these [regions](https://aws.amazon.com/about-aws/whats-new/2023/04/amazon-opensearch-service-ingestion/). When OSI is selected, please type in the minimum and maximum number of OCU. See more information [here](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/ingestion.html#ingestion-scaling). 
+14. Choose **Next**.
 
 9. Enable **Alarms** if needed and select an exiting SNS topic. If you choose **Create a new SNS topic**, please provide a name and an email address for the new SNS topic.
 

docs/en/implementation-guide/applications/eks-pipeline.md

@@ -62,7 +62,9 @@ You have created a log source for the log analytics pipeline. Now you are ready
 
 7. In the **Log Lifecycle** section, enter the number of days to manage the Amazon OpenSearch Service index lifecycle. The Centralized Logging with OpenSearch will create the associated [Index State Management (ISM)](https://opensearch.org/docs/latest/im-plugin/ism/index/) policy automatically for this pipeline.
 
-8. Choose **Next**.
+13. In the **Select log processor** section, please choose the log processor. 
+    - (Optional) OSI as log processor is now supported in these [regions](https://aws.amazon.com/about-aws/whats-new/2023/04/amazon-opensearch-service-ingestion/). When OSI is selected, please type in the minimum and maximum number of OCU. See more information [here](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/ingestion.html#ingestion-scaling). 
+14. Choose **Next**.
 
 9. Enable **Alarms** if needed and select an exiting SNS topic. If you choose **Create a new SNS topic**, please provide a name and an email address for the new SNS topic.
 

docs/en/implementation-guide/applications/syslog-pipeline.md

@@ -56,7 +56,9 @@ You have created a log source for the log analytics pipeline. Now you are ready
 
 7. In the **Log Lifecycle** section, enter the number of days to manage the Amazon OpenSearch Service index lifecycle. The Centralized Logging with OpenSearch will create the associated [Index State Management (ISM)](https://opensearch.org/docs/latest/im-plugin/ism/index/) policy automatically for this pipeline.
 
-8. Choose **Next**.
+13. In the **Select log processor** section, please choose the log processor. 
+    - (Optional) OSI as log processor is now supported in these [regions](https://aws.amazon.com/about-aws/whats-new/2023/04/amazon-opensearch-service-ingestion/). When OSI is selected, please type in the minimum and maximum number of OCU. See more information [here](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/ingestion.html#ingestion-scaling). 
+14. Choose **Next**.
 
 9. Enable **Alarms** if needed and select an exiting SNS topic. If you choose **Create a new SNS topic**, please provide a name and an email address for the new SNS topic.
 

docs/en/implementation-guide/aws-services/cloudtrail.md

@@ -19,7 +19,9 @@ You can create a log ingestion into Amazon OpenSearch Service either by using th
 10. Choose **Yes** for **Sample dashboard** if you want to ingest an associated built-in Amazon OpenSearch Service dashboard.
 11. You can change the **Index Prefix** of the target Amazon OpenSearch Service index if needed. The default prefix is your trail name.
 12. In the **Log Lifecycle** section, enter the number of days to manage the Amazon OpenSearch Service index lifecycle. Centralized Logging with OpenSearch will create the associated [Index State Management (ISM)](https://opensearch.org/docs/latest/im-plugin/ism/index/) policy automatically for this pipeline.
-13. Choose **Next**.
+13. In the **Select log processor** section, please choose the log processor. 
+    - (Optional) OSI as log processor is now supported in these [regions](https://aws.amazon.com/about-aws/whats-new/2023/04/amazon-opensearch-service-ingestion/). When OSI is selected, please type in the minimum and maximum number of OCU. See more information [here](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/ingestion.html#ingestion-scaling). 
+14. Choose **Next**.
 14. Add tags if needed.
 15. Choose **Create**.
 

docs/en/implementation-guide/aws-services/elb.md

@@ -27,7 +27,9 @@ You can create a log ingestion into Amazon OpenSearch Service or Light Engine ei
 9. Choose **Yes** for **Sample dashboard** if you want to ingest an associated templated Amazon OpenSearch Service dashboard.
 10. You can change the **Index Prefix** of the target Amazon OpenSearch Service index if needed. The default prefix is the `Load Balancer Name`.
 11. In the **Log Lifecycle** section, input the number of days to manage the Amazon OpenSearch Service index lifecycle. The Centralized Logging with OpenSearch will create the associated [Index State Management (ISM)](https://opensearch.org/docs/latest/im-plugin/ism/index/) policy automatically for this pipeline.
-12. Choose **Next**.
+13. In the **Select log processor** section, please choose the log processor. 
+    - (Optional) OSI as log processor is now supported in these [regions](https://aws.amazon.com/about-aws/whats-new/2023/04/amazon-opensearch-service-ingestion/). When OSI is selected, please type in the minimum and maximum number of OCU. See more information [here](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/ingestion.html#ingestion-scaling). 
+14. Choose **Next**.
 13. Add tags if needed.
 14. Choose **Create**.
 

docs/en/implementation-guide/aws-services/vpc.md

@@ -24,7 +24,9 @@ You can create a log ingestion into Amazon OpenSearch Service either by using th
  10. Choose **Yes** for **Sample dashboard** if you want to ingest an associated built-in Amazon OpenSearch Service dashboard.
  11. You can change the **Index Prefix** of the target Amazon OpenSearch Service index if needed. The default prefix is your VPC name.
  12. In the **Log Lifecycle** section, enter the number of days to manage the Amazon OpenSearch Service index lifecycle. The Centralized Logging with OpenSearch will create the associated [Index State Management (ISM)](https://opensearch.org/docs/latest/im-plugin/ism/index/) policy automatically for this pipeline.
- 13. Choose **Next**.
+13. In the **Select log processor** section, please choose the log processor. 
+    - (Optional) OSI as log processor is now supported in these [regions](https://aws.amazon.com/about-aws/whats-new/2023/04/amazon-opensearch-service-ingestion/). When OSI is selected, please type in the minimum and maximum number of OCU. See more information [here](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/ingestion.html#ingestion-scaling). 
+14. Choose **Next**.
  14. Add tags if needed.
  15. Choose **Create**.
 

docs/en/implementation-guide/aws-services/waf.md

@@ -32,7 +32,9 @@ You can create a log ingestion into Amazon OpenSearch Service or Light Engine ei
 10. Choose **Yes** for **Sample dashboard** if you want to ingest an associated templated Amazon OpenSearch Service dashboard.
 11. You can change the **Index Prefix** of the target Amazon OpenSearch Service index if needed. The default prefix is the `Web ACL Name`.
 12. In the **Log Lifecycle** section, enter the number of days to manage the Amazon OpenSearch Service index lifecycle. The Centralized Logging with OpenSearch will create the associated [Index State Management (ISM)](https://opensearch.org/docs/latest/im-plugin/ism/index/) policy automatically for this pipeline.
-13. Choose **Next**.
+13. In the **Select log processor** section, please choose the log processor. 
+    - (Optional) OSI as log processor is now supported in these [regions](https://aws.amazon.com/about-aws/whats-new/2023/04/amazon-opensearch-service-ingestion/). When OSI is selected, please type in the minimum and maximum number of OCU. See more information [here](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/ingestion.html#ingestion-scaling). 
+14. Choose **Next**.
 14. Add tags if needed.
 15. Choose **Create**.
 

docs/en/implementation-guide/domains/import.md

@@ -4,7 +4,7 @@ Once logged into the Centralized Logging with OpenSearch console, you can import
 
 ## Prerequisite
 
-1. Centralized Logging with OpenSearch supports Amazon OpenSearch Service, engine version Elasticsearch 7.10 or later, and engine version OpenSearch 1.0 or later.
+1. Centralized Logging with OpenSearch supports Amazon OpenSearch Service, and engine version OpenSearch 1.3 or later.
 2. Centralized Logging with OpenSearch supports OpenSearch clusters within VPC. If you don't have an Amazon OpenSearch Service domain yet, you can create an Amazon OpenSearch Service domain within VPC. See [Launching your Amazon OpenSearch Service domains within a VPC][vpc].
 3. Centralized Logging with OpenSearch supports OpenSearch clusters with [fine-grained access control](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/fgac.html) only. In the security configuration, the Access policy should look like the image below:
    ![](../../images/domain/policy.png)

docs/en/implementation-guide/faq.md

@@ -60,7 +60,7 @@ The Centralized Logging with OpenSearch console is served via CloudFront distrib
 to the local regulations, any Internet information service must bind to a domain name with [ICP recordal](https://www.amazonaws.cn/en/support/icp/?nc2=h_l2_su).
 
 **Q: What versions of OpenSearch does the solution work with?**</br>
-Centralized Logging with OpenSearch supports Amazon OpenSearch Service, with engine version Elasticsearch 7.10 and later, Amazon OpenSearch 1.0 and later.
+Centralized Logging with OpenSearch supports Amazon OpenSearch Service, with OpenSearch 1.3 or later.
 
 **Q: What are the index name rules for OpenSearch created by the Log Analytics Pipeline?**</br>