Security. We all feel a bit of comfort when we know our private information is secure.
What I recently learned:
SSH = Secure Shell. When I want to access my EC2 Instance, I need to "SSH" into it. What exactly does that mean? I have a private EC2 Key that is located on a file on my computer. My EC2 Instance has a public key that is located on the home directory of my EC2 Instance. SSH authenticates my computer to my EC2 Instance to make sure that I am authorized to communicate ( send, transfer, receive, and change files) with my EC2 Instance (my private server on AWS). Once SSH authenticates my private key to my public key, SSH provides a private secure encrypted environment for my computer to communicate with my EC2 Instance.
"But HOW do you SSH into your EC2 Instance," you might ask? I can't physically drive to my EC2 Instance, so I will need to access it using the same command window as I use to look at my own MacBook Pro Computer. For me, that program is called Terminal. It is located in the Applications Folder. Once in my command window (Terminal), I will need to type the command: SSH and then the location of my private key, then the whither. This is where the private key needs to goto to meet up with my public key. This contains the user name of the private key as well as the location (ip address or domain name) of my EC2 Instance. Here's an example of what that looks like (of course I will use FAKE file names 😊):
ssh -i ~/Documents/Harry/MetSally/PrivateKey.pem PrivateKey-user@wouldntyouliketoknow.com
That is an example of the command I would need to type in order to SSH into my private EC2 Instance.
Once inside, I can communicate with and make whatever changes I want to my EC2 Instance.
SCP = First successful upload with scp to my webserver. http://irontreedev.com/ArtesLatinae15.xml
Stay tuned for my next blog on what SCP is!
What I recently learned:
SSH = Secure Shell. When I want to access my EC2 Instance, I need to "SSH" into it. What exactly does that mean? I have a private EC2 Key that is located on a file on my computer. My EC2 Instance has a public key that is located on the home directory of my EC2 Instance. SSH authenticates my computer to my EC2 Instance to make sure that I am authorized to communicate ( send, transfer, receive, and change files) with my EC2 Instance (my private server on AWS). Once SSH authenticates my private key to my public key, SSH provides a private secure encrypted environment for my computer to communicate with my EC2 Instance.
"But HOW do you SSH into your EC2 Instance," you might ask? I can't physically drive to my EC2 Instance, so I will need to access it using the same command window as I use to look at my own MacBook Pro Computer. For me, that program is called Terminal. It is located in the Applications Folder. Once in my command window (Terminal), I will need to type the command: SSH and then the location of my private key, then the whither. This is where the private key needs to goto to meet up with my public key. This contains the user name of the private key as well as the location (ip address or domain name) of my EC2 Instance. Here's an example of what that looks like (of course I will use FAKE file names 😊):
ssh -i ~/Documents/Harry/MetSally/PrivateKey.pem PrivateKey-user@wouldntyouliketoknow.com
That is an example of the command I would need to type in order to SSH into my private EC2 Instance.
Once inside, I can communicate with and make whatever changes I want to my EC2 Instance.
SCP = First successful upload with scp to my webserver. http://irontreedev.com/ArtesLatinae15.xml
Stay tuned for my next blog on what SCP is!
Follow me as I learn to build my website bit by bit! IronTreeDev.com
Sorry, meant to put my comment to THIS post, Lisa. I have already seen that you have fixed your xml document and that it renders beautifully with no errors. Good job, again! Please keep the updates coming. And also post those images that you are referencing in your xml document!
ReplyDelete