Script AWS API Gateway with Cloudformation and YAML

Write the below Cloudformation script with YAML: Input parameter: -RootDomainName. (this is a domain name such as [login to view URL]) In the below instructions, replace all “[login to view URL]” with RootDomainName Use [login to view URL] for your tests only. Route53: - Create a Hosted Zone which is: 1- Local 2- Points to VPC mentioned below (VPC) 3- called "[login to view URL]" API Gateway: 1- Create a VPC Link a. Link to a VPC called “jxt-vpc”. The Cloudformation export name of this VPC is “JxtNestVPC” b. Link this VPC link to the only private load balancer in the VPC which has the Cloudformation export name of “PrivateLoadBalancerId” c. Name this VPC Link as “JxtNestLink” 2- Create a new API a. Name the API as “JXT Connect” b. No authentication is required c. Add a resource i. Type is Proxy Resource ii. The resource name is “jxtconnect” iii. Resource path is {proxy+} iv. Enable API Gateway CORS d. In the resource “jxtconnect” add method “ANY” i. The method must link tp VPC Link created above ii. URL path = [login to view URL]{proxy} 3- Create a stage called “v1” 4- Deploy the API to stage “v1” 5- Create a Custom Domain a. Link the custom domain to “[login to view URL]” b. Use TLS 1.2 c. Use regional d. Use the ARN of the first certificate you find in ACM e. Add base address mapping for this custom domain: i. "/" must be mapped to "jxtconnect" (v1) ii. Point to the “v1” staging and deployment 6- Get the “Target domain name” of the above custom domain 7- Add an A record in Route 53 for “[login to view URL]” a. This record is an Alias b. Points to the “Target Domain Name” If you make an HTTP call to [login to view URL] You must get HTTP 200 (healthy)