Allow use of dns-route53 plugin for Let's Encrypt challenges
Allow the use of
--dns-route53 for renewal and installation of certificates when using Let's Encrypt
Some gitlab instances might be behind rigid AWS security groups, but may allow Let's Encrypt challenges through Route53.
This would allow automated renewals in a more "firewalled" environment
You should be able to deploy and configure gitlab with Let's Encrypt certificates that can pass the challenge using Route53. Credentials for AWS could either be provided in
gitlab.rb or it could be assumed in the role tied to the EC2 instance.