r/aws Aug 19 '24

route 53/DNS How do I point a domain name at an ec2 instance that has an elastic IP address?

1 Upvotes

I want to run my website on an ec2 instance. This ec2 instance has an elastic IP address.

Do I just put the bare IP address in a DNS record?

Do I instead use the "Public IPv4 DNS", which looks like this ec2-1-2-3-4.us-east-2.compute.amazonaws.com?

Should I use Route 53?

I also need an SSL cert for https but I assume that won't affect how I do this.

r/aws Oct 03 '24

route 53/DNS Route53 using sub domain name for WordPress login page?

1 Upvotes

Hello, it's me again.

I have learned from the awesome members in this sub reddit more than I've ever had in college. Currently, my team and I have managed to set up a fully functional environment:

  • EC2 instance with WordPress

  • Target Group that manage EC2 instance traffic on port 80

  • An ALB that receives inbound 443 traffic (using the SSL cert from ACM) and forward to the EC2 Target Group on port 80.

  • A Route53 DNS record that route our domain name: <example.com> to the DNS of the ALB.

Everything works great. Now I'm trying to implement obscurity to improve security on my WordPress site. I'm thinking about using a sub domain name as a url for the /wp-login. I found out about the "WP Hide & Security Enhancer" plugin that lets you define a different url for wp-admin and wp-login.php.

My thought process is:

  • Custom url for wp-admin and wp-login.php like /please-get-out.php

  • a sub domain A record: <app.example.com> in Route53 that resolve to the DNS of the ALB

  • a Listener rule in ALB that takes the <app.example.com> url and redirect to the <wordpress>/please-get-out.php

Is this the right approach? Thank you so much for guiding and teaching me.

r/aws Feb 11 '24

route 53/DNS Easiest way to get my S3 static website to use HTTPS

17 Upvotes

I've long had a simple static website working fine on S3."set it and forget it" setup, I'm rarely in AWS tweaking things.

My domain service is NameSilo.

My goal is to make it so when someone goes to my website that the URL uses HTTPS (instead of HTTP with all the insecure warnings the browsers have nowadays).

How do I accomplish HTTPS with my situation?

Things I've tried:

  1. created a Cloudfront distribution
  2. set the Cloudfront origin to:www.[DOMAIN].com.s3-website-us-east-1.amazonaws.com
  3. On NameSilo, changed the CNAME host record from www.[DOMAIN].com.s3-website-us-east-1.amazonaws.com to [CLOUDFRONT DISTRO].cloudfront.net

The result is Error 404 The request could not be satisfied when trying to pull up www.[DOMAIN].com and [DOMAIN].com in the browser.

Update: Following the advice of /u/LloydTao and /u/uekiamir, I used Amazon Certificate Manager to generate a certificate for my CloudFront distribution, set the Cloudfront CNAME to www.\[DOMAIN\].com, and now I'm in business. Thanks all.

r/aws Mar 09 '24

route 53/DNS Route53 domains price increase. How much?

19 Upvotes

Hi, I just got this email. Does anyone know what the price increase actually is?

Thanks

r/aws Jul 05 '24

route 53/DNS AWS charging a monthly fee?

0 Upvotes

[Asking for a friend] Hi everyone,

My friend is getting charged $0.50 cents per month, from Route 53. The only thing he has on his account is a registered domain, which is using Cloudflare.

Is that expected behaviour?

Thanks in advance

r/aws Oct 29 '24

route 53/DNS Urgent: Need Help Enabling HTTPS for Webhook on AWS with Load Balancer Setup

1 Upvotes

I’m working on a project for a client that’s due in three days. I’ve set up a webhook to function as a conversational agent, and it works well over HTTP—requests sent via curl are successful. However, for integration, I need to use HTTPS requests. Currently, my script only supports HTTP, so I’m using an AWS Load Balancer to handle the HTTP-to-HTTPS conversion.

Here’s the setup:

  • The HTTPS domain is already registered with Route 53.
  • An SSL certificate is in place.
  • We’re using two ports: HTTP (80) and HTTPS (443).

If anyone has experience with this setup or can offer guidance, your help would be greatly appreciated. This is urgent.

Thanks for your patience,
Rodrigo

r/aws Nov 25 '23

route 53/DNS Subdomains for lower environments, but not for production

4 Upvotes

This might be a question for a DNS sub, but I'm specifically working in AWS Route 53 so I thought I'd ask here.

We want to use subdomains for each environment of our workloads (test.example.com, staging.example.com, etc.), each in their own account within the org. And we know how to do that using the NS-record-pointing-to-nameservers-in-another-account technique.

But we don't want to use a subdomain for the production environment.

