# route53

Published articles for route53.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Using SSL in HatchBox with AWS Route 53

DevFeed: [Using SSL in HatchBox with AWS Route 53](<https://devfeed.tech/articles/using-ssl-in-hatchbox-with-aws-route-53-28286.md>)

Original publisher: [Read original article](<http://fuzzyblog.io/blog/rails/2022/06/23/using-ssl-in-hatchbox-with-aws-route-53.html>)

Author: Fuzzygroup

Published: 2022-06-23T07:01:00Z

Content type: tutorial

Language: en

Sources: [Scott Johnson](<https://devfeed.tech/sources/scott-johnson.md>)

Topics: [Amazon Route 53](<https://devfeed.tech/topics/amazon-route-53.md>), [Rails](<https://devfeed.tech/topics/rails.md>), [SSL](<https://devfeed.tech/topics/ssl.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [JSON](<https://devfeed.tech/topics/json.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [cartazzi](<https://devfeed.tech/tags/cartazzi.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [hatchbox](<https://devfeed.tech/tags/hatchbox.md>), [iam](<https://devfeed.tech/tags/iam.md>), [json](<https://devfeed.tech/tags/json.md>), [rails](<https://devfeed.tech/tags/rails.md>), [route53](<https://devfeed.tech/tags/route53.md>), [ssl](<https://devfeed.tech/tags/ssl.md>)

### AI overview

A practical guide to configuring wildcard SSL in HatchBox with AWS Route 53. It explains the required Route 53 setup, IAM user and JSON policy configuration, credential handling, and the addition of route53:ListResourceRecordSets after an incomplete policy caused validation problems.

### Source excerpt

HatchBox continues to be my favorite tool for Rails deployment hands down. And this includes Dockarno - my own Bash based Docker deployment tool. When something you pay for replaces something you wrote yourself, that's a sign of its very, very strong goodness. I just used HatchBox to support SSL wildcard deployment for something I'm building and the process was a tad bit tricky so I thought I'd write it up. HatchBox has excellent built in SSL support using Let's Encrypt but when you use wildcard SSL, you get asked for the Route 53 Key and the Route 53 secret. Here's how you get those: On AWS, in Route 53 In Route 53, make sure you have *.domain.extension defined to allow it to be wildcard. On AWS, in IAM In the IAM console, you need to: Add a user Add that user to a group Add a JSON policy document Here is the JSON policy that you need to add: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "route53:GetChange", "Resource": "arn:aws:route53:::change/*" }, { "Effect": "Allow", "Action": "route53:ChangeResourceRecordSets", "Resource": "arn:aws:route53:::hostedzone/*" }, { "Effect": "Allow", "Action": "route53:ListHostedZonesByName", "Resource": "*" }, { "Effect": "Allow", "Action": "route53:ListHostedZones", "Resource": "*" }, { "Effect": "Allow", "Action": "route53:ListResourceRecordSets", "Resource": "*" } ] } After you've added that user then you will be prompted with the normal AWS access key / secret key. Save the credentials and then add them to HatchBox. HatchBox will then got thru an API session with AWS and validate the key. My Experience and Chris's Brilliant Work I started from documentation I found online (see below) that turned out to be incomplete. When I examined the HatchBox log for the transaction, I saw this: -----> Connecting to SOMETHING3-lb (138.68.227.244 port 22) as root Uploaded /etc/logrotate.d/acme.sh Executing 'curl https://raw.githubusercontent.com/acmesh-official/acme.sh/master/acme.sh | sh -s -- --install-online' %