aws-certificate-manager

问题 While certificate manager UI shows my imported certificated with status "issued" , when trying to use it from an ELB (application lb) I get: " no certificates available " (the POST request to the api returns with empty list) Also when I run aws acm list-certificates --max-items 10 I don't get the imported certificate , only my second (Not imported) one Any ideas what's wrong here? is there a setting on the imported certificate I should be configuring? 回答1: I've got only half answer here: but

问题 I've just started using AWS a week ago. I deployed my NodeJS backend in a Docker container via Elastic Beanstalk. And a front-end Angular5 app in an S3 via CloudFront. I bought a domain name on GoDaddy and configured it to point to my CloudFront Angular5 app. I also generated an SSL certificate for that domain (used for the front-end). However, all requests from the frontend app are getting blocked due to the backend insecurity. So, as I understand, the next step would be to configure HTTPS

来源： https://stackoverflow.com/questions/63779272/aws-elastic-beanstalk-ssl-certificate-added-but-still-https-error-ssl-error-b

问题 Someone purchased a wildcard certificate via AWS Certificate Manager for their domain name and I need to transfer it to Heroku for an app that uses a sub-domain of the domain name. I can't figure out, either through the AWS Console or through their CLI, how I would get the private key used to generate the CSR for this certificate? Can anyone on here help me? 回答1: You can't. That's one of the points of using AWS Certificate Manager: the private keys won't leave AWS infrastructure. You can't

问题 Someone purchased a wildcard certificate via AWS Certificate Manager for their domain name and I need to transfer it to Heroku for an app that uses a sub-domain of the domain name. I can't figure out, either through the AWS Console or through their CLI, how I would get the private key used to generate the CSR for this certificate? Can anyone on here help me? 回答1: You can't. That's one of the points of using AWS Certificate Manager: the private keys won't leave AWS infrastructure. You can't

问题 I have a few AWS accounts where I manage DNS addresses and ACM SSL certificates. I have a top-level.com domain in one account and another account manages subdomain.top-level.com. I created some SSL certificates with ACM on the top account for example: example.subdomain.top-level.com. But now I'd like to use the same certificate in my subdomain account. Is there a way to share these certificates between my accounts? 回答1: Reply from Amazon: ... Unfortunately it is not possible to share ACM

问题 I already have a certificate from AWS Certificate Manager (ACM) when only the 1 region was available (think the US-West-1 region?) and currently being used with Cloudfront to host a website for the Australian market. Now that ACM is available in more regions, would using a certificate created from the Sydney region have any improvements in performance? 回答1: ACM now supports multiple regions, but that doesn't have any implications for certificates for use with CloudFront. To use an ACM

问题 I am working with an AWS EC2 instance (amazon Linux, elastic IP) trying to set up SSL through ACM. The certificate is verified and the load balancer is passing the health checks listening on prot 443, forwarding to port 80. Initially, when testing https I received a connection refused. This confused me because I thought the load balancer would catch and forward this to port 80. I enabled port 443 via nginx on the EC2 instance, so now it is listening on 443 (tested via telnet), which got rid

问题 I am working with an AWS EC2 instance (amazon Linux, elastic IP) trying to set up SSL through ACM. The certificate is verified and the load balancer is passing the health checks listening on prot 443, forwarding to port 80. Initially, when testing https I received a connection refused. This confused me because I thought the load balancer would catch and forward this to port 80. I enabled port 443 via nginx on the EC2 instance, so now it is listening on 443 (tested via telnet), which got rid

问题 I am working with an AWS EC2 instance (amazon Linux, elastic IP) trying to set up SSL through ACM. The certificate is verified and the load balancer is passing the health checks listening on prot 443, forwarding to port 80. Initially, when testing https I received a connection refused. This confused me because I thought the load balancer would catch and forward this to port 80. I enabled port 443 via nginx on the EC2 instance, so now it is listening on 443 (tested via telnet), which got rid