AWS Route 53

Version: 1.1
Updated: Jun 21, 2023
Interact with DNS records through AWS Route 53.
Actions
- Create Record (Enrichment) - Creates a resource record set that has the specified values.
- List Hosted Zones (Enrichment) - Retrieves a list of the public and private hosted zones that are associated with the current AWS account.
- List Resource Records Sets (Enrichment) - Lists the resource record sets in a specified hosted zone.
- Test DNS Answer (Enrichment) - Gets the value that Amazon Route 53 returns in response to a DNS request for a specified record name and type.
- Delete Record (Containment) - Deletes an existing resource record set that has the specified values.
- Upsert Record (Containment) - If a resource record set does not already exist, AWS creates it. If a resource set does exist, Route 53 updates it with the values in the request.
External Libraries
Configure AWS Route 53 in Automation Service and Cloud SOAR
Before you can use this automation integration, you must configure its authentication settings so that the product you're integrating with can communicate with Sumo Logic. For general guidance, see Configure Authentication for Automation Integrations.
How to open the integration's configuration dialog
- Access App Central and install the integration. (You can configure at installation, or after installation with the following steps.)
- Go to the Integrations page.
Classic UI. In the main Sumo Logic menu, select Automation and then select Integrations in the left nav bar.
New UI. In the main Sumo Logic menu, select Automation > Integrations. You can also click the Go To... menu at the top of the screen and select Integrations. - Select the installed integration.
- Hover over the resource name and click the Edit button that appears.
In the configuration dialog, enter information from the product you're integrating with. When done, click TEST to test the configuration, and click SAVE to save the configuration:
-
Label. Enter the name you want to use for the resource.
- URL. Enter your AWS Route 53 URL, for example,
route53.amazonaws.com
. -
Access Key ID. Enter an AWS access key ID to provide authentication. (Although AWS recommends using IAM roles with temporary security credentials instead of access keys, our AWS integrations currently support only access keys due to the need for dynamically managed credentials.)
-
Secret Access Key. Enter the secret access key associated with the access key ID.
-
AWS Region. Enter your AWS region.
-
Automation Engine. Select Cloud execution for this certified integration. Select a bridge option only for a custom integration. See Cloud or Bridge execution.
-
Proxy Options. Select whether to use a proxy. (Applies only if the automation engine uses a bridge instead of cloud execution.)
- Use no proxy. Communication runs on the bridge and does not use a proxy.
- Use default proxy. Use the default proxy for the bridge set up as described in Using a proxy.
- Use different proxy. Use your own proxy service. Provide the proxy URL and port number.

For configuration information specific to AWS integrations, see the AWS integrations section.
For information about AWS Route 53, see Route 53 documentation.
Change Log
- December 24, 2019 - First upload
- June 21, 2023 (v1.1) - Updated the integration with Environmental Variables