I currently have an sftp site setup on AWS where I can connect via Filezilla by providing the long AWS Public DNS name or the Public IP address(hostname) along with my credentials.
I have an existing domain abc.com which is hosted elsewhere(not aws). I want to use a sub domain such as sftp.abc.com to connect to my sftp site instead of the IP address.
Can I create the subdomain(sftp.abc.com) on AWS using Route53? If so, how do I accomplish this?
Would this affect my primary domain site abc.com ?
Anyone who can give me some advice on this would be helpful. Thanks
Create a hosted zone in Route 53 for the subdomain - e.g. sftp.abc.com. Amazon will specify 4 nameservers for the hosted zone. Simply go into your root DNS and create an NS record for the subdomain, specifying those 4 nameservers, and it should delegate authority for the subdomain to Route 53.
Related
I have a domain example.tld that is registered with one company and hosted with another. That website uses https and has a let's encrypt certificate setup by the hosting company through an automated script. I'm trying to an s3 bucket accessible from sub.example.tld.
I currently have a public s3 bucket and a CNAME setup with my hosting company to point sub to my bucket. I'm able to access the contents of my bucket from the http and https protocols using an Amazon generated domain, and from http only from sub.example.tld.
I know I can setup s3 with cloudflare and and use a cname with https there, however, since my domain name isn't hosted with aws I have to upload import a certificate which I do not have.
What I'm thinking of how I can proceed is to create a hosted zone in route 53 for sub.example.tld. Then I can delete the current CNAME registration with my hosting company to the bucket and instead create some kind of DNS record with my hosting company to point sub to the hosted zone with Amazon.
I'm able to create the following DNS records: A, CNAME, MX, NS, TXT, SRV, AAAA, DNAME, and CAA.
Does my idea of creating a hosted zone for the subdomain make sense? And if so, what type of DNS record would I create with my host to allow me to have a subdomain managed elsewhere?
I have a simple AWS setup of 2 VMs hosting a WebApp. An Application Load Balancer is in-front of these machines. I can access the DNS name of the Load Balancer and can reach to the WebApp.
Now, I want to connect to my app with a domain name hosted on Godaddy. I tried to simply create CNAME (as no Elastic IP on Application LB) with the LB's DNS name, but it didn't work.
What am I missing ? I tried with godaddy support but already wasted 7 days with not solution.
I want to put SSL certificate also on ALB. Should I be aware of anything specific in this setup?
The problem was, I was trying to CNAME for root level domain. Now, I created an alias in Route 53 and used AWS's nameservers on Godaddy to forward request there.
I purchased domain name from GoDaddy. www.***ta.com
I am using AWS to host virtual machine (EC2 instance).
Now my web site is up and running on EC2 instance. I can access my webpage from public IP address.
I want to use domain that i purchased from GoDaddy www.***ta.com.
I follow online help
Create hosted zone add record set
Type A - with public IP4 in AWS Route 53 and public ip address of EC2 machine.
When i tested it works on AWS but not from the browser.
Anything missing? can you please provide some inputs?
You can either set the DNS records in godaddy DNS zone or Map the DNS servers to Route53 and then create the Zone file.
For setting DNS in Godaddy -
Go to Manage DNS and select your domain.
Add a A record - Enter the IP of your EC2 instance as value and # as key.
Add another CNAME Record - www as key value as #
After sometime your domain will start working.
For setting DNS in Route53 -
Go to Route53 and create a domain by entering your domain name.
In godaddy changethe DNS server 1, server 2, server 3, server 4 to the Name Servers received from Route 53.
after 24 hours your Domain name servers will start pointing to Route53.
Now come back to Route53 and add A record with your ec2 instance IP address.
I have a domain for instance example.com.
The domain is hosted by a third party service (Digital Ocean).
I would like to give control of a subdomain to AWS.
So I would like to point aws.example.com to AWS.
Once the root subdomain is pointed to AWS. I would like to use Route 53 to setup the following functionality:
aws.example.com => alias to eb my-production-eb
dev.aws.example.com => alias to eb my-dev-eb
stage.aws.example.com => alias to eb my-stage-eb
Is this possible? Do I have to point my domains directly via cname record to the AWS load balancer?
Update 1:
I feel like I need to set the following in Digital Ocean:
aws.example.com => revoke control to AWS Route 53 somehow
*.aws.example.com => revoke control to AWS Route 53 somehow
Update 2:
The AWS documentation for Creating a Subdomain That Uses Amazon Route 53 as the DNS Service without Migrating the Parent Domain does not work for Digital Ocean.
Do not add a start of authority (SOA) record to the zone file for the parent domain. Because the subdomain will use Amazon Route 53, the DNS service for the parent domain is not the authority for the subdomain.
If your DNS service automatically added an SOA record for the subdomain, delete the record for the subdomain. However, do not delete the SOA record for the parent domain.
The question on Digital ocean regarding changing the SOA address titled "How can I change the SOA address in DNS settings?" states the following in one of the comments.
Unfortunately it is not possible to edit the SOA address right now
There is the ability to vote for this feature in Digital Ocean Configurable SOA record in DNS.
So my idea is that because you can't remove the SOA on Digital Ocean Amazon can't communicate to the domain correctly.
You need to delegate the DNS subdomain aws.example.com to Route 53.
See Creating a Subdomain That Uses Amazon Route 53 as the DNS Service without Migrating the Parent Domain
You can create a subdomain that uses Amazon Route 53 as the DNS
service without migrating the parent domain from another DNS service.
The basic steps are:
Create an Amazon Route 53 hosted zone for the subdomain.
Add resource record sets for the new subdomain to your Amazon Route 53 hosted
Update the DNS service for the parent domain by adding name server records for the subdomain provided in Step 1.
Assuming the current TLD example.com is hosted at Digital Ocean, then you need to create NS resource records there for the aws subdomain, using the name servers Route 53 provides you when create the hosted zone for aws.example.com.
Then you can control all hosts *.aws.example.com, including CNAMES for ELBs etc. from Route 53.
Yes, you can have any number of subdomains whether they are A or CNAME records, just point them to the target (public) IP.
I'm using EC2 of Amazon to host a website built in JSP :
http://ec2-50-17-144-64.compute-1.amazonaws.com:8080/p2p
And I bought this domain:
www.p2pbrasil.com
How can I redirect www.p2pbrasil.com to my website in Amazon EC2 ?
When someone type www.p2pbrasil.com it redirects to http://ec2-50-17-144-64.compute-1.amazonaws.com:8080/p2p ?
You need to do two things
In the Amazon Web Service admin panel, create an elastic IP in the same region as your instance and associate that IP with your that instance (IPs cost nothing while they are associated with an instance, but do cost if not).
Add a A record to the DNS record of your domain mapping the domain to the elastic IP address assigned in (1). Your domain provide should either give you some way to set the A record (the IP address), or it will give you a way to edit the nameservers of your domain.
If they do not allow you to set the A record directly, find a DNS management service like ZoneEdit, register your domain as a zone there and ZoneEdit will give you the nameservers to enter in the admin panel of your domain provider. You can then add the A record for the domain in ZoneEdit.
I only mention ZoneEdit because the basic service is free, you could also use Amazon route 53 or a similar pay-for service, if you preferred.
Create an Elastic IP on the AWS Panel, then associate it to your instance.
Then use a DNS management service to add your domain and Ip address (Elastic IP), then on the domain provider panel add the DNS provided from the DNS management service.
I recommend EntryDNS which is actually free.
As you have your server on AWS best option is to use Route53 hosted zone.By doing this you can manage all your DNS entries using AWS. In future if you plan to use ELB's for your application, you can various traffic routing options using Route53.
Create Hosted Zone and get the name servers.
Replace current name servers with AWS nameservers from your Domain registrars DNS entries.
Create an A record in AWS hosted zone and give your servers IP (Elastic IP) as value.
For detailed instruction, you can follow this blog post. Mapping Domain Name to EC2 Server
Assuming this is a hobby website and your domain registrar isn't AWS.
If your registrar (for example godaddy.com) provides a DNS manager you simply need to add a CNAME record for www that points to the aws public DNS record for your instance. For example ec2-50-17-144-64.compute-1.amazonaws.com
This will make http://www.p2pbrasil.com display the same content as http://ec2-50-17-144-64.compute-1.amazonaws.com
Doing it this way you don't have to pay for an elastic IP, which is a dedicated resource. Your IP on your ec2 instance shouldn't change but could if you restart your instance.
Put the public IP from your EC2 instance as an A name to your root domain in Route 53 hosted zone.
This change might take some time.