By using AWS re:Post, you agree to the Terms of Use
/Amazon Route 53/

Questions tagged with Amazon Route 53

Sort by most recent
  • 1
  • 90 / page

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Hosting many Static Sites with Single Cloudfront Distrubation

Hello, i’m planing to build a SaaS Plattform like Shopify. part of my business will be that the customer can have their own domain on which their shop runs. I’ve solved everything on aws so far, but I’m now coming up against a limit (number of S3 buckets and the domain assignment). My principle when creating my platform was always that it scales from 1 to 10000 without resorting to servers or manually switching anything later in production. I found a solution here, where u use 1 cloudfront distro with 1 s3 bucket with multiple directorys : https://repost.aws/questions/QUJCmEN5YvTdevcBub9nlW5w/hosting-1000-s-of-static-sites but i wonder what the limitation of ssl certificates has to do with it. without increasing the limit I can only use 10 domains with SSL? example.com shop.com test.com ... If so, what can the limit be increased to? Can it be that AWS denies my limit increase? I ask myself the same thing for domains in Route53, there I have a limit of 20, to what can this generally be increased? Edit: i just found out about Amplify. this service seems also nice, i could use amplify for the static site generation and use 1 s3 bucket with all the images. but it also has a limit of 25. does anybody know how much i can increase the limit? I also can not find anyway of explaining my limit increase or contact the support. it would be really nice to know beforehand what limit i can expect before building my plattform and than later to change it again because of the limit
0
answers
1
votes
47
views
asked a day ago

ACM Cert Renewal Problem when GoDaddy is the Registrar

I recently received an email from AWS saying that my cert was about to expire and that since I had email validation turned on they had sent me a separate email with a link to verify renewal. I never received the separate e-mail. My domain is hosted on Route53 but GoDaddy is the registrar. I finally figured out that since ACM uses the email addresses in the whois records as the authoritative e-mail address for validating cert renewals, it doesn't work with certain godaddy domain configurations. At godaddy, I had their privacy features turned on. I finally figured out that godaddy has stopped putting valid email addresses into whois records and instead puts links to the godaddy web site in those whois fields. That means that any emails sent from ACM will never arrive or will silently fail to send. I worked around the problem by briefly turning off domain privacy at godaddy, then having ACM resend the emails, then turning privacy back on. But as long as godaddy doesn't write valid email addresses in the whois records ACM email validation won't work for domains registered at godaddy ***that have privacy turned on***. This is actually a godaddy bug, but it bites anyone who is hosting their zone at route53 and using ACM certs. In the past, godaddy would write a valid email address in whois records (e.g. foo.com@domainsbyproxy.com) and forward emails sent to that address to the domain name owner. Not anymore. I'm just posting this here for the benefit of anyone who has a domain registered at godaddy but is using ACM certs on AWS.
0
answers
2
votes
29
views
asked 8 days ago

CDK Route 53 zone lookup brings back wrong zone ID

We are attempt to update our IaC code base to CDK v2. Prior to that we're deploy entire stacks of our system in another test environment. One part of a stack creates a TLS certificate for use with our load balancer. ``` var hostedZone = HostedZone.FromLookup(this, $"{config.ProductName}-dns-zone", new HostedZoneProviderProps { DomainName = config.RootDomainName }); DnsValidatedCertificate certificate = new DnsValidatedCertificate(this, $"{config.ProductName}-webELBCertificate-{config.Environment}", new DnsValidatedCertificateProps { HostedZone = hostedZone, DomainName = config.AppDomainName, // Used to implement ValidationMethod = ValidationMethod.DNS Validation = CertificateValidation.FromDns(hostedZone) }); ``` For some reason, the synthesised template defines the hosted zone ID for that AWS::CloudFormation::CustomResource has *something else other than the actual zone ID* in that account. That causes the certificate request validation process to fail - thus the whole cdk deploy - since it cannot find the real zone to place the validation records in. If looking at the individual pending certificate requests in Certificate Manager page, they can be approved by manually pressing the [[Create records in Route 53]] button, which finds the correct zone to do so. Not sure where exactly CDK is finding this mysterious zone ID that does not belong to us? ``` "AppwebELBCertificatetestCertificateRequestorResource68D095F7": { "Type": "AWS::CloudFormation::CustomResource", "Properties": { "ServiceToken": { "Fn::GetAtt": [ "AppwebELBCertificatetestCertificateRequestorFunctionCFE32764", "Arn" ] }, "DomainName": "root.domain", "HostedZoneId": "NON-EXISTENT ZONE ID" }, "UpdateReplacePolicy": "Delete", "DeletionPolicy": "Delete", "Metadata": { "aws:cdk:path": "App-webELBStack-test/App-webELBCertificate-test/CertificateRequestorResource/Default" } } ```
1
answers
0
votes
13
views
asked a month ago
  • 1
  • 90 / page