GetResolverQueryLogConfig - Amazon Route 53


Gets information about a specified Resolver query logging configuration, such as the number of VPCs that the configuration is logging queries for and the location that logs are sent to.

Request Syntax

{ "ResolverQueryLogConfigId": "string" }

Request Parameters

For information about the parameters that are common to all actions, see Common Parameters.

The request accepts the following data in JSON format.


The ID of the Resolver query logging configuration that you want to get information about.

Type: String

Length Constraints: Minimum length of 1. Maximum length of 64.

Required: Yes

Response Syntax

{ "ResolverQueryLogConfig": { "Arn": "string", "AssociationCount": number, "CreationTime": "string", "CreatorRequestId": "string", "DestinationArn": "string", "Id": "string", "Name": "string", "OwnerId": "string", "ShareStatus": "string", "Status": "string" } }

Response Elements

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.


Information about the Resolver query logging configuration that you specified in a GetQueryLogConfig request.

Type: ResolverQueryLogConfig object


For information about the errors that are common to all actions, see Common Errors.


The current account doesn't have the IAM permissions required to perform the specified Resolver operation.

This error can also be thrown when a customer has reached the 5120 character limit for a resource policy for CloudWatch Logs.

HTTP Status Code: 400


We encountered an unknown error. Try again in a few minutes.

HTTP Status Code: 400


One or more parameters in this request are not valid.

HTTP Status Code: 400


The request is invalid.

HTTP Status Code: 400


The specified resource doesn't exist.

HTTP Status Code: 400


The request was throttled. Try again in a few minutes.

HTTP Status Code: 400


GetResolverQueryLogConfig Example

This example illustrates one usage of GetResolverQueryLogConfig.

Sample Request

POST / HTTP/1.1 Host: Accept-Encoding: identity Content-Length: 48 X-Amz-Target: Route53Resolver.GetResolverQueryLogConfig X-Amz-Date: 20200731T192652Z User-Agent: aws-cli/1.16.45 Python/2.7.10 Darwin/16.7.0 botocore/1.12.35 Content-Type: application/x-amz-json-1.1 Authorization: AWS4-HMAC-SHA256 Credential=AKIAJJ2SONIPEXAMPLE/20181101/us-east-2/route53resolver/aws4_request, SignedHeaders=content-type;host;x-amz-date;x-amz-target, Signature=[calculated-signature] { "ResolverQueryLogConfigId": "rqlc-8ca61fe7cexample" }

Sample Response

HTTP/1.1 200 OK Date: Thu, 01 Nov 2018 19:26:52 GMT Content-Type: application/x-amz-json-1.1 Content-Length: 464 x-amzn-RequestId: 1d7c8aad-1c63-413d-88a9-bc7b0example Connection: keep-alive { "ResolverQueryLogConfig": { "Arn": "arn:aws:route53resolver:us-east-1:111122223333:resolver-query-log-config/rqlc-8ca61fe7cexample", "AssociationCount": "1", "CreationTime": "20200731T191604Z", "CreatorRequestId": "ramirezd-20200731T191001Z", "DestinationArn": "arn:aws:s3:::examplebucket/development/", "Id": "rqlc-8ca61fe7c055415a", "Name": "MyQueryLog", "OwnerId": "111122223333", "ShareStatus": "NOT_SHARED", "Status": "CREATING" } }

See Also

For more information about using this API in one of the language-specific AWS SDKs, see the following: