DisassociateResolverQueryLogConfig - Amazon Route 53

DisassociateResolverQueryLogConfig

Disassociates a VPC from a query logging configuration.

Note

Before you can delete a query logging configuration, you must first disassociate all VPCs from the configuration. If you used Resource Access Manager (RAM) to share a query logging configuration with other accounts, VPCs can be disassociated from the configuration in the following ways:

  • The accounts that you shared the configuration with can disassociate VPCs from the configuration.

  • You can stop sharing the configuration.

Request Syntax

{ "ResolverQueryLogConfigId": "string", "ResourceId": "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.

ResolverQueryLogConfigId

The ID of the query logging configuration that you want to disassociate a specified VPC from.

Type: String

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

Required: Yes

ResourceId

The ID of the Amazon VPC that you want to disassociate from a specified query logging configuration.

Type: String

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

Required: Yes

Response Syntax

{ "ResolverQueryLogConfigAssociation": { "CreationTime": "string", "Error": "string", "ErrorMessage": "string", "Id": "string", "ResolverQueryLogConfigId": "string", "ResourceId": "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.

ResolverQueryLogConfigAssociation

A complex type that contains settings for the association that you deleted between an Amazon VPC and a query logging configuration.

Type: ResolverQueryLogConfigAssociation object

Errors

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

AccessDeniedException

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

HTTP Status Code: 400

InternalServiceErrorException

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

HTTP Status Code: 400

InvalidParameterException

One or more parameters in this request are not valid.

HTTP Status Code: 400

InvalidRequestException

The request is invalid.

HTTP Status Code: 400

ResourceNotFoundException

The specified resource doesn't exist.

HTTP Status Code: 400

ThrottlingException

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

HTTP Status Code: 400

Examples

DisassociateResolverQueryLogConfig Example

This example illustrates one usage of DisassociateResolverQueryLogConfig.

Sample Request

POST / HTTP/1.1 Host: route53resolver.us-east-2.amazonaws.com Accept-Encoding: identity Content-Length: 107 X-Amz-Target: Route53Resolver.DisassociateResolverQueryLogConfig X-Amz-Date: 20200415T185222Z 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/20200415/us-east-2/route53resolver/aws4_request, SignedHeaders=content-type;host;x-amz-date;x-amz-target, Signature=[calculated-signature] { "ResolverQueryLogConfigId": "rqlc-8ca61fe7cexample", "Resource": { "VpcId": "vpc-03cf94c75cexample" } }

Sample Response

HTTP/1.1 200 OK Date: Thu, 01 Nov 2018 18:52:22 GMT Content-Type: application/x-amz-json-1.1 Content-Length: 275 x-amzn-RequestId: bda80f7b-0f2c-41d1-9043-f36d3example Connection: keep-alive { "ResolverQueryLogConfigAssociation":{ "CreationTime": "2020-04-15T18:52:23.30Z", "Error": "", "ErrorMessage": "", "Id": "rqlca-ff85e1ffexample", "ResolverQueryLogConfigId": "rqlc-8ca61fe7cexample", "Resource": "vpc-03cf94c75cexample", "Status": "DELETING" } }

See Also

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