• Home

Aws Cli Client For Mac Os


AWS CLI v1.15.32 or higher; Kubectl; aws-iam-authenticator; The instructions below are to install the tools on a Mac OS client. AWS CLI – The easiest way to install the AWS CLI on a mac is to use homebrew. If you’ve already got homebrew installed on your Mac, then skip over this. Otherwise run the following from a terminal in order to. It’s also easy to interact with Amazon S3 buckets through the web console and AWS CLI (Command Line Interface). To make your workflow smoother, you can additionally employ tools like ForkLift, an Amazon S3 client for macOS.

When I’m writing this tutorial I’m using macOS Sierra but everything should work correctly also on previous versions of macOS like El Capitan, Yosemite, Mavericks and so on.

This tutorial describes how to use the console to manage your cloud. I think it’s clearer and easier way than their website interface.

Let’s start. I assume that you’ve heard something about Amazon’s cloud. If not let me introduce you in the first chapter, everyone else can go directly to next chapters.

What is Amazon’s Cloud?

We call it AWS, it’s shortcut from Amazon Web Services. At the beginning of Amazon there was just an online shop like thousand others. However, they grew up to spectacular size acting in many countries in the world. Working in this scale (from our – IT side of course) requires a lot of servers working together. Amazon engineers had to develop something that allows them to manage their server farms which are located around the world. Everything that they involved had to be easy, cheap and scalable. They did it and we are looking at it when we are using AWS.


  1. An account on Amazon.
  2. A user with access key ID and secret access key(instruction bellow).
  3. Installed brew.

Create access key ID and secret access key

I hope that you don’t need details how to create an account on Amazon website, so let’s go directly to creating a user with programmatic access.

  1. Login to your account on aws.amazon.com.
  2. On dashboard choose “IAM” in section “Security, Identity & Compliance”.
  3. Look at the left sidebar, there you have option “Users”, follow it.
  4. Click blue button “Add user”.
  5. Fill in the form, remember to mark options Programmatic access.
  6. Now you have to assign the user to some group or attach to it some polices. Other words, you are defining what user can do on Amazon Cloud. At this moment you can just add created user to the group ec2_admin which allows you to do most everything.
  7. Go to next step (review) and again click blue button, this time called “Create user”.
  8. You should see a table with created user, there are columns Access key ID and Secret access key.
  9. Copy your keys or download CSV file which contains that data.

Install pip

Amazon provides two powerful tools which you can use to manage your cloud directly from command line. A both of them are written in python and pip is nothing more than packet manager for python which allows us to install these tools.

Probably you should have installed it, you can check it using a command line, just type:

If get something like bellow then you can go to next step, if not, stay a little bit longer in this chapter.

Ok, you don’t see anything that could look like message above. We know that you haven’t pip, so let’s install it! Don’t close the command line and type that line:

brew with python will try to install pip as a default packets manager after it, try again run the command:

Install aws

Everything that you have to do is to type that four words in your terminal. It will install this tool to use only by your user on your mac, so you don’t need to grant root permissions using sudo.

If everything has gone ok then you could have run that command to see the version which you installed.

Install eb

The command to install tool to manage Elastic Beanstalk is also really easy:

And again, let’s check the version.

Create the first project on Amazon behind load balancer

First, what you need to do is to create an empty folder and go there, you can do that:

After that, you have to type only one command

You can see some easy form, which asks you a few question to prepare everything.

Select a default region

Amazon has datacenter around the world, so choose the prime where you want to work. Definitely, servers at the US are cheaper than others, so for the test, you can choose Oregon.

Access key

Because you run first time that command you have to fill in next questions using yours Access key ID and Secret access key which you created few steps earlier.

As a first step you have to provide your Access key ID and after that Secret access key.

Application name

You are creating your first project on Elastic Beanstalk you have to figure out some names, it could be hello world.

Oh no, “Elastic Beanstalk could not find any platforms”

You’ve just typed the name of your new application, and see you it as an error like in header? Don’t worry, you have to come back to Amazon website, to section “IAM”, then to “Users” find your new created user and click blue button “Add permissions”. There click on “Attach existing policies directly” and in search form paste it: AWSElasticBeanstalkFullAccess. You should find out one result, check it and click blue button “Next: Review” and then another blue button “Add permissions”.

What exactly did you do? You give your user privileges to manage service Elastic Beanstalk. So, go on!

Type again that commend:

Choose region like previously and type a name your new application.

Select a platform.

Aws Cli Client For Mac Osx

