Skip to main content

AWS CLI: Uploading Files From The Command Window To My S3 Bucket

When I wanted to upload my media/audio/data files to my S3 Bucket, I was logging on to AWS through my web browser.

Yesterday, however, I learned a more efficient way to upload files to my S3 Bucket by using the AWS COMMAND LINE INTERFACE (AWS CLI).  I installed and configured this onto my computer so that I would be able to upload files directly from my command window.

I created a user account with administrative permission using the AWS IAM service.  I noticed a familiar thing happen.  I received two sets of keys!  That's right... a public key and a SECRET key. 😊This secret key works pretty much the same way the public and private keys work when using SSH.  Just like the SSH keys, I filed the new keys from AWS IAM in a safe place on my computer.

Then I installed and configured AWS CLI onto my computer.   Once it was installed, I gave it a test run... everything worked BUT---- all of the files I was putting into my S3 Bucket were not going in as public.  So, I applied a bucket policy with this code:



{
  "Id": "DefaultPublic",
  "Statement": [
    {
      "Sid": "GetDefaultPublic",
      "Action": [
        "s3:GetObject"
      ],
      "Effect": "Allow",
      "Resource": "arn:aws:s3:::PUT THE NAME OF YOUR BUCKET HERE/*",
      "Principal": {
        "AWS": [
          "*"
        ]
      }
    }
  ]
}


Once that was done...WHOLA!  I was able to upload media, sound, and data files to my S3 Bucket from the command line and it ALL be visible to the public.  I now have complete control to do everything that I need to do on the command line. 👊💪😆

Follow me as I learn to build my website bit by bit!    IronTreeDev.com

Photo by Andras Vas on Unsplash




Comments

  1. CajunesqueFebruary 12, 2019 at 7:26 AM

    Yep, You a "power-user" now. Command line FTW! But since command line requires cumbersome typing, we will configuring your terminal window via .bash_profile to make the commands easier to execute and give you more power.

    ReplyDelete

Post a Comment

Popular posts from this blog

XPATH and XPATH Expressions In XMLLINT

XPATH And XPATH Expressions Earlier, I told you about xmllint and xmllint for html files .  Let's say you just want to parse the <span> tags within your html file or just your <span lang="el"> tags? Enter:  Xpath. Xpath is yet another option available within the xmllint language. Remember, an Xpath is used to navigate through elements and attributes in xml and html documents.  Xpath uses Xpath Expressions to select nodes or node sets within a document. Example 1 .  Looking for all of the <span> tags within an html document. xmllint -- html -- xpath " // span" StedmanLesson10.html xmllint = This tells the command line that we are going to be using the xmllint language. space = because we always have space in between commands -- = Remember, these are the two hyphen-minus characters that we need to tell the command line that we are going to use an xmllint option. html = This is the xmllint option we want to ...
Post a Comment
Read more

XMLLINT for HTML: Cleaning up the HTML Code

Getting That MESS Cleaned Up! In an earlier post, we learned about xmllint .  Today, I want to talk about cleaning up the code for an HTML file. When we have an xml file, xmllint is used.  For an html file, we use the following command in the command line: xmllint --html <filename goes here>         Here is an actual command on my command line for running xmllint for my StedmanLesson10.html file. In the photo above, you see that I start off the command with xmllint. The next thing is a space and then a --html.  The two -- are two hyphen-minus characters that are used to specify long options (Basically there are options that can be used within xmllint.  The two hyphen-minus characters are saying an option is going to be used.  In this case, that option will be html - because we are going to do an xmllint on an html file). After that you see a space and then the name of the html file I want t...
Post a Comment
Read more

DevOps Skills Part 2: Talking Like a Toddler

http colon whack whack dub-dub-dub dot google dot com What in the world did I just say?   I sound like a toddler talking in words and sounds that make no sense at all! 🙊The funny thing is, if you talk to a person involved with DevOps, they will know and understand exactly what you said! 😲 whack = "/"  That forward slash symbol on a Mac key board that is usually placed under the ? ...... that is referred to as a "whack".  Think of a duck quacking who forgot to sound the "q". 🙈 That forward slash (/) "whack" is the path separator that will eventually lead to the file on your web server.  Let's say the url is www.cloviscorp.com/collegium/grammar/index.html , then the browser will first find the webserver (in this case:  www.cloviscorp.com).  It then starts in that server's filesystem at the docroot (/var/html/www) and then continuing through to /collegium/grammar , where the file index.html resides (at the webserver's f...
Post a Comment
Read more