Elasticbeanstalk configurando HTTPS en una sola instancia de Python: no se permiten valores nulos en las plantillas

He implementado una aplicación Flask en un entorno EB (instancia única) y está funcionando bien, y ahora estoy tratando de configurarlo para https con un certificado autofirmado para probarlo.

Así que agregué un archivo de configuración como se muestra en la Guía del desarrollador de EB a .ebextensions (donde tenía 2 archivos anteriores para configurar la ruta del directorio satic e instalar postgresql94-devel), así que ahora tengo:

/.ebextensions a_packages.config b_path.config singlehttps.config /.elasticbeanstalk config.yml 

donde config.yml es:

 branch-defaults: default: environment: myApp-env global: application_name: myApp default_ec2_keyname: aws-eb default_platform: 64bit Amazon Linux 2015.09 v2.0.6 running Python 2.7 default_region: eu-central-1 profile: eb-cli sc: null 

a_packages.config es:

 packages: yum: postgresql94-devel: [] 

b_path.config es:

 option_settings: "aws:elasticbeanstalk:container:python:staticfiles": "/static/": "flaskApp/static/" 

y singlehttps.config es:

 Resources: sslSecurityGroupIngress: Type: AWS::EC2::SecurityGroupIngress Properties: GroupId: {"Fn::GetAtt" : ["AWSEBSecurityGroup", "GroupId"]} IpProtocol: tcp ToPort: 443 FromPort: 443 CidrIp: 0.0.0.0/0 packages: yum: mod24_ssl : [] files: /etc/httpd/conf.d/ssl.conf: mode: "000644" owner: root group: root content: | LoadModule wsgi_module modules/mod_wsgi.so WSGIPythonHome /opt/python/run/baselinenv WSGISocketPrefix run/wsgi WSGIRestrictEmbedded On Listen 443  ServerName myserver Redirect permanent / https://myserver   ServerName myserver SSLEngine on SSLCertificateFile "/etc/pki/tls/certs/server.crt" SSLCertificateKeyFile "/etc/pki/tls/certs/server.key" Alias /static/ /opt/python/current/app/static/  Order allow,deny Allow from all  WSGIScriptAlias / /opt/python/current/app/application.py  Require all granted  WSGIDaemonProcess wsgi-ssl processes=1 threads=15 display-name=%{GROUP} \ python-path=/opt/python/current/app:/opt/python/run/venv/lib/python2.7/site-packages:/opt/python/run/venv/lib64/python2.7/site-packages \ home=/opt/python/current/app user=wsgi \ group=wsgi \ WSGIProcessGroup wsgi-ssl  /etc/pki/tls/certs/server.crt: mode: "000400" owner: root group: root content: | -----BEGIN CERTIFICATE----- MIID .... fUJbS8/O+ -----END CERTIFICATE----- /etc/pki/tls/certs/server.key: mode: "000400" owner: root group: root content: | -----BEGIN RSA PRIVATE KEY----- MIIEz ....... JTAwSYIw== -----END RSA PRIVATE KEY----- container_commands: 01killhttpd: command: "killall httpd" 02waitforhttpddeath: command: "sleep 3" 

Así que cada vez que trato de crear un nuevo entorno EB con singlehttps.config colocado en .ebextensions no puedo desplegar y la salida es:

 Enter Environment Name (default is myApp-dev): myApp-env Enter DNS CNAME prefix (default is myApp-env): myApp Creating application version archive "app-160115_183325". Uploading myApp/app-160115_183325.zip to S3. This may take a while. Upload Complete. Environment details for: myApp-env Application name: myApp Region: eu-central-1 Deployed Version: app-160115_183325 Environment ID: *********** Platform: 64bit Amazon Linux 2015.09 v2.0.6 running Python 2.7 Tier: WebServer-Standard CNAME: myApp.elasticbeanstalk.com Updated: 2016-01-15 17:34:22.209000+00:00 Printing Status: INFO: createEnvironment is starting. INFO: Using elasticbeanstalk-eu-central-1-************* as Amazon S3 storage bucket for environment data. ERROR: Service:AmazonCloudFormation, Message:'null' values are not allowed in templates ERROR: Failed to launch environment. 

Estoy bastante seguro de que el problema está en un solo https.config, ya que sin él no está sucediendo. No puedo leer nada útil en los registros. Traté de echar un vistazo a CloudFourmation pero no estoy llegando a ningún lado.

Debería sangrar todo el contenido debajo de la línea /etc/httpd/conf.d/ssl.conf :

 files: /etc/httpd/conf.d/ssl.conf: mode: "000644" owner: root group: root content: | multiline file content goes here