---
title: "Check permissions for log services"
method: POST
path: "/api/v1/integration/aws/logs/services_async"
tags: ["AWS Logs Integration"]
---

# Check permissions for log services

`POST /api/v1/integration/aws/logs/services_async`

Test if permissions are present to add log-forwarding triggers for the
given services and AWS account. Input is the same as for `EnableAWSLogServices`.
Done async, so can be repeatedly polled in a non-blocking fashion until
the async request completes.

- Returns a status of `created` when it's checking if the permissions exists
  in the AWS account.
- Returns a status of `waiting` while checking.
- Returns a status of `checked and ok` if the Lambda exists.
- Returns a status of `error` if the Lambda does not exist.

## Request body

- AWSLogsServicesRequest — A list of current AWS services for which Datadog offers automatic log collection.
  - `account_id` string, required — Your AWS Account ID without dashes.
  - `services` string[], required — Array of services IDs set to enable automatic log collection. Discover the list of available services with the get list of AWS log ready services API endpoint.

## Response `200`

OK

- AWSLogsAsyncResponse — A list of all Datadog-AWS logs integrations available in your Datadog organization.
  - `errors` AWSLogsAsyncError[] — List of errors.
    - `code` string — Code properties
    - `message` string — Message content.
  - `status` string — Status of the properties.

## Other responses

- `400` — Bad Request
- `403` — Authentication Error
- `429` — Too many requests

---

[API](https://skmtc.net/datadog/apis/api-v1.md) · [All operations](https://skmtc.net/datadog/apis/api-v1/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/datadog/api-v1/revisions/ca5871004d26/schema)