Nginx欢迎页面返回

我在EC2实例上运行Nginx。 我有一个网页安装在默认的/usr/share/nginx/html目录中。 我注意到，如果我使用AMI创build一个EC2实例的AMI和一个新的EC2实例，默认的Nginx欢迎站点（即index.html，404.html等）被恢复并覆盖我现有的网站这些文件是一样的。 我可以通过在那个目录中做一个git status来看这个，看看他们已经被添加了。

这有点痛苦，因为我在EC2实例上运行一个SaaS产品，让客户看到Nginx的欢迎页面看起来有些不专业。

我的问题是：这可能是什么原因造成的？

这是我的nginx.conf ：

• Amazon EC2实例上没有Web API控制器
• 在Amazon EC2上使用nginx安装SSL证书
• 使用EIP（基本EC2）在AWS EC2中设置HAProxy / Keepalived vrrp
• 市场ami的可用实例types
• 多个networking接口，路由configuration。 IP规则失败（基于debian的实例）

 # For more information on configuration, see: # * Official English Documentation: http://nginx.org/en/docs/ # * Official Russian Documentation: http://nginx.org/ru/docs/ user nginx; worker_processes 1; error_log /var/log/nginx/error.log; #error_log /var/log/nginx/error.log notice; #error_log /var/log/nginx/error.log info; pid /var/run/nginx.pid; events { worker_connections 1024; } http { include /etc/nginx/mime.types; default_type application/octet-stream; log_format main '$remote_addr - $remote_user [$time_local] "$request" ' '$status $body_bytes_sent "$http_referer" ' '"$http_user_agent" "$http_x_forwarded_for"'; access_log /var/log/nginx/access.log main; sendfile on; #tcp_nopush on; #keepalive_timeout 0; keepalive_timeout 65; #gzip on; # Load modular configuration files from the /etc/nginx/conf.d directory. # See http://nginx.org/en/docs/ngx_core_module.html#include # for more information. include /etc/nginx/conf.d/*.conf; #server { # listen 80; # server_name *.xxx.com; # return 301 https://$host$request_uri; #} server { listen 80; listen 443 default ssl; server_name *.xxx.com; if ($http_x_forwarded_proto = "http") { return 301 https://$host$request_uri; } ssl_certificate /etc/pki/tls/certs/process.st.crt; ssl_certificate_key /etc/pki/tls/private/process.st.key; ssl_protocols SSLv3 TLSv1; ssl_ciphers ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:RC4+RSA:+HIGH:+MEDIUM; #charset koi8-r; #access_log /var/log/nginx/host.access.log main; location / { root /usr/share/nginx/html; index index.html index.htm; # Disable cache (for now). add_header Cache-Control no-cache; } # redirect server error pages to the static page /40x.html # error_page 404 /404.html; location = /40x.html { root /usr/share/nginx/html; } # redirect server error pages to the static page /50x.html # error_page 500 502 503 504 /50x.html; location = /50x.html { root /usr/share/nginx/html; } # proxy the PHP scripts to Apache listening on 127.0.0.1:80 # #location ~ \.php$ { # proxy_pass http://127.0.0.1; #} # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000 # #location ~ \.php$ { # root html; # fastcgi_pass 127.0.0.1:9000; # fastcgi_index index.php; # fastcgi_param SCRIPT_FILENAME /scripts$fastcgi_script_name; # include fastcgi_params; #} # deny access to .htaccess files, if Apache's document root # concurs with nginx's one # #location ~ /\.ht { # deny all; #} } # another virtual host using mix of IP-, name-, and port-based configuration # #server { # listen 8000; # listen somename:8080; # server_name somename alias another.alias; # location / { # root html; # index index.html index.htm; # } #} # HTTPS server # #server { # listen 443; # server_name localhost; # ssl on; # ssl_certificate cert.pem; # ssl_certificate_key cert.key; # ssl_session_timeout 5m; # ssl_protocols SSLv2 SSLv3 TLSv1; # ssl_ciphers HIGH:!aNULL:!MD5; # ssl_prefer_server_ciphers on; # location / { # root html; # index index.html index.htm; # } #} } 

我做了创build基本AMI图像的步骤。

1. AWS EC2控制台：使用Amazon Linux 64位启动实例。
2. SSH入实例： sudo yum install git ， sudo yum install nginx 。
3. 编辑/etc/nginx/nginx.conf到上面。
4. 复制所有必需的SSL证书。
5. 删除/usr/share/nginx/html默认页面。
6. 将Git repo克隆到/usr/share/nginx/html 。

现在我创build图像：

1. ec2-create-image $INSTANCE_ID --name base 。
2. AWS EC2控制台：使用“基本”AMI启动实例。
3. 当它启动的时候，它又连同我从git中拉出的页面一样有欢迎页面，但是Nginx页面覆盖了同名的文件。