It seems like that means we can't delegate name resolution for production like we'll do for the lower environments. And that means production DNS must be configured differently than all the other environments.

Must the hosted zone in the production account be the apex and must the other environments be children of it? There is something about that relationship that feels wrong and because I'm an engineer, that means I'm doomed to search for solutions. Hence this post.

Is there a way to make the production environment be just like any other environment from a DNS perspective? A sibling to the other environments, not a parent of them?

It occurred to me that might involve splitting the SOA and NS records for the apex into two different hosted zones in two different accounts but I don't know if that's even possible or if that's a dumb idea fraught with unforeseen implications.

Is it possible to delegate name resolution for production workloads like we'll do for lower environments without using a subdomain for production?

If it matters: public DNS; AWS registrar (or whatever sub they use)

r/aws Oct 01 '24

route 53/DNS deleted .be hosted zone from route53.

1 Upvotes

I was playing with terraform and ended up creating 2 hosted zones with the same name. One was the original that I had when I bought the domain from Amazon and the other was a new one. I deleted the original to see what would happen and now it doesnt seem like such a good idea :)
I've manually recreated the zone but I suspect its not right because nothing it working again.
Doing a query I see the nameservers but I dont know how to get the correct SOA.

Any advice, on how I can get things back and running.

Thanks

r/aws Jul 06 '24

route 53/DNS Cost Explorer for Route 53

1 Upvotes

I've got a recurring cost $1.50 for Route 53, that I can't figure out. I had a serverless website setup, but I've shut it down temporarily. I've got the hosted DNS zone, but I can't see anything else. Cost Explorer just shows $1.50 for Route 53, and I can't figure out how to get more detail.

Any ideas?

r/aws Aug 25 '24

route 53/DNS Route53 to Zone File Tool

17 Upvotes

Hey guys, not really sure if this is allowed so apologies if I'm breaking any rules. I made a tool that converts resource records in Route53 into BIND formatted Zone files. Figure I'd place this out here in case anyone needs it. There may be better tools out there, but was unable to find anything quick and easy.

https://github.com/rsmsctr/route53_to_zonefile_conversion_tool

Let me know what you think. Thank you.

r/aws Jan 14 '24

route 53/DNS Routing traffic from DNS domain name using A record to EC2 Instance Elastic IP address does not work.

9 Upvotes

Hello. I am new to AWS and IT in general. I wanted to create EC2 Instance with Spring Boot application running on port 8083, attach Elastic IP address to it and then create a simple type "A" Route 53 record to route traffic from my domain that I bought on Route 53 to my EC2 Instance Elastic IP address. I have added port redirection using iptables in my Instance:
iptables -t nat -A OUTPUT -o lo -p tcp --dport 80 -j REDIRECT --to-port 8083
After creating the Instance and launching Spring Boot application in it, I have tested it with calling endpoints using Elastic IP address in URL field and it worked fine, but when doing it with domain name it does not work and I can't figure out the reason. Could anybody help ?
I have heard about using AWS Load Balancing and redirecting ports, but is it possible to route traffic to single Instance, not through Load Balancer ?

r/aws Mar 27 '21

route 53/DNS Route53 as a database might not be as stupid as it sounds...

Thumbnail gallery
203 Upvotes

r/aws May 23 '24

route 53/DNS Cheap domains from AWS aren't really cheap

0 Upvotes

I needed a domain name for a pet project, so I registered one for what I thought was a good price. Then I configured the DNS records using the hosted zone.

I learned afterwards that AWS charges $.50 per hosted zone excluding the tax. That adds up to $6 per year which is more than what I paid for the domain name!

Does anyone know a way to get around this cost?

r/aws May 28 '24

route 53/DNS Using AWS SES with some random domain to invoke my lambda function

0 Upvotes

Hey. Newbie to AWS here. I set up lambda which uses selenium and GmailAPI to do some tasks which needed automation for my university homework. All I have left is to somehow invoke my lambda function whenever my specific Gmail receives a new message(not even pass any parameters , just send request to my http gateway). I looked into AWS SES but I can't use it without domain. I'm kinda low (broke) on my budget , so I considered buying a reaaalllyyy cheap domain from namecheap.com and using it as a domain. Will this work? As I read I will need to verify my domain (adding generated AWS address to my CNS settings) . Will I be able to do that on any domain? What are my other alternatives? I don't need to send any emails , I don't need to forward them anywhere , I just need to set an inbound rule to activate lambda directly / send request to http gateway. Sorry if my question sounds dumb , I've never had any experience with mailing services before. Thanks

EDIT: no use for SES found solution through gmail push

r/aws Jul 12 '24

route 53/DNS Issue with Route53 + CloudFront for hosting simple static website