Amazon has predefined few systems, some specialized and two general (docker, Multi-container Docker). We can start with docker, so type a number which is on the left of the docker name.

Select a platform version.

Don’t ask, just choose the first option. On the first place there is always the newest version of the platform, you don’t need an older version, right?

Do you want to set up SSH for your instances?

Yes! Unless you don’t want to have access to your new instance from your command line, then ignore, but I don’t recommend it.

Select a keypair.

Security is so important on Amazon, so you need to create some keys which will be used to get connected to your instance. Chose options [ Create new KeyPair ].

Type a keypair name.


Click enter, at this moment, the default name will be enough.

Enter passphrase

If stronger password then it will be harder to crack it, so don’t save your keyboard.

Enter same passphrase again:

Repeat your password, please.

Enter passphrase:

And again repeat your password.

You are ready

It’s everything. Your Amazon account has been set up the same as your first application on Elastic Beanstalk. In some next post, I will describe how you can use it. Stay tuned!

Avaiable datacenters (regions)

[ aws . kms ]

Aws cli install mac os


Decrypts ciphertext that was encrypted by a AWS KMS customer master key (CMK) using any of the following operations:

  • Encrypt

  • GenerateDataKey

  • GenerateDataKeyPair

  • GenerateDataKeyWithoutPlaintext

  • GenerateDataKeyPairWithoutPlaintext

You can use this operation to decrypt ciphertext that was encrypted under a symmetric or asymmetric CMK. When the CMK is asymmetric, you must specify the CMK and the encryption algorithm that was used to encrypt the ciphertext. For information about symmetric and asymmetric CMKs, see Using Symmetric and Asymmetric CMKs in the AWS Key Management Service Developer Guide .

The Decrypt operation also decrypts ciphertext that was encrypted outside of AWS KMS by the public key in an AWS KMS asymmetric CMK. However, it cannot decrypt ciphertext produced by other libraries, such as the AWS Encryption SDK or Amazon S3 client-side encryption . These libraries return a ciphertext format that is incompatible with AWS KMS.

If the ciphertext was encrypted under a symmetric CMK, the KeyId parameter is optional. AWS KMS can get this information from metadata that it adds to the symmetric ciphertext blob. This feature adds durability to your implementation by ensuring that authorized users can decrypt ciphertext decades after it was encrypted, even if they’ve lost track of the CMK ID. However, specifying the CMK is always recommended as a best practice. When you use the KeyId parameter to specify a CMK, AWS KMS only uses the CMK you specify. If the ciphertext was encrypted under a different CMK, the Decrypt operation fails. This practice ensures that you use the CMK that you intend.

Whenever possible, use key policies to give users permission to call the Decrypt operation on a particular CMK, instead of using IAM policies. Otherwise, you might create an IAM user policy that gives the user Decrypt permission on all CMKs. This user could decrypt ciphertext that was encrypted by CMKs in other accounts if the key policy for the cross-account CMK permits it. If you must use an IAM policy for Decrypt permissions, limit the user to particular CMKs or particular trusted accounts. For details, see Best practices for IAM policies in the AWS Key Management Service Developer Guide .

The CMK that you use for this operation must be in a compatible key state. For details, see How Key State Affects Use of a Customer Master Key in the AWS Key Management Service Developer Guide .

Cross-account use : Yes. You can decrypt a ciphertext using a CMK in a different AWS account.

Required permissions : kms:Decrypt (key policy)

Related operations:

  • Encrypt

  • GenerateDataKey

  • GenerateDataKeyPair

  • ReEncrypt

See also: AWS API Documentation

See ‘aws help’ for descriptions of global parameters.



--ciphertext-blob (blob)

Ciphertext to be decrypted. The blob includes metadata.

Aws Cli Client For Mac Os 10.13

--encryption-context (map)

Specifies the encryption context to use when decrypting the data. An encryption context is valid only for cryptographic operations with a symmetric CMK. The standard asymmetric encryption algorithms that AWS KMS uses do not support an encryption context.

An encryption context is a collection of non-secret key-value pairs that represents additional authenticated data. When you use an encryption context to encrypt data, you must specify the same (an exact case-sensitive match) encryption context to decrypt the data. An encryption context is optional when encrypting with a symmetric CMK, but it is highly recommended.

For more information, see Encryption Context in the AWS Key Management Service Developer Guide .

key -> (string)

value -> (string)

Shorthand Syntax:

JSON Syntax:

--grant-tokens (list)

