UpdateResolverConfigRequest is a JSON Structure definition published by Amazon Route 53 Resolver, describing 2 properties, of which 2 are required. It conforms to the https://json-structure.org/meta/core/v0/# meta-schema.
{
"$schema": "https://json-structure.org/meta/core/v0/#",
"$id": "https://raw.githubusercontent.com/api-evangelist/amazon-route53-resolver/refs/heads/main/json-structure/amazon-route53-resolver-openapi-update-resolver-config-request-structure.json",
"description": "UpdateResolverConfigRequest schema from openapi",
"type": "object",
"properties": {
"ResourceId": {
"allOf": [
{
"$ref": "#/components/schemas/ResourceId"
},
{
"description": "Resource ID of the Amazon VPC that you want to update the Resolver configuration for."
}
]
},
"AutodefinedReverseFlag": {
"allOf": [
{
"$ref": "#/components/schemas/AutodefinedReverseFlag"
},
{
"description": "<p>Indicates whether or not the Resolver will create autodefined rules for reverse DNS lookups. This is enabled by default. Disabling this option will also affect EC2-Classic instances using ClassicLink. For more information, see <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/vpc-classiclink.html\">ClassicLink</a> in the <i>Amazon EC2 guide</i>.</p> <important> <p>We are retiring EC2-Classic on August 15, 2022. We recommend that you migrate from EC2-Classic to a VPC. For more information, see <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/vpc-migrate.html\">Migrate from EC2-Classic to a VPC</a> in the <i>Amazon EC2 guide</i> and the blog <a href=\"http://aws.amazon.com/blogs/aws/ec2-classic-is-retiring-heres-how-to-prepare/\">EC2-Classic Networking is Retiring \u2013 Here\u2019s How to Prepare</a>.</p> </important> <note> <p>It can take some time for the status change to be completed.</p> </note> <p/>"
}
]
}
},
"required": [
"ResourceId",
"AutodefinedReverseFlag"
],
"name": "UpdateResolverConfigRequest"
}
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.