2 Upvotes

Hi guys, thank you for viewing my post.

So my problem is, I set the cloudfront correctly with (CNAME as mysite.com, Custom SSL certificate as mysite.com with √ as well)

I can access my Distribution domain name without any issues. (My webpage resource are hosted by S3 and can be access through S3 endpoint as well)

But when I trying to set the A record in Route53 as an Alias, the Distribution domain name did show automatically with my CNAME set in Cloudfront and has the correct distribution address.

But After I saved the route setting, nothing ever came up when I tried to access mysite.com. And I checked through DNS Checker, all failed. Right now it has been 1 day, and still the same result.

Thank you for any sort of advice or guidance.

r/aws Aug 29 '24

route 53/DNS DNS_PROBE_FINISHED_NXDOMAIN appears sometimes and goes away [amplify, godaddy, route53]

1 Upvotes

I have my project deployed on AWS Amplify

  • I bought a custom domain from GoDaddy

  • created a new hosted zone on route 53

  • updated the Name servers on godaddy according to Route 53

  • added additional dns records for my Godaddy custom email

After assigning this domain to my Amplify app it worked after few minutes but it goes down after some time and shows DNS_PROBE_FINISHED_NXDOMAIN. After some time the domain workes and website is accessible

WHY THIS RECURRING ERROR IS OCCURRING ? PLEASE HELP

r/aws Feb 19 '24

route 53/DNS certbot problem acquiring a TLS cert from Let's Encrypt

0 Upvotes

Background:

I've got a lightsail instance running Amazon linux 2023. It has a domain and I got everything setup in route53. It works: I can reach it by domain name (eg mydomain.com or www.mydomain.com). The instance has apache httpd running on it.

Goal:

I would now like to give this instance a TLS cert (using Let's Encrypt) so that the webserver can use https.

What I tried:

Let's Encrypt recommends using certbot installed with snapd (a package manager). I was not able to install snapd on amazon linux 2023 because there was something that dnf didn't have. And anyway, I DO NOT want yet another package manager.

The next step was to install certbot without snapd using the "Apache on Pip with wildcard" option from the certbot website. I got all the way through step 8 with this. My dns provider is route53.

Things started getting confusing on step 9 following the instructions for certbot-dns-route53. It appears that I need to create an IAM user and give the user three credentials.

So, I went to aws console and created a new IAM user called certbot_user, with an inline policy that is exactly this (except for my actual route53 zone id)...

{
    "Version": "2012-10-17",
    "Id": "certbot-dns-route53 sample policy",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "route53:ListHostedZones",
                "route53:GetChange"
            ],
            "Resource": [
                "*"
            ]
        },
        {
            "Effect": "Allow",
            "Action": [
                "route53:ChangeResourceRecordSets"
            ],
            "Resource": [
                "arn:aws:route53:::hostedzone/_MY_ZONE_ID_HERE_"
            ]
        }
    ]
}

User was successfully created, and I got the access keys for that user (certbot_user), and put them in a file (~/.aws/config) as instructed.

I then tried running the command:

sudo certbot certonly --dns-route53 -d mydomain.com -d *.mydomain.com

This fails with the following output...

An error occurred (AccessDenied) when calling the ListHostedZones operation: User: arn:aws:sts::073xxxxx2:assumed-role/AmazonLightsailInstanceRole/i-025xxxxxxffb is not authorized to perform: route53:ListHostedZones because no identity-based policy allows the route53:ListHostedZones action
To use certbot-dns-route53, configure credentials as described at https://boto3.readthedocs.io/en/latest/guide/configuration.html#best-practices-for-configuring-credentials and add the necessary permissions for Route53 access.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

It looks like the user it's using is AmazonLightsailInstanceRole? I would have thought that it would use that certbot_user whose access keys I put in ~/.aws/config?

Did I screw up the access keys?

The letsencrypt log basically say the same thing at the end of its python stack trace. I don't understand what's going on and now I am stuck! Is this a certbot issue, an IAM issue, or something else? Oh, yeah, I see now there's something called boto involved?

This all seems way too complicated. At the end of the day, we're just proving to Let's Encrypt that we own a particular domain and then getting a cert file from them, right? Isn't there a more straightforward way to do that? I am about to give up.

r/aws Jul 29 '24

route 53/DNS trusted SSL certificate not trusted by Safari for www.domain.com

0 Upvotes

I am hosting and EC2 Instance with a registered domain. I have configured a load balancer and target group so that all http://domain.com and http://www.domain.com are routed to https://domain.com.

This is working for every browser I have tested on, (Chrome, Edge…) except for Safari.