A list of grant tokens.

Write high-performance code faster with Unity 2020.2. New improved tools for programmers help you to iterate faster and optimize your projects for higher performance. Highlights include improved compilation times, C#8. Unity is the ultimate real-time 2D, 3D, AR, & VR development engine. Download Unity to start creating today and get access to the Unity platform and ecosystem. Unity is the ultimate game development platform. Use Unity to build high-quality 3D and 2D games, deploy them across mobile, desktop, VR/AR, consoles or the Web, and connect with loyal. Unity 2018 3.

For more information, see Grant Tokens in the AWS Key Management Service Developer Guide .



--key-id (string)

Specifies the customer master key (CMK) that AWS KMS uses to decrypt the ciphertext. Enter a key ID of the CMK that was used to encrypt the ciphertext.

This parameter is required only when the ciphertext was encrypted under an asymmetric CMK. If you used a symmetric CMK, AWS KMS can get the CMK from metadata that it adds to the symmetric ciphertext blob. However, it is always recommended as a best practice. This practice ensures that you use the CMK that you intend.

To specify a CMK, use its key ID, Amazon Resource Name (ARN), alias name, or alias ARN. When using an alias name, prefix it with 'alias/' . To specify a CMK in a different AWS account, you must use the key ARN or alias ARN.

For example:

  • Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab

  • Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab

  • Alias name: alias/ExampleAlias

  • Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias

To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey . To get the alias name and alias ARN, use ListAliases .

--encryption-algorithm (string)

Specifies the encryption algorithm that will be used to decrypt the ciphertext. Specify the same algorithm that was used to encrypt the data. If you specify a different algorithm, the Decrypt operation fails.

This parameter is required only when the ciphertext was encrypted under an asymmetric CMK. The default value, SYMMETRIC_DEFAULT , represents the only supported algorithm that is valid for symmetric CMKs.

Possible values:




--cli-input-json--cli-input-yaml (string)Reads arguments from the JSON string provided. The JSON string follows the format provided by --generate-cli-skeleton. If other arguments are provided on the command line, those values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally. This may not be specified along with --cli-input-yaml.

--generate-cli-skeleton (string)Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value input, prints a sample input JSON that can be used as an argument for --cli-input-json. Similarly, if provided yaml-input it will print a sample input YAML that can be used with --cli-input-yaml. If provided with the value output, it validates the command inputs and returns a sample output JSON for that command.

See ‘aws help’ for descriptions of global parameters.


Example 1: To decrypt an encrypted file

The following decrypt command demonstrates the recommended way to decrypt data with the AWS CLI.

The command does several things:

  1. Uses the fileb:// prefix to specify the --ciphertext-blob parameter.

    The fileb:// prefix instructs the CLI to read the encrypted data, called the ciphertext, from a file and pass the file’s contents to the command’s --ciphertext-blob parameter. If the file is not in the current directory, type the full path to file. For example: fileb:///var/tmp/ExampleEncryptedFile or fileb://C:TempExampleEncryptedFile.

    For more information about reading AWS CLI parameter values from a file, see Loading Parameters from a File in the AWS Command Line Interface User Guide and Best Practices for Local File Parameters on the AWS Command Line Tool Blog.

    The command assumes the ciphertext in ExampleEncryptedFile is binary data. The encrypt examples demonstrate how to save a ciphertext this way.

  2. Uses the --output and --query parameters to control the command’s output.

    These parameters extract the decrypted data, called the plaintext, from the command’s output. For more information about controlling output, see Controlling Command Output in the AWS Command Line Interface User Guide.

  3. Uses the base64 utility.

    This utility decodes the extracted plaintext to binary data. The plaintext that is returned by a successful decrypt command is base64-encoded text. You must decode this text to obtain the original plaintext.

  4. Saves the binary plaintext to a file.

    The final part of the command (>ExamplePlaintextFile) saves the binary plaintext data to a file.

Example 2: Using the AWS CLI to decrypt data from the Windows command prompt

The preceding example assumes the base64 utility is available, which is commonly the case on Linux and Mac OS X. For the Windows command prompt, use certutil instead of base64. This requires two commands, as shown in the following examples.


KeyId -> (string)

The Amazon Resource Name (key ARN ) of the CMK that was used to decrypt the ciphertext.

Plaintext -> (blob)

Decrypted plaintext data. When you use the HTTP API or the AWS CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.

EncryptionAlgorithm -> (string)

The encryption algorithm that was used to decrypt the ciphertext.