You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/api/getting-started.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ See [Access Keys](/docs/manage/security/access-keys) to learn how to generate an
42
42
Because access keys use the permissions of the user running the key, ensure that the user utilizing a key has the [role capabilities](/docs/manage/users-roles/roles/role-capabilities) needed to execute the tasks the key is needed for.
43
43
:::
44
44
45
-
### Access ID and Access Key
45
+
### Access ID and access key
46
46
47
47
When you have an `accessId` and `accessKey`, you can execute requests like the following:
48
48
@@ -80,7 +80,7 @@ This would yield a Base64 encoded string `QWxhZGRpbjpPcGVuU2VzYW1l` that is used
80
80
```
81
81
82
82
83
-
## Sumo Logic Endpoints by Deployment and Firewall Security
83
+
## Sumo Logic endpoints by deployment and firewall security
@@ -218,17 +218,17 @@ For collection to work, your firewall must allow outbound traffic to Sumo Logic.
218
218
* If your firewall doesn’t allow DNS entries, you must allowlist all of the IP addresses for your deployment region. The addresses to allowlist depend on your Sumo Logic deployment.
219
219
* To determine the IP addresses that require allowlisting, download the JSON object provided by Amazon Web Services (AWS). Amazon advises that this file will change several times a week. For details on how the file is updated, its usage, its syntax, and how to download the JSON file, see [AWS IP Address Ranges](https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html).
220
220
221
-
### FedRAMP Deployment
221
+
### FedRAMP deployment
222
222
223
223
Sumo Logic's FedRAMP deployment is similar to our other deployments, such as US2, except that FedRAMP is certified to comply with the United States Standards for Security Categorization of Federal Information and Information Systems ([FIPS-199](https://en.wikipedia.org/wiki/FIPS_199)). In this deployment, we adhere to specific security requirements that are required for handling, storing, and transmitting data classified in the "Moderate" impact level.
224
224
225
-
### AWS Region by Sumo Deployment
225
+
### AWS region by Sumo Logic deployment
226
226
227
227
import AwsRegion from '../reuse/aws-region-by-sumo-deployment.md';
228
228
229
229
<AwsRegion/>
230
230
231
-
## Status Codes
231
+
## Status codes
232
232
233
233
Generic status codes that apply to all our APIs. See the [HTTP status code registry](https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml) for reference.
234
234
@@ -251,7 +251,7 @@ Generic status codes that apply to all our APIs. See the [HTTP status code regis
251
251
252
252
If a rate is exceeded, a `rate limit exceeded 429` status code is returned.
253
253
254
-
## Versioning and Conflict Detection
254
+
## Versioning and conflict detection
255
255
256
256
The [Collector Management API](/docs/api/collector-management) uses optimistic locking to deal with versioning and conflict detection. Any response that returns a single entity will have an ETag header which identifies the version of that entity.
Copy file name to clipboardExpand all lines: docs/reuse/aws-region-by-sumo-deployment.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,19 +1,21 @@
1
1
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.
2
2
3
-
| Sumo Deployment | AWS Region Name | AWS Region |
3
+
| Sumo Logic Deployment | AWS Region Name | AWS Region |
4
4
|:---|:---|:---|
5
5
| AU | Asia Pacific (Sydney) | ap-southeast-2 |
6
6
| CA | Canada (Central) | ca-central-1 |
7
7
| DE | EU (Frankfurt) | eu-central-1 |
8
8
| EU | EU (Ireland) | eu-west-1 |
9
9
| FED | US East (N. Virginia) | us-east-1 |
10
-
| IN | Asia Pacific (Mumbai) | ap-south-1 |
10
+
| IN | Asia Pacific (Mumbai) | ap-south-1*|
11
11
| JP | Asia Pacific (Tokyo) | ap-northeast-1 |
12
12
| KR | Asia Pacific (Seoul) | ap-northeast-2 |
13
13
| US1 | US East (N. Virginia) | us-east-1 |
14
14
| US2 | US West (Oregon) | us-west-2 |
15
15
16
-
[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 deployment uses, as shown in the table.
16
+
\* The ap-south-1 deployment region is restricted. It is not possible to create new instances in this region.
17
+
18
+
[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.
17
19
18
20
The list of IP ranges is shared infrastructure. It is not limited to Sumo Logic nodes and is subject to change over time.
0 commit comments