Logs Data Forwarding management API. Logs Data Forwarding allows you to forward log data from a Partition or Scheduled View to an S3 bucket. For more information, see [Forwarding Data to S3](https://help.sumologic.com/docs/manage/data-forwarding/amazon-s3-bucket).
openapi: 3.0.0
info:
title: Sumo Logic accessKeyManagement logsDataForwardingManagement API
description: "# Getting Started\nWelcome to the Sumo Logic API reference. You can use these APIs to interact with the Sumo Logic platform. For information on Collector and Search Job APIs, see our [API home page](https://help.sumologic.com/docs/api).\n## API Endpoints\nSumo Logic has several deployments in different geographic locations. You'll need to use the Sumo Logic API endpoint corresponding to your geographic location. See the table below for the different API endpoints by deployment. For details determining your account's deployment, see [API endpoints](https://help.sumologic.com/?cid=3011).\n\n <table>\n <tr>\n <td> <strong>Deployment</strong> </td>\n <td> <strong>Endpoint</strong> </td>\n </tr>\n <tr>\n <td> AU </td>\n <td> https://api.au.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> CA </td>\n <td> https://api.ca.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> DE </td>\n <td> https://api.de.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> EU </td>\n <td> https://api.eu.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> FED </td>\n <td> https://api.fed.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> IN </td>\n <td> https://api.in.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> JP </td>\n <td> https://api.jp.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> KR </td>\n <td> https://api.kr.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> US1 </td>\n <td> https://api.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> US2 </td>\n <td> https://api.us2.sumologic.com/api/ </td>\n </tr>\n </table>\n\n## Authentication\nSumo Logic supports the following options for API authentication:\n- Access ID and Access Key\n- Base64 encoded Access ID and Access Key\n\nSee [Access Keys](https://help.sumologic.com/docs/manage/security/access-keys) to generate an Access Key. Make sure to copy the key you create, because it is displayed only once.\nWhen you have an Access ID and Access Key you can execute requests such as the following:\n ```bash\n curl -u \"<accessId>:<accessKey>\" -X GET https://api.<deployment>.sumologic.com/api/v1/users\n ```\n\nWhere `deployment` is either `au`, `ca`, `de`, `eu`, `fed`, `in`, `jp`, `us1`, or `us2`. See [API endpoints](#section/API-Endpoints) for details.\n\nIf you prefer to use basic access authentication, you can do a Base64 encoding of your `<accessId>:<accessKey>` to authenticate your HTTPS request. The following is an example request, replace the placeholder `<encoded>` with your encoded Access ID and Access Key string:\n ```bash\n curl -H \"Authorization: Basic <encoded>\" -X GET https://api.<deployment>.sumologic.com/api/v1/users\n ```\n\n\nRefer to [API Authentication](https://help.sumologic.com/?cid=3012) for a Base64 example.\n\n## Status Codes\nGeneric 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.\n <table>\n <tr>\n <td> <strong>HTTP Status Code</strong> </td>\n <td> <strong>Error Code</strong> </td>\n <td> <strong>Description</strong> </td>\n </tr>\n <tr>\n <td> 301 </td>\n <td> moved </td>\n <td> The requested resource SHOULD be accessed through returned URI in Location Header. See [troubleshooting](https://help.sumologic.com/docs/api/troubleshooting/#api---301-error---moved) for details.</td>\n </tr>\n <tr>\n <td> 401 </td>\n <td> unauthorized </td>\n <td> Credential could not be verified.</td>\n </tr>\n <tr>\n <td> 403 </td>\n <td> forbidden </td>\n <td> This operation is not allowed for your account type or the user doesn't have the role capability to perform this action. See [troubleshooting](https://help.sumologic.com/docs/api/troubleshooting/#api---401-error---credential-could-not-be-verified) for details.</td>\n </tr>\n <tr>\n <td> 404 </td>\n <td> notfound </td>\n <td> Requested resource could not be found. </td>\n </tr>\n <tr>\n <td> 405 </td>\n <td> method.unsupported </td>\n <td> Unsupported method for URL. </td>\n </tr>\n <tr>\n <td> 415 </td>\n <td> contenttype.invalid </td>\n <td> Invalid content type. </td>\n </tr>\n <tr>\n <td> 429 </td>\n <td> rate.limit.exceeded </td>\n <td> The API request rate is higher than 4 request per second or inflight API requests are higher than 10 request per second. </td>\n </tr>\n <tr>\n <td> 500 </td>\n <td> internal.error </td>\n <td> Internal server error. </td>\n </tr>\n <tr>\n <td> 503 </td>\n <td> service.unavailable </td>\n <td> Service is currently unavailable. </td>\n </tr>\n </table>\n\n## Filtering\nSome API endpoints support filtering results on a specified set of fields. Each endpoint that supports filtering will list the fields that can be filtered. Multiple fields can be combined by using an ampersand `&` character.\n\nExample: To get user with email `john@demo.com`:\n ```bash\n api.sumologic.com/v1/users?email=john@demo.com\n ```\n\n## Sorting\nSome API endpoints support sorting fields by using the `sortBy` query parameter. The default sort order is ascending. Prefix the field with a minus sign `-` to sort in descending order.\n\nFor example, to get 20 users sorted by their `email` in descending order:\n ```bash\n api.sumologic.com/v1/users?limit=20&sort=-email\n ```\n\n## Asynchronous Request\nAsynchronous requests do not wait for results, instead they immediately respond back with a job identifier while the job runs in the background. You can use the job identifier to track the status of the asynchronous job request. Here is a typical flow for an asynchronous request.\n1. Start an asynchronous job. On success, a job identifier is returned. The job identifier uniquely identifies\n your asynchronous job.\n\n2. Once started, use the job identifier from step 1 to track the status of your asynchronous job. An asynchronous\n request will typically provide an endpoint to poll for the status of asynchronous job. A successful response\n from the status endpoint will have the following structure:\n ```json\n {\n \"status\": \"Status of asynchronous request\",\n \"statusMessage\": \"Optional message with additional information in case request succeeds\",\n \"error\": \"Error object in case request fails\"\n }\n ```\n The `status` field can have one of the following values:\n 1. `Success`: The job succeeded. The `statusMessage` field might have additional information.\n 2. `InProgress`: The job is still running.\n 3. `Failed`: The job failed. The `error` field in the response will have more information about the failure.\n\n3. Some asynchronous APIs may provide a third endpoint (like [export result](#operation/getAsyncExportResult))\n to fetch the result of an asynchronous job.\n\n\n### Example\nLet's say we want to export a folder with the identifier `0000000006A2E86F`. We will use the [async export](#operation/beginAsyncExport) API to export all the content under the folder with `id=0000000006A2E86F`.\n1. Start an export job for the folder\n ```bash\n curl -X POST -u \"<accessId>:<accessKey>\" https://api.<deployment>.sumologic.com/api/v2/content/0000000006A2E86F/export\n ```\n See [authentication section](#section/Authentication) for more details about `accessId`, `accessKey`, and\n `deployment`.\n On success, you will get back a job identifier. In the response below, `C03E086C137F38B4` is the job identifier.\n ```bash\n {\n \"id\": \"C03E086C137F38B4\"\n }\n ```\n\n2. Now poll for the status of the asynchronous job with the [status](#operation/getAsyncExportStatus) endpoint.\n ```bash\n curl -X GET -u \"<accessId>:<accessKey>\" https://api.<deployment>.sumologic.com/api/v2/content/0000000006A2E86F/export/C03E086C137F38B4/status\n ```\n You may get a response like\n ```json\n {\n \"status\": \"InProgress\",\n \"statusMessage\": null,\n \"error\": null\n }\n ```\n It implies the job is still in progress. Keep polling till the status is either `Success` or `Failed`.\n\n3. When the asynchronous job completes (`status != \"InProgress\"`), you can fetch the results with the\n [export result](#operation/getAsyncExportResult) endpoint.\n ```bash\n curl -X GET -u \"<accessId>:<accessKey>\" https://api.<deployment>.sumologic.com/api/v2/content/0000000006A2E86F/export/C03E086C137F38B4/result\n ```\n\n The asynchronous job may fail (`status == \"Failed\"`). You can look at the `error` field for more details.\n ```json\n {\n \"status\": \"Failed\",\n \"errors\": {\n \"code\": \"content1:too_many_items\",\n \"message\": \"Too many objects: object count(1100) was greater than limit 1000\"\n }\n }\n ```\n\n\n## Rate Limiting\n* A rate limit of four API requests per second (240 requests per minute) applies to all API calls from a user.\n* A rate limit of 10 concurrent requests to any API endpoint applies to an access key.\n\nIf a rate is exceeded, a rate limit exceeded 429 status code is returned.\n\n## Generating Clients\nYou can use [OpenAPI Generator](https://openapi-generator.tech) to generate clients from the YAML file to access the API.\n\n### Using [NPM](https://www.npmjs.com/get-npm)\n1. Install [NPM package wrapper](https://github.com/openapitools/openapi-generator-cli) globally, exposing the CLI\n on the command line:\n ```bash\n npm install @openapitools/openapi-generator-cli -g\n ```\n You can see detailed instructions [here](https://openapi-generator.tech/docs/installation#npm).\n\n2. Download the [YAML file](/docs/sumologic-api.yaml) and save it locally. Let's say the file is saved as `sumologic-api.yaml`.\n3. Use the following command to generate `python` client inside the `sumo/client/python` directory:\n ```bash\n openapi-generator generate -i sumologic-api.yaml -g python -o sumo/client/python\n ```\n\n\n### Using [Homebrew](https://brew.sh/)\n1. Install OpenAPI Generator\n ```bash\n brew install openapi-generator\n ```\n\n2. Download the [YAML file](/docs/sumologic-api.yaml) and save it locally. Let's say the file is saved as `sumologic-api.yaml`.\n3. Use the following command to generate `python` client side code inside the `sumo/client/python` directory:\n ```bash\n openapi-generator generate -i sumologic-api.yaml -g python -o sumo/client/python\n ```\n"
version: 1.0.0
x-logo:
url: ./sumologic_logo.png
servers:
- url: https://api.au.sumologic.com/api/
description: AU deployment API server
- url: https://api.ca.sumologic.com/api/
description: CA deployment API server
- url: https://api.de.sumologic.com/api/
description: DE deployment API server
- url: https://api.eu.sumologic.com/api/
description: EU deployment API server
- url: https://api.fed.sumologic.com/api/
description: FED deployment API server
- url: https://api.jp.sumologic.com/api/
description: JP deployment API server
- url: https://api.kr.sumologic.com/api/
description: KR deployment API server
- url: https://api.in.sumologic.com/api/
description: IN deployment API server
- url: https://api.sumologic.com/api/
description: US1 deployment API server
- url: https://api.us2.sumologic.com/api/
description: US2 deployment API server
security:
- basicAuth: []
tags:
- name: logsDataForwardingManagement
description: 'Logs Data Forwarding management API.
Logs Data Forwarding allows you to forward log data from a Partition or Scheduled View to an S3 bucket. For more information, see [Forwarding Data to S3](https://help.sumologic.com/docs/manage/data-forwarding/amazon-s3-bucket).
'
x-displayName: Logs Data Forwarding
paths:
/v1/logsDataForwarding/destinations:
get:
tags:
- logsDataForwardingManagement
summary: Get Amazon S3 Data Forwarding Destinations.
description: Get a list of all Amazon S3 data forwarding destinations.
operationId: getDataForwardingBuckets
parameters:
- name: limit
in: query
description: Limit the number of data forwarding destinations returned in the response. The number of data forwarding destinations returned may be less than the `limit`.
required: false
schema:
maximum: 100
minimum: 1
type: integer
format: int32
default: 10
- name: token
in: query
description: Continuation token to get the next page of results. A page object with the next continuation token is returned in the response body. Subsequent GET requests should specify the continuation token to get the next page of results. `token` is set to null when no more pages are left.
required: false
schema:
type: string
responses:
'200':
description: List of all S3 data forwarding destinations.
content:
application/json:
schema:
$ref: '#/components/schemas/GetDataForwardingDestinations'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
post:
tags:
- logsDataForwardingManagement
summary: Create An S3 Data Forwarding Destination.
description: Create a new Amazon S3 data forwarding destination.
operationId: createDataForwardingBucket
parameters: []
requestBody:
description: Parameters to create new S3 data forwarding destination.
content:
application/json:
schema:
$ref: '#/components/schemas/CreateBucketDefinition'
required: true
responses:
'200':
description: The new data forwarding destination has been created.
content:
application/json:
schema:
$ref: '#/components/schemas/BucketDefinition'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/logsDataForwarding/destinations/{id}:
get:
tags:
- logsDataForwardingManagement
summary: Get An S3 Data Forwarding Destination.
description: Get an S3 data forwarding destination by the given identifier.
operationId: getDataForwardingDestination
parameters:
- name: id
in: path
description: Identifier of the S3 data forwarding destination to return.
required: true
schema:
type: string
example: 1
responses:
'200':
description: Data forwarding destination object requested.
content:
application/json:
schema:
$ref: '#/components/schemas/BucketDefinition'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
put:
tags:
- logsDataForwardingManagement
summary: Update An S3 Data Forwarding Destination.
description: Update an S3 data forwarding destination by the given identifier.
operationId: UpdateDataForwardingBucket
parameters:
- name: id
in: path
description: Identifier of the data forwarding destination to update.
required: true
schema:
type: string
example: 1
requestBody:
description: Object with the updated parameters.
content:
application/json:
schema:
$ref: '#/components/schemas/UpdateBucketDefinition'
required: true
responses:
'200':
description: The data forwarding destination has been updated.
content:
application/json:
schema:
$ref: '#/components/schemas/BucketDefinition'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
delete:
tags:
- logsDataForwardingManagement
summary: Delete An S3 Data Forwarding Destination.
description: Delete an existing Amazon S3 data forwarding destination with the given identifier.
operationId: deleteDataForwardingBucket
parameters:
- name: id
in: path
description: Identifier of the data forwarding destination to delete.
required: true
schema:
type: string
example: 1
responses:
'204':
description: The data forwarding destination has been deleted.
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/logsDataForwarding/rules:
get:
tags:
- logsDataForwardingManagement
summary: Get All S3 Data Forwarding Rules.
description: Get a list of all S3 data forwarding rules.
operationId: getRulesAndBuckets
parameters:
- name: limit
in: query
description: Limit the number of data forwarding rules returned in the response. The number of data forwarding rules returned may be less than the `limit`.
required: false
schema:
maximum: 100
minimum: 1
type: integer
format: int32
default: 10
- name: token
in: query
description: Continuation token to get the next page of results. A page object with the next continuation token is returned in the response body. Subsequent GET requests should specify the continuation token to get the next page of results. `token` is set to null when no more pages are left.
required: false
schema:
type: string
responses:
'200':
description: List of all S3 data forwarding rules.
content:
application/json:
schema:
$ref: '#/components/schemas/GetRulesAndBucketsResult'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
post:
tags:
- logsDataForwardingManagement
summary: Create An S3 Data Forwarding Rule.
description: Create a data forwarding rule to send data from a Partition or Scheduled View to an S3 bucket.
operationId: createDataForwardingRule
parameters: []
requestBody:
description: Parameters to create the new S3 data forwarding rule.
content:
application/json:
schema:
$ref: '#/components/schemas/CreateDataForwardingRule'
required: true
responses:
'200':
description: The data forwarding rule was created.
content:
application/json:
schema:
$ref: '#/components/schemas/DataForwardingRule'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/logsDataForwarding/rules/{indexId}:
get:
tags:
- logsDataForwardingManagement
summary: Get An S3 Data Forwarding Rule By Its Index.
description: Get the details of an S3 data forwarding rule by its Partition or Scheduled View identifier.
operationId: getDataForwardingRule
parameters:
- name: indexId
in: path
description: The `id` of the Partition or Scheduled View.
required: true
schema:
type: string
example: 1
responses:
'200':
description: Data forwarding rule that was requested.
content:
application/json:
schema:
$ref: '#/components/schemas/RuleAndBucketDetail'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
put:
tags:
- logsDataForwardingManagement
summary: Update An S3 Data Forwarding Rule By Its Index.
description: Update an S3 data forwarding rule by its Partition or Scheduled View identifier.
operationId: updateDataForwardingRule
parameters:
- name: indexId
in: path
description: The `id` of the Partition or Scheduled View with the data forwarding rule to update.
required: true
schema:
type: string
example: 1
requestBody:
description: Parameters of an S3 data forwarding rule.
content:
application/json:
schema:
$ref: '#/components/schemas/UpdateDataForwardingRule'
required: true
responses:
'200':
description: The data forwarding rule was updated.
content:
application/json:
schema:
$ref: '#/components/schemas/DataForwardingRule'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
delete:
tags:
- logsDataForwardingManagement
summary: Delete An S3 Data Forwarding Rule By Its Index.
description: Delete an S3 data forwarding rule by its Partition or Scheduled View identifier.
operationId: deleteDataForwardingRule
parameters:
- name: indexId
in: path
description: The `id` of the Partition or Scheduled View with the data forwarding rule to delete.
required: true
schema:
type: string
example: 1
responses:
'204':
description: The S3 data forwarding rule was deleted.
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
components:
schemas:
BucketDefinition:
type: object
allOf:
- $ref: '#/components/schemas/CreateBucketDefinition'
- $ref: '#/components/schemas/MetadataModel'
- required:
- bucketName
- destinationName
- id
properties:
id:
type: string
description: The unique identifier of the data forwarding destination.
example: '1'
invalidatedBySystem:
type: boolean
description: True if invalidated by the system.
UpdateDataForwardingRule:
type: object
properties:
destinationId:
type: string
description: Data forwarding destination id.
example: '1'
enabled:
type: boolean
description: True when the data forwarding rule is enabled.
example: true
fileFormat:
type: string
description: Specify the path prefix to a directory in the S3 bucket and how to format the file name.
example: '{index}_{day}_{hour}_{minute}_{second}'
payloadSchema:
pattern: ^(builtInFields|allFields|raw)$
type: string
description: Schema for the payload. Default value of the payload schema is "allFields" for scheduled view, and "builtInFields" for partition. "raw" payloadSchema should be used in conjunction with "text" format and vice-versa.
example: builtInFields
x-pattern-message: 'should be one of the following: ''builtInFields'', ''allFields'' or ''raw'''
format:
pattern: ^(csv|json|text)$
type: string
description: Format of the payload. Default format will be "csv". "text" format should be used in conjunction with "raw" payloadSchema and vice-versa.
example: csv
x-pattern-message: 'should be one of the following: ''csv'', ''json'' or ''text'''
GetDataForwardingDestinations:
type: object
properties:
nextToken:
type: string
description: Next continuation token.
example: VEZuRU4veXF2UWFCUURYSDNQUzJxWlpRRUsvTlBieXA
data:
type: array
description: List of data forwarding destinations.
items:
$ref: '#/components/schemas/BucketDefinition'
MetadataModel:
required:
- createdAt
- createdBy
- modifiedAt
- modifiedBy
type: object
properties:
createdAt:
type: string
description: Creation timestamp in UTC in [RFC3339](https://tools.ietf.org/html/rfc3339) format.
format: date-time
example: 2018-10-16 09:10:00+00:00
createdBy:
type: string
description: Identifier of the user who created the resource.
example: 0000000006743FDD
modifiedAt:
type: string
description: Last modification timestamp in UTC.
format: date-time
example: 2018-10-16 09:10:00+00:00
modifiedBy:
type: string
description: Identifier of the user who last modified the resource.
example: 0000000006743FE8
RuleAndBucketDetail:
allOf:
- $ref: '#/components/schemas/DataForwardingRule'
- type: object
properties:
bucket:
$ref: '#/components/schemas/logs-data-forwarding-rule-management'
logs-data-forwarding-rule-management:
type: object
ErrorDescription:
required:
- code
- message
type: object
properties:
code:
type: string
description: An error code describing the type of error.
example: auth:password_too_short
message:
type: string
description: A short English-language description of the error.
example: Your password was too short.
detail:
type: string
description: An optional fuller English-language description of the error.
example: Your password was 5 characters long, the minimum length is 12 characters. See http://example.com/password for more information.
meta:
type: object
description: An optional list of metadata about the error.
example:
minLength: 12
actualLength: 5
GetRulesAndBucketsResult:
type: object
properties:
data:
type: array
description: List of S3 data forwarding rules.
items:
$ref: '#/components/schemas/RuleAndBucketDetail'
nextToken:
type: string
description: Next continuation token.
example: VEZuRU4veXF2UWFCUURYSDNQUzJxWlpRRUsvTlBieXA
CreateBucketDefinitionItems:
required:
- authenticationMode
- bucketName
- destinationName
type: object
properties:
bucketName:
pattern: (?!(^xn--|-s3alias$))^[a-z0-9][a-z0-9-.]{1,61}[a-z0-9]$
type: string
description: The name of the Amazon S3 bucket.
example: df-bucket
x-pattern-message: Must be a valid AWS S3 Bucket name.
ErrorResponse:
required:
- errors
- id
type: object
properties:
id:
type: string
description: An identifier for the error; this is unique to the specific API request.
example: IUUQI-DGH5I-TJ045
errors:
type: array
description: A list of one or more causes of the error.
example:
- code: auth:password_too_short
message: Your password was too short.
- code: auth:password_character_classes
message: Your password did not contain any non-alphanumeric characters
items:
$ref: '#/components/schemas/ErrorDescription'
DataForwardingRule:
allOf:
- $ref: '#/components/schemas/CreateDataForwardingRule'
- $ref: '#/components/schemas/MetadataModel'
- type: object
properties:
id:
type: string
description: The unique identifier of the data forwarding rule.
example: '1'
CreateDataForwardingRule:
required:
- destinationId
- indexId
type: object
properties:
indexId:
type: string
description: The `id` of the Partition or Scheduled View the rule applies to.
example: '1'
destinationId:
type: string
description: The data forwarding destination id.
example: '1'
enabled:
type: boolean
description: True when the data forwarding rule is enabled.
example: true
fileFormat:
type: string
description: Specify the path prefix to a directory in the S3 bucket and how to format the file name.
example: '{index}_{day}_{hour}_{minute}_{second}'
payloadSchema:
pattern: ^(builtInFields|allFields|raw)$
type: string
description: Schema for the payload. Default value of the payload schema is "allFields" for scheduled view, and "builtInFields" for partition. "raw" payloadSchema should be used in conjunction with "text" format and vice-versa.
example: builtInFields
x-pattern-message: 'should be one of the following: ''builtInFields'', ''allFields'' or ''raw'''
format:
pattern: ^(csv|json|text)$
type: string
description: Format of the payload. Default format will be "csv". "text" format should be used in conjunction with "raw" payloadSchema and vice-versa.
example: csv
x-pattern-message: 'should be one of the following: ''csv'', ''json'' or ''text'''
UpdateBucketDefinition:
required:
- authenticationMode
type: object
properties:
destinationName:
type: string
description: Name of the S3 data forwarding destination.
example: df-destination
description:
type: string
description: Description of the S3 data forwarding destination.
authenticationMode:
type: string
description: 'AWS IAM authentication method used for access. Possible values are: 1. `AccessKey` 2. `RoleBased`'
example: RoleBased
accessKeyId:
type: string
description: The AWS Access ID to access the S3 bucket.
example: accessKeyId
secretAccessKey:
type: string
description: The AWS Secret Key to access the S3 bucket.
example: secretAccessKey
roleArn:
type: string
description: The AWS Role ARN to access the S3 bucket.
example: roleArn
region:
type: string
description: The region where the S3 bucket is located.
example: us-east-1
encrypted:
type: boolean
description: Enable S3 server-side encryption.
enabled:
type: boolean
description: True if the destination is Active.
example: true
CreateBucketDefinition:
type: object
allOf:
- $ref: '#/components/schemas/UpdateBucketDefinition'
- $ref: '#/components/schemas/CreateBucketDefinitionItems'
securitySchemes:
basicAuth:
type: http
scheme: basic
x-tagGroups:
- name: Archive Management
tags:
- archiveManagement
- name: Health Events
tags:
- healthEvents
- name: Infrequent Data Tier
tags:
- logSearchesEstimatedUsage
- name: Ingest Budgets Management V2
tags:
- ingestBudgetManagementV2
- name: Library Management
tags:
- appManagement
- appManagementV2
- contentManagement
- dashboardManagement
- folderManagement
- lookupManagement
- contentPermissions
- logSearchesManagement
- parsersLibraryManagement
- name: Metrics
tags:
- metricsSearchesManagement
- transformationRuleManagement
- metricsQuery
- metricsSearchesManagementV2
- name: Security Management
tags:
- accessKeyManagement
- oauthManagement
- accountManagement
- passwordPolicy
- policiesManagement
- samlConfigur
# --- truncated at 32 KB (33 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/sumo-logic/refs/heads/main/openapi/sumo-logic-logsdataforwardingmanagement-api-openapi.yml