Unify deployment codes and AWS region mapping (#5864)

* Unify deployment codes and AWS region mapping

* Remove bullet

* rm docs/api/aws-region-by-deployment.md

---------

Co-authored-by: John Pipkin <[email protected]>

Author: kimsauce

docs/api/about-apis/getting-started.md

@@ -134,7 +134,7 @@ Sumo Logic's FedRAMP deployment is similar to our other deployments, such as US2
 
 import AWSDeploymentRegion from '../../reuse/aws-region-by-sumo-deployment.md';
 
-* <AWSDeploymentRegion/>
+<AWSDeploymentRegion/>
 
 ## Status codes
 

docs/api/aws-region-by-deployment.md

@@ -2,6 +2,7 @@
 id: faq
 title: Sumo Logic FAQ
 sidebar_label: FAQ
+description: Answers to frequently asked questions about Sumo Logic.
 ---
 
 
@@ -25,7 +26,7 @@ For example, from our own production logs, we use the following:
 
 This is a key-value pair log, which is easy to parse and easy to read in Sumo.
 
-## What Types of Logs Can I Collect?
+## What types of logs can I collect?
 
 The following table lists data types and some of the popular sources that produce logs, which can be collected by Sumo Logic. This list is a sample only to provide a general idea of the possible sources of log data; it is not complete.
 
@@ -43,20 +44,10 @@ The following table lists data types and some of the popular sources that produc
 | SaaS | <ul><li>[Box](/docs/integrations/saas-cloud/box)</li><li>[ServiceNow](/docs/alerts/webhook-connections/servicenow/set-up-connections.md)</li><li>[Salesforce](/docs/integrations/saas-cloud/salesforce)</li><li>[Microsoft Office 365](/docs/integrations/microsoft-azure/office-365)</li></ul> |
 | Security | <ul><li>Cisco</li><li>McAfee</li><li>Symantec</li><li>Qualys</li></ul> |
 
-## Where is My Data Stored?
+## Where is my data stored?
 
-Where your data is stored depends on the geographical location the
-Account Owner selected when establishing your Sumo Logic account. 
+Where your data is stored depends on the geographical location the Account Owner selects when creating your Sumo Logic account. Your data is stored only in your selected region.
 
-* Australia. Your data is stored in the AWS ap-southeast-2 (Sydney) region.
-* Canada. Your data is stored in the AWS ca-central-1 (Central) region.
-* Europe. Ireland. Your data is stored in the AWS eu-west-1 (Ireland) region.
-* Europe. Frankfurt. Your data is stored in the AWS eu-central-1 (Frankfurt) region.
-* Japan. Your data is stored in the AWS ap-northeast-1 (Tokyo) region.
-* North America. Your data is stored in the AWS us-east-1 (Northern Virginia) or us-west-2 (Oregon) region.
-* South Korea. Your data is stored in the AWS ap-northeast-2 (Seoul) region.
-* Federal. Your data is stored in the AWS us-east-1 (Northern Virginia) region.
+import AWSDeploymentRegion from '../reuse/aws-region-by-sumo-deployment.md';
 
-Your data is stored only in your region. 
-
-For more information, see [AWS Regions and Endpoints](http://docs.aws.amazon.com/general/latest/gr/rande.html) and our [Privacy Statement](https://www.sumologic.com/privacy-statement/).
+<AWSDeploymentRegion/>

docs/get-started/faq.md

@@ -1,25 +1,45 @@
-The following table describes the AWS regions used by each Sumo Logic deployment. See the [AWS page on regions and endpoints](http://docs.aws.amazon.com/general/latest/gr/rande.html) for more information.
+The following table describes the AWS regions used by each Sumo Logic deployment.
 
-| Sumo Logic Deployment | AWS Region Name | AWS Region |
-|:---|:---|:---|
-| AU | Asia Pacific (Sydney) | ap-southeast-2 |
-| CA | Canada (Central) | ca-central-1 |
-| DE | EU (Frankfurt) | eu-central-1 |
-| EU | EU (Ireland) | eu-west-1 |
-| FED | US East (N. Virginia) | us-east-1 |
-| JP | Asia Pacific (Tokyo) | ap-northeast-1 |
-| KR | Asia Pacific (Seoul) | ap-northeast-2 |
-| US1 | US East (N. Virginia) | us-east-1 |
-| US2 | US West (Oregon) | us-west-2 |
+| Region code | Region name | AWS region | API endpoint |
+|:----|:----|:---|:-----|
+| AU | Asia Pacific (Sydney)  | ap-southeast-2 | https://api.au.sumologic.com/api/   |
+| CA | Canada (Central) | ca-central-1 | https://api.ca.sumologic.com/api/   |
+| DE | EU (Frankfurt)  | eu-central-1 | https://api.de.sumologic.com/api/   |
+| EU | EU (Ireland)    | eu-west-1  | https://api.eu.sumologic.com/api/   |
+| FED | US East (N. Virginia) | us-east-1  | https://api.fed.sumologic.com/api/  |
+| IN | Asia Pacific (Mumbai) | ap-south-1 | https://api.in.sumologic.com/api/   |
+| JP  | Asia Pacific (Tokyo)  | ap-northeast-1 | https://api.jp.sumologic.com/api/  |
+| KR | Asia Pacific (Seoul) | ap-northeast-2 | https://api.kr.sumologic.com/api/  |
+| US1 | US East (N. Virginia) | us-east-1  | https://api.sumologic.com/api/|
+| US2 | US West (Oregon)| us-west-2 | https://api.us2.sumologic.com/api/ |
 
-[This link](https://ip-ranges.amazonaws.com/ip-ranges.json) provides the complete current list of AWS IP ranges or subnets or prefixes. You can limit the number of entries in a firewall by using just the IP prefixes against the AWS region that your account's Sumo Logic deployment uses, as shown in the table.
+See the [AWS IP ranges JSON file](https://ip-ranges.amazonaws.com/ip-ranges.json) for the current list of AWS IP ranges or subnets or prefixes. To simplify firewall configuration, you can use only the IP prefixes for the AWS region associated with your Sumo Logic deployment, as shown in the table.
 
 The list of IP ranges is shared infrastructure. It is not limited to Sumo Logic nodes and is subject to change over time.
 
 You can run the following query against the downloaded file in Sumo Logic to determine the IP addresses for each deployment.
 
 ```sql
-| parse regex "\s+\"ip_prefix\":\s+\"(?<ip_prefix>.*?)\",\n\s+\"region\":\s+\"(?<region>.*?)\",\n\s+\"service\":\s+\"(?<service>.*?)\"" multi | where service="AMAZON" and (region="us-west-2" or region="us-east-1" or region="eu-west-1" or region="ap-southeast-2") | if (region="us-west-2", "US2", region) as region | if (region="us-east-1", "PROD", region) as region | if (region="eu-west-1", "EU", region) as region | if (region="ap-southeast-2", "AU", region) as region | | if (region="ap-northeast-2", "KR", region) as region | count by ip_prefix, region, service | fields - _count | sort by region, ip_prefix
+| parse regex "\s+\"ip_prefix\":\s+\"(?<ip_prefix>.*?)\",\n\s+\"region\":\s+\"(?<region>.*?)\",\n\s+\"service\":\s+\"(?<service>.*?)\"" multi
+| where service="AMAZON"
+  and (
+       region="us-west-2"
+    or region="us-east-1"
+    or region="eu-west-1"
+    or region="ap-southeast-2"
+  )
+| if (region="us-west-2", "US2", region) as region
+| if (region="us-east-1", "US1", region) as region
+| if (region="eu-west-1", "EU", region) as region
+| if (region="ap-southeast-2", "AU", region) as region
+| if (region="ap-northeast-2", "KR", region) as region
+| count by ip_prefix, region, service
+| fields - _count
+| sort by region, ip_prefix
 ```
 
 After configuring the firewall, Collector, and Sources, confirm that the Collector and Sources are working by verifying that you can receive a given type of message (such as syslog messages) at the specified location.
+
+For more information, see:
+* [AWS documentation: Service endpoints](http://docs.aws.amazon.com/general/latest/gr/rande.html)
+* [Sumo Logic Privacy Statement](https://www.sumologic.com/privacy-statement/)