Mixing
![What should I do when my employer stopped paying me without informing/discussing with me during my leave when I worked remotely? [closed]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgjbpfN9tAutmK93bJRC3ZoROZzi2TJDms5n8_qJuhgE0a9b52OOHayv3NGT8igAdFL7byXNst-_1DZK5SjrIJ28_6RQPUpBROqMs5s6jo-ZsjX8kjDwfxJufIitH3TaQRXWaGSQKRQib-f/s72-c/1.jpg)
AWS Solution for wildcard subdomains (with SSL)
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
Is there a solution within AWS for implementing a wildcard subdomain (with Route 53). where any subdomain ex1.example.com, ex2.example.com or whatever.example.com can all point to the same server? This server would then have a wildcard SSL cert to allow for the subdomains.
Is this possible?
amazon-web-services subdomain amazon-route53
asked 2 hours ago
Larry
111
New contributor
Larry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
2
down vote
favorite
Is there a solution within AWS for implementing a wildcard subdomain (with Route 53). where any subdomain ex1.example.com, ex2.example.com or whatever.example.com can all point to the same server? This server would then have a wildcard SSL cert to allow for the subdomains.
Is this possible?
amazon-web-services subdomain amazon-route53
asked 2 hours ago
Larry
111
New contributor
Larry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Is there a solution within AWS for implementing a wildcard subdomain (with Route 53). where any subdomain ex1.example.com, ex2.example.com or whatever.example.com can all point to the same server? This server would then have a wildcard SSL cert to allow for the subdomains.
Is this possible?
amazon-web-services subdomain amazon-route53
asked 2 hours ago
Larry
111
New contributor
Larry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Is there a solution within AWS for implementing a wildcard subdomain (with Route 53). where any subdomain ex1.example.com, ex2.example.com or whatever.example.com can all point to the same server? This server would then have a wildcard SSL cert to allow for the subdomains.
Is this possible?
amazon-web-services subdomain amazon-route53
amazon-web-services subdomain amazon-route53
asked 2 hours ago
Larry
111
New contributor
Larry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 hours ago
Larry
111
New contributor
Larry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 hours ago
Larry
111
New contributor
Larry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 hours ago
Larry
111
asked 2 hours ago
Larry
111
111
New contributor
Larry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Larry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Larry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
add a comment |Â
3 Answers
3
active
oldest
votes
up vote
2
down vote
Route53 does support wildcards (from the Route53 FAQ):
Q. Does Amazon Route 53 support wildcard entries? If so, what record
types support them?
Yes. To make it even easier for you to configure DNS settings for your
domain, Amazon Route 53 supports wildcard entries for all record
types, except NS records. A wildcard entry is a record in a DNS zone
that will match requests for any domain name based on the
configuration you set. For example, a wildcard DNS record such as
*.example.com will match queries for www.example.com and subdomain.example.com.
You will need to obtain a wildcard SSL certificate separately and host it on any servers accepting these requests.
answered 1 hour ago
guzzijason
782114
add a comment |Â
up vote
1
down vote
Not with route 53 but with a Load Balancer. Checkout ACM. You will have to create
your wildcard certificate. It is free but you won't have access to it.
If you need a secure connection between the Load Balancer and your server, you will have to install your own on this server.
answered 1 hour ago
Kaymaz
134
It's entirely possible to have a wildcard subdomain on AWS without needing ACM and a load balancer.
– ceejayoz
2 mins ago
add a comment |Â
up vote
1
down vote
Sure AWS can do that.
Set a wildcard CNAME record
*.example.comin Route53 that points to your AWS ELB (Elastic Load Balancer), AWS ALB (Application Load Balancer) or directly to your HTTP Server.If you are using ELB/ALB do not create the wildcard as A-records for the IP addresses as they may change over time. Either create CNAME or ALIAS!
If you're using ELB/ALB check out AWS ACM (Amazon Certificate Manager) - it can create and manage free SSL certificates that you can use with ELB/ALB.
If you're not using ELB/ALB you will either have to buy a commercial wildcard cert or use LetsEncrypt wildcard certificate, however that's a bit of a pain to renew as the challenge handshake must be done through DNS / Route53.
If your website is at least a little important I suggest you look at ALB + ACM instead of terminating the traffic directly on the web server.
Hope that helps :)
answered 1 hour ago
MLu
2,2181225
add a comment |Â
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
Route53 does support wildcards (from the Route53 FAQ):
Q. Does Amazon Route 53 support wildcard entries? If so, what record
types support them?
Yes. To make it even easier for you to configure DNS settings for your
domain, Amazon Route 53 supports wildcard entries for all record
types, except NS records. A wildcard entry is a record in a DNS zone
that will match requests for any domain name based on the
configuration you set. For example, a wildcard DNS record such as
*.example.com will match queries for www.example.com and subdomain.example.com.
You will need to obtain a wildcard SSL certificate separately and host it on any servers accepting these requests.
answered 1 hour ago
guzzijason
782114
add a comment |Â
up vote
2
down vote
Route53 does support wildcards (from the Route53 FAQ):
Q. Does Amazon Route 53 support wildcard entries? If so, what record
types support them?
Yes. To make it even easier for you to configure DNS settings for your
domain, Amazon Route 53 supports wildcard entries for all record
types, except NS records. A wildcard entry is a record in a DNS zone
that will match requests for any domain name based on the
configuration you set. For example, a wildcard DNS record such as
*.example.com will match queries for www.example.com and subdomain.example.com.
You will need to obtain a wildcard SSL certificate separately and host it on any servers accepting these requests.
answered 1 hour ago
guzzijason
782114
add a comment |Â
up vote
2
down vote
up vote
2
down vote
Route53 does support wildcards (from the Route53 FAQ):
Q. Does Amazon Route 53 support wildcard entries? If so, what record
types support them?
Yes. To make it even easier for you to configure DNS settings for your
domain, Amazon Route 53 supports wildcard entries for all record
types, except NS records. A wildcard entry is a record in a DNS zone
that will match requests for any domain name based on the
configuration you set. For example, a wildcard DNS record such as
*.example.com will match queries for www.example.com and subdomain.example.com.
You will need to obtain a wildcard SSL certificate separately and host it on any servers accepting these requests.
answered 1 hour ago
guzzijason
782114
Route53 does support wildcards (from the Route53 FAQ):
Q. Does Amazon Route 53 support wildcard entries? If so, what record
types support them?
Yes. To make it even easier for you to configure DNS settings for your
domain, Amazon Route 53 supports wildcard entries for all record
types, except NS records. A wildcard entry is a record in a DNS zone
that will match requests for any domain name based on the
configuration you set. For example, a wildcard DNS record such as
*.example.com will match queries for www.example.com and subdomain.example.com.
You will need to obtain a wildcard SSL certificate separately and host it on any servers accepting these requests.
answered 1 hour ago
guzzijason
782114
answered 1 hour ago
guzzijason
782114
answered 1 hour ago
guzzijason
782114
answered 1 hour ago
guzzijason
782114
782114
add a comment |Â
add a comment |Â
up vote
1
down vote
Not with route 53 but with a Load Balancer. Checkout ACM. You will have to create
your wildcard certificate. It is free but you won't have access to it.
If you need a secure connection between the Load Balancer and your server, you will have to install your own on this server.
answered 1 hour ago
Kaymaz
134
It's entirely possible to have a wildcard subdomain on AWS without needing ACM and a load balancer.
– ceejayoz
2 mins ago
add a comment |Â
up vote
1
down vote
Not with route 53 but with a Load Balancer. Checkout ACM. You will have to create
your wildcard certificate. It is free but you won't have access to it.
If you need a secure connection between the Load Balancer and your server, you will have to install your own on this server.
answered 1 hour ago
Kaymaz
134
It's entirely possible to have a wildcard subdomain on AWS without needing ACM and a load balancer.
– ceejayoz
2 mins ago
add a comment |Â
up vote
1
down vote
up vote
1
down vote
Not with route 53 but with a Load Balancer. Checkout ACM. You will have to create
your wildcard certificate. It is free but you won't have access to it.
If you need a secure connection between the Load Balancer and your server, you will have to install your own on this server.
answered 1 hour ago
Kaymaz
134
Not with route 53 but with a Load Balancer. Checkout ACM. You will have to create
your wildcard certificate. It is free but you won't have access to it.
If you need a secure connection between the Load Balancer and your server, you will have to install your own on this server.
answered 1 hour ago
Kaymaz
134
answered 1 hour ago
Kaymaz
134
answered 1 hour ago
Kaymaz
134
answered 1 hour ago
Kaymaz
134
134
It's entirely possible to have a wildcard subdomain on AWS without needing ACM and a load balancer.
– ceejayoz
2 mins ago
add a comment |Â
It's entirely possible to have a wildcard subdomain on AWS without needing ACM and a load balancer.
– ceejayoz
2 mins ago
It's entirely possible to have a wildcard subdomain on AWS without needing ACM and a load balancer.
– ceejayoz
2 mins ago
It's entirely possible to have a wildcard subdomain on AWS without needing ACM and a load balancer.
– ceejayoz
2 mins ago
add a comment |Â
up vote
1
down vote
Sure AWS can do that.
Set a wildcard CNAME record
*.example.comin Route53 that points to your AWS ELB (Elastic Load Balancer), AWS ALB (Application Load Balancer) or directly to your HTTP Server.If you are using ELB/ALB do not create the wildcard as A-records for the IP addresses as they may change over time. Either create CNAME or ALIAS!
If you're using ELB/ALB check out AWS ACM (Amazon Certificate Manager) - it can create and manage free SSL certificates that you can use with ELB/ALB.
If you're not using ELB/ALB you will either have to buy a commercial wildcard cert or use LetsEncrypt wildcard certificate, however that's a bit of a pain to renew as the challenge handshake must be done through DNS / Route53.
If your website is at least a little important I suggest you look at ALB + ACM instead of terminating the traffic directly on the web server.
Hope that helps :)
answered 1 hour ago
MLu
2,2181225
add a comment |Â
up vote
1
down vote
Sure AWS can do that.
Set a wildcard CNAME record
*.example.comin Route53 that points to your AWS ELB (Elastic Load Balancer), AWS ALB (Application Load Balancer) or directly to your HTTP Server.If you are using ELB/ALB do not create the wildcard as A-records for the IP addresses as they may change over time. Either create CNAME or ALIAS!
If you're using ELB/ALB check out AWS ACM (Amazon Certificate Manager) - it can create and manage free SSL certificates that you can use with ELB/ALB.
If you're not using ELB/ALB you will either have to buy a commercial wildcard cert or use LetsEncrypt wildcard certificate, however that's a bit of a pain to renew as the challenge handshake must be done through DNS / Route53.
If your website is at least a little important I suggest you look at ALB + ACM instead of terminating the traffic directly on the web server.
Hope that helps :)
answered 1 hour ago
MLu
2,2181225
add a comment |Â
up vote
1
down vote
up vote
1
down vote
Sure AWS can do that.
Set a wildcard CNAME record
*.example.comin Route53 that points to your AWS ELB (Elastic Load Balancer), AWS ALB (Application Load Balancer) or directly to your HTTP Server.If you are using ELB/ALB do not create the wildcard as A-records for the IP addresses as they may change over time. Either create CNAME or ALIAS!
If you're using ELB/ALB check out AWS ACM (Amazon Certificate Manager) - it can create and manage free SSL certificates that you can use with ELB/ALB.
If you're not using ELB/ALB you will either have to buy a commercial wildcard cert or use LetsEncrypt wildcard certificate, however that's a bit of a pain to renew as the challenge handshake must be done through DNS / Route53.
If your website is at least a little important I suggest you look at ALB + ACM instead of terminating the traffic directly on the web server.
Hope that helps :)
answered 1 hour ago
MLu
2,2181225
Sure AWS can do that.
Set a wildcard CNAME record
*.example.comin Route53 that points to your AWS ELB (Elastic Load Balancer), AWS ALB (Application Load Balancer) or directly to your HTTP Server.If you are using ELB/ALB do not create the wildcard as A-records for the IP addresses as they may change over time. Either create CNAME or ALIAS!
If you're using ELB/ALB check out AWS ACM (Amazon Certificate Manager) - it can create and manage free SSL certificates that you can use with ELB/ALB.
If you're not using ELB/ALB you will either have to buy a commercial wildcard cert or use LetsEncrypt wildcard certificate, however that's a bit of a pain to renew as the challenge handshake must be done through DNS / Route53.
If your website is at least a little important I suggest you look at ALB + ACM instead of terminating the traffic directly on the web server.
Hope that helps :)
answered 1 hour ago
MLu
2,2181225
answered 1 hour ago
MLu
2,2181225
answered 1 hour ago
MLu
2,2181225
answered 1 hour ago
MLu
2,2181225
2,2181225
add a comment |Â
add a comment |Â
Larry is a new contributor. Be nice, and check out our Code of Conduct.
Larry is a new contributor. Be nice, and check out our Code of Conduct.
Larry is a new contributor. Be nice, and check out our Code of Conduct.
Larry is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f934645%2faws-solution-for-wildcard-subdomains-with-ssl%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
