Amazon Route 53 High TTL Resource Record Sets

Checks for resource record sets that can benefit from having a lower time-to-live (TTL) value. Presently checking for a threshold of 600 seconds. TTL is the number of seconds that a resource record set is cached by DNS resolvers.

Adopt Template

Trigger

Use this to initiate a workflow based on time, events or call.

Trigger by External Application

Resource

Select resources on which you want to work on.

Gets Hosted Zones in a specific AWS Region for Route53 service. Also inject data from Route53 Resource Record Sets

Filter

Enter parameters to filter resources in the workflow.

Filters the data

Report

Use this node to generate advanced reports

Generates the report and sends it via Slack or email
Adopt Template

Workflow Template

Trigger

Use this to initiate a workflow based on time, events or call.

Trigger by External Application

Resource

Select resources on which you want to work on.

Gets Hosted Zones in a specific AWS Region for Route53 service. Also inject data from Route53 Resource Record Sets

Filter

Enter parameters to filter resources in the workflow.

Filters the data

Report

Use this node to generate advanced reports

Generates the report and sends it via Slack or email

Create A Template

Thank you! Your submission has been received!
Oops! Something went wrong while submitting. Please Try Again.

Request for a template

You can publish templates created by you on this platform.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Similar Templates

Create Alarms based on previous data

EC2
CloudWatch
Operational Excellence

Takes all the EC2 server and calculates the average CPUUtilization of last one month for all the Servers. Using this average CPUUtilization as threshold, new alarms are being created for the servers that doesn't have an alarm already.

Stop RDS DB Instance - Create And Close Jira Ticket

Remediation
Automation
RDS

Create a Jira ticket with DB Instance Identifiers of all Instances that will be stopped, stop the DB Instance, and then close the Jira ticket

Create an EKS Cluster and Node Group (Part 2)

Automation
Release and Deployment
EC2

Automated Deployment of a Container application in a Kubernetes cluster in AWS, including logging and monitoring attributes. Part 2 of 2.

Create a 3-Tier Application (Part 3)

Automation
Release and Deployment
EC2

Provision a 3 tier application in AWS Cloud involving a CDN, DNS, Load Balancer, VPC, Web Server, Application and Database layer, Integrated with AWS Logging and Auditing services like Cloudwatch and CloudTrail. Part 3 of 3.