Note: Doc team updates the current version of the documentation and the
two previous versions (n-2), but we address *only high-priority, or
customer-reported issues* for -2 releases in support.
Describe the changes in the doc and link to your dev story:

1. - [ ] Mandatory: Add the required version to the Fix version/s field.

2. - [ ] Mandatory: Choose the type of documentation change or review.

• [x] We need to update to an existing topic

• [] We need to add a new document to an existing section

• [ ] We need a whole new section; this is a function not
  documented before and doesn't belong in any current section

• [ ] We need an Operator Advisory review and approval

• [ ] We need a z-Stream (Errata) Advisory and Release note
  for MCE and/or ACM

3. - [ ] *Mandatory: *Use the following link to open the doc and find where the
documentation update should go. Note: As the feature and doc is
understood and developed, this placement decision may change:

• Published doc: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10
• Source: https://github.com/stolostron/rhacm-docs

4. - [ ] Mandatory for GA content:

• [x] Add steps, the diff, known issue, and/or other important
  conceptual information in the following space:
  Add this to the pre-requiste section

For AWS , if using existing VPC , configure the details manually

This content can be a hyper link leading to the configuring Submariner section.

Do the following steps,
Open the SubmarinerConfig for editing:
oc edit submarinerconfig -n <managed-cluster-ns> submariner
Add these annotations in the metadata field (all the IDs here are alphanumeric, not the names):
annotations:
submariner.io/control-plane-sg-id: <control-plane-security-group-id> # Usually takes the name <infra-id>-master-sg
submariner.io/subnet-id-list: <comma-separated list of public subnet IDs in the custom VPC>
submariner.io/vpc-id: <custom VPC ID>
submariner.io/worker-sg-id: <worker-security-group-id> # Usually takes the name <infra-id>-worker-sg

Save the file.
"

• [ ] *Add Required access level *(example, *Cluster
  Administrator*) for the user to complete the task:

• [ ] Add verification at the end of the task, how does the user
  verify success (a command to run or a result to see?)

• [ ] Add link to dev story here:

5. - [ ] Mandatory for bugs: What is the diff? Clearly define what the
problem is, what the change is, and link to the current documentation. Only
use this for a documentation bug.