Mock sample for your project: Amazon Route 53 Resolver API

Integrate with "Amazon Route 53 Resolver API" from amazonaws.com in no time with Mockoon's ready to use mock sample

Amazon Route 53 Resolver

amazonaws.com

Version: 2018-04-01

Use this API in your project

Open in the application
Download mock API file
📖 How to use?
Own this API? Add a Mockoon button on your website.

Integrate third-party APIs faster by using "Amazon Route 53 Resolver API" ready-to-use mock sample. Mocking this API will allow you to start working in no time. No more accounts to create, API keys to provision, accesses to configure, unplanned downtime, just work.
Improve your integration tests by mocking third-party APIs and cover more edge cases: slow response time, random failures, etc.

Description

When you create a VPC using Amazon VPC, you automatically get DNS resolution within the VPC from Route 53 Resolver. By default, Resolver answers DNS queries for VPC domain names such as domain names for EC2 instances or Elastic Load Balancing load balancers. Resolver performs recursive lookups against public name servers for all other domain names. You can also configure DNS resolution between your VPC and your network over a Direct Connect or VPN connection: Forward DNS queries from resolvers on your network to Route 53 Resolver DNS resolvers on your network can forward DNS queries to Resolver in a specified VPC. This allows your DNS resolvers to easily resolve domain names for Amazon Web Services resources such as EC2 instances or records in a Route 53 private hosted zone. For more information, see How DNS Resolvers on Your Network Forward DNS Queries to Route 53 Resolver in the Amazon Route 53 Developer Guide. Conditionally forward queries from a VPC to resolvers on your network You can configure Resolver to forward queries that it receives from EC2 instances in your VPCs to DNS resolvers on your network. To forward selected queries, you create Resolver rules that specify the domain names for the DNS queries that you want to forward (such as example.com), and the IP addresses of the DNS resolvers on your network that you want to forward the queries to. If a query matches multiple rules (example.com, acme.example.com), Resolver chooses the rule with the most specific match (acme.example.com) and forwards the query to the IP addresses that you specified in that rule. For more information, see How Route 53 Resolver Forwards DNS Queries from Your VPCs to Your Network in the Amazon Route 53 Developer Guide. Like Amazon VPC, Resolver is Regional. In each Region where you have VPCs, you can choose whether to forward queries from your VPCs to your network (outbound queries), from your network to your VPCs (inbound queries), or both.

Other APIs by amazonaws.com

Amazon Location Service

amazonaws.com
Suite of geospatial services including Maps, Places, Routes, Tracking, and Geofencing
Use API

Amazon Mechanical Turk

amazonaws.com
Amazon Mechanical Turk API Reference
Use API

Amazon Kinesis

amazonaws.com
Amazon Kinesis Data Streams Service API Reference Amazon Kinesis Data Streams is a managed service that scales elastically for real-time processing of streaming big data.
Use API

Amazon Lex Runtime Service

amazonaws.com
Amazon Lex provides both build and runtime endpoints. Each endpoint provides a set of operations (API). Your conversational bot uses the runtime API to understand user utterances (user input text or voice). For example, suppose a user says "I want pizza", your bot sends this input to Amazon Lex using the runtime API. Amazon Lex recognizes that the user request is for the OrderPizza intent (one of the intents defined in the bot). Then Amazon Lex engages in user conversation on behalf of the bot to elicit required information (slot values, such as pizza size and crust type), and then performs fulfillment activity (that you configured when you created the bot). You use the build-time API to create and manage your Amazon Lex bot. For a list of build-time operations, see the build-time API, .
Use API

Amazon Macie

amazonaws.com
Amazon Macie Classic Amazon Macie Classic is a security service that uses machine learning to automatically discover, classify, and protect sensitive data in AWS. Macie Classic recognizes sensitive data such as personally identifiable information (PII) or intellectual property, and provides you with dashboards and alerts that give visibility into how this data is being accessed or moved. For more information, see the Amazon Macie Classic User Guide.
Use API

Amazon Chime SDK Messaging

amazonaws.com
The Amazon Chime SDK Messaging APIs in this section allow software developers to send and receive messages in custom messaging applications. These APIs depend on the frameworks provided by the Amazon Chime SDK Identity APIs. For more information about the messaging APIs, see Amazon Chime SDK messaging
Use API

AWSServerlessApplicationRepository

