AWS prescriptive-guidance documentation change
Summary
Formatting updates: replaced en-dash with hyphen in heading, changed bold headings to markdown subheadings, minor text edits (removed 'the' before 'collection phase', corrected 'Amazon Data Firehose' to 'Amazon Kinesis Data Firehose'), fixed section title from 'Deployment' to 'Stage 3 - Deployment'.
Security assessment
Changes are purely cosmetic, grammatical, or branding updates with no security context. No vulnerabilities, security controls, or security features are mentioned or modified.
Diff
diff --git a/prescriptive-guidance/latest/opensearch-service-migration/stage-2-poc.md b/prescriptive-guidance/latest/opensearch-service-migration/stage-2-poc.md index 8292198a6..6d194de21 100644 --- a//prescriptive-guidance/latest/opensearch-service-migration/stage-2-poc.md +++ b//prescriptive-guidance/latest/opensearch-service-migration/stage-2-poc.md @@ -9 +9 @@ Defining entry and exit criteriaSecuring fundingAutomatingThorough testingPoC st -# Stage 2 – Proof of concept +# Stage 2 - Proof of concept @@ -68 +68 @@ Test all portions of the stack by making sure that you perform the required vali -**Presentation layer** +### Presentation layer @@ -83 +83 @@ In the presentation layer, be sure to run a PoC exercise that includes the follo -**Ingestion layer** +### Ingestion layer @@ -87 +87 @@ In the ingestion layer, be sure to evaluate various components such as collectio - * **Collection** – For log analytics use cases, validate whether all the data that you are logging is being collected. For search use cases, identify the sources that feed the data and perform validations on completeness and correctness of data to make sure that the collection phase has been executed successfully. + * **Collection** – For log analytics use cases, validate whether all the data that you are logging is being collected. For search use cases, identify the sources that feed the data and perform validations on completeness and correctness of data to make sure that collection phase has been executed successfully. @@ -89 +89 @@ In the ingestion layer, be sure to evaluate various components such as collectio - * **Buffer** – If you have a spike in traffic, you might want to make sure that you are buffering the data that is getting ingested. There are various ways to create a buffering design. For example, you can collect data in Amazon Data Firehose, or you can use Amazon S3 storage as a buffer. + * **Buffer** – If you have a spike in traffic, you might want to make sure that you are buffering the data that is getting ingested. There are various ways to create a buffering design. For example, you can collect data in Amazon Kinesis Data Firehose, or you can use Amazon S3 storage as a buffer. @@ -102 +102 @@ We recommend that you use the following stages to implement your PoC and validat - * **Functional testing and load testing** – Ensure that all levels are being thoroughly tested. Simulate failures in all portions of the stack. For example, if you have a cluster with two large nodes and one of them goes down, the other node must take up all the traffic on your cluster. In such a scenario, having a higher number of smaller nodes can result in a smoother recovery from a node failure. Test your workloads at peak loads and above to make sure that the performance is not impacted in such scenarios. During testing, raise issues early so that any potential issues are being evaluated by various stakeholders at the right time. + * **Functional testing and load testing** – Ensure that all levels are being thoroughly tested. Simulate failures in all potions of the stack. For example, if you have a cluster with two large nodes and one of them goes down, the other node must take up all the traffic on your cluster. In such a scenario, having a higher number of smaller can result in a smoother recovery from a node failure. Test your workloads at peak loads and above to make sure that the performance is not impacted in such scenarios. During testing, raise issues early so that any potential issues are being evaluated by various stakeholders at the right time. @@ -123 +123 @@ Deployment frameworks -Deployment +Stage 3 - Deployment