Browse through the questions and answers listed below or filter and sort to narrow down your results.
Can't add AWS Certificate Manager to domain
Hello. 1. Previously, I created it through DNS validation and connected it to the domain "storyflow.link" (which is registered through AWS tools) through "Create DNS records in Amazon Route 53" 2. Currently the CNAME fields appear in "Hosted zones" but the status does not change (Pending validation) 3. I cannot add "add listener" - HTTPS to the Configuration of Elastic Beanstalk. A message appears: Creating Load Balancer listener failed Reason: Resource handler returned message: "The certificate '*****' must have a fully-qualified domain name , a supported signature, and a supported key size. (Service: ElasticLoadBalancingV2, Status Code: 400, Request ID: *****, Extended Request ID: null)" (RequestToken: ****, HandlerErrorCode: InvalidRequest).
CloudFront with ECS Blue/Green Deployments
I have a setup with CloudFront as CDN and application on ECS cluster. As we are using ECS Blue/Green deployment, production listener port 443 & test listener port 8443 are being used in ECS service and the same ports are registered as listeners in application load balancer. Route 53 A record has alias to Cloudfront distribution. And the origin is application load balancer and only https traffic on 443 port is allowed in CloudFront distrubution. When request is sent to application on 443 port for example, portal.example.com; it works. But the request is timed out when it is sent on 8443 port for example, portal.example.com:8443. I am able to launch application on both ports using Application Load Balancer's domain name which means there is no restriction on 8443 port at Load Balancer, EC2, VPC, Subnet, Security Group or NACL layers. I thought the issue is due to https port configured on CloudFront distribution and changed it to 8443. Still portal.example.com:8443 doesn't work and getting timed out. I couldn't get why the request is not passing through cloudfront and reaching load balancer on 8443 port. Any suggestions would be appreciated. Note: There is no WAF ACL used in cloudfront
Validation timed out for SSL certificate with domain transferred from Wordpress (Gandi.net)
I transferred a domain from wordpress more than a month ago and cannot seem to successfully validate the domain for a SSL cert in Certificate manager. Gandi keeps pointing me back to AWS stating "They are in charge of everything from A to Z". How do I resolve this issue?
Domain registration failed
I have status: Domain registration failed: [Parameters in request are not valid]. All that I see in route 53 it is this notification about registration failed, other tabs like a 'Registered domains', 'Pending requests' are empty. And I don’t know what to do now to resolve this problem, I can’t find where I should change this parameters to register done, or return my money that I spent on this.
How2 Create SSL Certificates for IDNs (puny code) for Lightsail instances?
I'm currently working for a Bulgarian client that is using an International Domain Name (IDN). The domain is in Cyrillic (Bulgarian). I have converted the IDN to the appropriate puny code. However, when I try to create the ssl certificate on my Lightsail instance for Wordpress in the Bitnami stack using the bncert-tool, the tool doesn't recognise the puny code nor the Bulgarian language domain. the tool keeps asking me to "enter a valid domain name". Therefore, I can't create the certificates and secure the traffic to my customer's site. How can I create SSL certificates for Lightsail instances for IDNs? Help me obi wan, you're my only hope ;-) thanks!
502 ERROR || The request could not be satisfied
Generated by cloudfront (CloudFront) Request ID: Q8ButBHQ_qu22oo0A59rNSox60_lT9e2S4dKQE_XkA8z5wWt_gcHwQ== My website is not working from over a month Please Help!!! CloudFront attempted to establish a connection with the origin, but either the attempt failed or the origin closed the connection. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
My domain on Route 53 is not reaching my server created on AWS Lightsail
Hi AWS folk! I am trying to create my own website using AWS Route 53 and Lightsail. In Route 53, I registered a domain somedomain.com, and created a public hosted zone. The hosted zone configuration has four name servers that match the "Value/Route traffic to" of the NS record of the hosted zone. In Lightsail, I have created a Wordpress website. I provided a static IP to the Lightsail instance. Under Networking, I created a DNS zone (using the registered domain somedomain.com from the previous step) which had also four name servers (different from the four name servers in Route 53). Now when I try to reach my website using the instance's static IP address it works perfectly. However, when I browse using my domain name I keep getting "This site can’t be reached". Here's my configuration of the Route 53 Hosted zone ![Route 53 configuration](/media/postImages/original/IMmuW1VRmcRGi2UdEJXtXClw) Here's the configuration of the DNS zone on Lightsail: ![Lightsail configuration](/media/postImages/original/IMANmOdVs1TmyZ-rrc5loOGw) Am I missing something or maybe have some wrong configuration? Any help is highly appreciated!
Newbie here. CNAME vs Alias
I have a Domain say "www.example.com" which is hosted on Salesforce. I have a CNAME (www) record that points "www.example.com" to Salesforce Host Server. I do not have a IP address, so no 'A' Record. So far, it all works fine. The problem is "example.com" (naked domain) is a dead end for users. I was wondering that I could use Alias record that points "example.com" to "www.example.com". So to say both "example.com" and "www.example.com" both should point to the same Salesforce Host Server. But I see a note that got me confused. **URL:** https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-choosing-alias-non-alias.html **Paragraph:** Unlike a CNAME record, you can create an alias record at the top node of a DNS namespace, also known as the zone apex. For example, if you register the DNS name example.com, the zone apex is example.com. You can't create a CNAME record for example.com, but you can create an alias record for example.com that routes traffic to www.example.com (as long as www.example.com doesn't already have a CNAME record). My confusion - "(as long as www.example.com doesn't already have a CNAME record)" got me offtrack. CNAME record for www.example.com has to exist, right? Along with CNAME if I also create a ALIAS record will that not solve my problem?