amazonaws.com
The AWS Serverless Application Repository makes it easy for developers and enterprises to quickly find
and deploy serverless applications in the AWS Cloud. For more information about serverless applications,
see Serverless Computing and Applications on the AWS website. The AWS Serverless Application Repository is deeply integrated with the AWS Lambda console, so that developers of
all levels can get started with serverless computing without needing to learn anything new. You can use category
keywords to browse for applications such as web and mobile backends, data processing applications, or chatbots.
You can also search for applications by name, publisher, or event source. To use an application, you simply choose it,
configure any required fields, and deploy it with a few clicks. You can also easily publish applications, sharing them publicly with the community at large, or privately
within your team or across your organization. To publish a serverless application (or app), you can use the
AWS Management Console, AWS Command Line Interface (AWS CLI), or AWS SDKs to upload the code. Along with the
code, you upload a simple manifest file, also known as the AWS Serverless Application Model (AWS SAM) template.
For more information about AWS SAM, see AWS Serverless Application Model (AWS SAM) on the AWS Labs
GitHub repository. The AWS Serverless Application Repository Developer Guide contains more information about the two developer
experiences available:
Consuming Applications – Browse for applications and view information about them, including
source code and readme files. Also install, configure, and deploy applications of your choosing.
Publishing Applications – Configure and upload applications to make them available to other
developers, and publish new versions of applications.
Use API

Amazon Chime SDK Identity

amazonaws.com
The Amazon Chime SDK Identity APIs in this section allow software developers to create and manage unique instances of their messaging applications. These APIs provide the overarching framework for creating and sending messages. For more information about the identity APIs, refer to Amazon Chime SDK identity.
Use API

AWS Elemental MediaLive

amazonaws.com
API for AWS Elemental MediaLive
Use API

AWS Elemental MediaConvert

amazonaws.com
AWS Elemental MediaConvert
Use API

AWS Step Functions

amazonaws.com
AWS Step Functions AWS Step Functions is a service that lets you coordinate the components of distributed applications and microservices using visual workflows. You can use Step Functions to build applications from individual components, each of which performs a discrete function, or task, allowing you to scale and change applications quickly. Step Functions provides a console that helps visualize the components of your application as a series of steps. Step Functions automatically triggers and tracks each step, and retries steps when there are errors, so your application executes predictably and in the right order every time. Step Functions logs the state of each step, so you can quickly diagnose and debug any issues. Step Functions manages operations and underlying infrastructure to ensure your application is available at any scale. You can run tasks on AWS, your own servers, or any system that has access to AWS. You can access and use Step Functions using the console, the AWS SDKs, or an HTTP API. For more information about Step Functions, see the AWS Step Functions Developer Guide .
Use API

Amazon Kinesis Video Signaling Channels

amazonaws.com
Kinesis Video Streams Signaling Service is a intermediate service that establishes a communication channel for discovering peers, transmitting offers and answers in order to establish peer-to-peer connection in webRTC technology.
Use API

Other APIs in the same category

Amazon Kinesis Video Streams

amazonaws.com
Use API

Azure Media Services

azure.com
This Swagger was generated by the API Framework.
Use API

ServiceBusManagementClient

azure.com
Azure Service Bus client for managing Namespace, IPFilter Rules, VirtualNetworkRules and Zone Redundant
Use API

Azure Machine Learning Workspaces

azure.com
These APIs allow end users to operate on Azure Machine Learning Workspace resources.
Use API

HDInsightManagementClient

azure.com
The HDInsight Management Client.
Use API

Azure Dedicated HSM Resource Provider

azure.com
The Azure management API provides a RESTful set of web services that interact with Azure Dedicated HSM RP.
Use API

DnsManagementClient

azure.com
The DNS Management Client.
Use API

VirtualMachineImageTemplate

azure.com
Virtual Machine Image Template
Use API

iotDpsClient

azure.com
API for using the Azure IoT Hub Device Provisioning Service features.
Use API

DiskResourceProviderClient

azure.com
The Disk Resource Provider Client.
Use API

IntuneResourceManagementClient

azure.com
Microsoft.Intune Resource provider Api features in the swagger-2.0 specification
Use API

Machine Learning Compute Management Client

azure.com
These APIs allow end users to operate on Azure Machine Learning Compute resources. They support the following operations: Create or update a cluster Get a cluster Patch a cluster Delete a cluster Get keys for a cluster Check if updates are available for system services in a cluster Update system services in a cluster Get all clusters in a resource group Get all clusters in a subscription
Use API
⬅ Back to the list of mock samples