Created
September 8, 2015 06:54
-
-
Save Gigabyte1979/8fc4d57f59212080228d to your computer and use it in GitHub Desktop.
Configure AWS SSL-certificates
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
:: Step 1 - Create CSR-file :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: | |
openssl req -nodes -newkey rsa:2048 -keyout any.domainname.com.key -out any.domainname.com.csr | |
:: Step 2 - Prepare Private Key for configuration :::::::::::::::::::::::::::::::::::::::::::::::: | |
openssl rsa -in any.domainname.com.key -text | |
:: Step 3 - Print CRT-file’s content to screen ::::::::::::::::::::::::::::::::::::::::::::::::::: | |
openssl x509 -inform PEM -in any.domainname.com.crt | |
:: Step 4 - AWS ELB Configuration :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: | |
:: - open EC2 Dashboard -> Network & Security -> LoadBalancer - Listeners | |
:: - add new listener HTTPS (443) to HTTP (80) | |
:: - select SSL-certificate “New” | |
:: Step 5 - Compose certificate info ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: | |
:: - define certificate name | |
:: - copy Private Key’s content (info from Step 2) into “Private Key field” | |
:: - copy Certificate’s content (info from Step 3) into “Public Key Certificate field” | |
:: - copy content from bundel certificate into “Certificate Chain” filed | |
:: - click button Save | |
:: That’s All | |
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment