---
title: "Check that an AWS Lambda Function exists"
method: POST
path: "/api/v1/integration/aws/logs/check_async"
tags: ["AWS Logs Integration"]
---

# Check that an AWS Lambda Function exists

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

Test if permissions are present to add a log-forwarding triggers for the given services and AWS account. The input
is the same as for Enable an AWS service log collection. Subsequent requests will always repeat the above, so this
endpoint can be polled intermittently instead of blocking.

- Returns a status of 'created' when it's checking if the Lambda exists in the 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

- AWSAccountAndLambdaRequest — AWS account ID and Lambda ARN.
  - `account_id` string, required — Your AWS Account ID without dashes.
  - `lambda_arn` string, required — ARN of the Datadog Lambda created during the Datadog-Amazon Web services Log collection setup.

## 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)