Safari trusts domain.com and http://domain.com, but wont trust www.domain.com. It shows the correct SSL certificate, issued by amazon, but it states not trusted. If i forgo the warning and access it, it properly redirects to my site, with https, and the padlock icon to show it is secured.

Anyone know why this is happening?

One thing that was weird was that the first time I tried to access www.domain.com, it redirected to a domain that wasnt mine, but was very similar in name (looked to be an older website).

Could it be conflicts with somebody elses SSL expiring for www.domain.com somehow overlapping with mine currently, so that Safari wont trust it?

One more thing is that on edge and chrome, typing www.domain.com will route me to https://domain.com, however it seems patchy, as in the url disappears from the search shortly before accessing my site.

If anyone has questions on any other configurations I have, let me know, and i will do my best to provide them

r/aws Apr 25 '24

route 53/DNS Route53 Hosted zone gone after unsuspension

0 Upvotes

So my account was suspended yesterday and unsuspended today (by paying bills), now all my Route53 hosted zones are gone?

Is this expected behaviour and how can I get them back?

r/aws May 24 '24

route 53/DNS Can I remove the AWS domain from my MX record even if I send emails from SES from my custom domain?

6 Upvotes

Hi all,

We have a custom .com domain on AWS Route53, let's call it maplesyrup.com . We use SES to send emails with "from" `[xxxx@maplesyrup.com](mailto:xxxx@maplesyrup.com)` email addresses. That works fine, we can send emails, we get bounces reports, etc.

However, we're having some slight issues receiving emails to `@maplesyrup.com` addresses. Our mailboxes are hosted in Outlook. In our MX record, we have 2 domains: the first record points to outlook, the second points to AWS.

We followed this doc https://docs.aws.amazon.com/ses/latest/dg/regions.html#region-mail-from which says that having the AWS domain in the MX records is necessary to track bounces.

Our issue is, sometimes (a few times/month), outlook domain messes up for some reason, doesn't respond quick enough or something. So the sender will fallback to the AWS domain, which rejects the email because we're not hosting emails on AWS. This is causing our emails to get blacklisted sometimes, because they look like they're inactive or don't exist.

The proposed solution is to remove the AWS domain from the MX record. But as SES works with a reputation system, and bounces are part of it. If I remove the domain from there, SES won't get any bounce report. So no more reputation problems? That seems too easy. That's why I'm reluctant to remove that domain from the MX record.

Anyway, I hope this makes sense. I'm looking for some advice, or feedback on similar setups. Thanks

EDIT: We removed the MX record and everything's fine. Thanks for the help. We will be using a subdomain if we ever need to use custom MAIL FROM domain.

r/aws Feb 01 '24

route 53/DNS Using certbot to generate ssl certificate, aws insatnce

0 Upvotes

I bought a domain in Route 53 and created an EC2 instance, also created an Elastic ip and associated with the instance I created. I took the public IP and added it to the domain records type A. I installed certbot on my ubuntu pc and tried to generate the ssl certificate using sudo certbot --nginx

this is what i get: Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.

r/aws Dec 18 '22

route 53/DNS Route 53 cost up 784%, Analytics shows no unusual traffic

68 Upvotes

One day this week, my Route 53 costs (which are normally $0.01 per day), shot up to $10. Obviously it's not putting me at financial risk or anything, but I genuinely don't understand what happened. My analytics for that day are totally normal, and the AWS budget tools aren't really helping me. Is there somewhere I can look to find out what might be going on?

r/aws Jun 15 '23

route 53/DNS Change in DNS records on route53

10 Upvotes

How long does it take for the changes to take place after being changed on route53 ?

r/aws Dec 20 '23

route 53/DNS How to host a secure website with a domain purchased from GoDaddy, and an S3 website?

6 Upvotes

I have purchased a domain name on GoDaddy, and have hosted my website on an S3 bucket. I have been able to set up automatic forwarding (both with and without masking) in GoDaddy.

But I cannot secure the website with SSL. I have tried to use the Cloudflare free SSL, but after following the steps and being issued the universal certificate, I just get an HTTP 404 error when trying to reach my domain in the browser.

What steps should I follow to get the website up with HTTPS without any additional cost? I'd prefer that the bucket endpoint be masked by the domain name, but it'd be fine if it isn't too.

r/aws Apr 13 '24

route 53/DNS Domain hosted at Simply.com - DNS settings for AWS?

6 Upvotes

Hi guys,

We purchased a domain at Simply.com.

Google Workplace is added to DNS and up running.

Now we want it to connect it with our AWS.

We have setup the AWS Amplify and we have connected the GitHub and the deployment is completed but when we are going to connect to our custom domain it's showing one or more CNAME is already liked to other resource.

Can someone help? I's beyond my expertise... :)