Can't communicate with API hosting on AWS EC2 via https

By -

Problem: I can send an HTTP request to my website hosted on an EC2 instance via the auto-generated IPv4 DNS (ec2-12-345-67-899.compute-1.amazonaws.com) and receive a correct response, but when I try to send an HTTPS request, the page keeps loading and I eventually got "ec2-12-345-67-899.compute-1.amazonaws.com took too long to respond"

Details:

  • I am using Flask, Gunicorn as the webserver, and Nginx as the reverse proxy server
  • Here is my Nginx configuration file:
server {
    listen 443;
    listen 80;
    server_name ec2-12-345-67-899.compute-1.amazonaws.com;

    location / {
        proxy_pass http://localhost:5000;
    }
}

  • Here is what it looks like when I start my gunicorn server: gunicorn running

  • Here is my EC2's instance Sercurity Group:

ec2 security group

Notes: I'm a beginner so I don't know if the above information is enough. Please let me know if there's other information I need to provide.

I thought the DNS provided by the EC2 instance should be SSL-certified? If it's not then do I need to get an SSL certification and put the link to it in my Nginx Configuration file?

I tried to use Let's Encrypt but it said it cannot provide a certificate for the requested domain name (probably because the domain name belongs to Amazon).

My ultimate goal is to be able to communicate with my website hosted on EC2 instance via HTTPS. Is buying a domain name the only way?



from Recent Questions - Stack Overflow https://ift.tt/3rDAlj0
https://ift.tt/3BQ8LUm

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more