
This will be applicable for services with the rate that looks like this:

$X per `provisioned IOPS-month`

For example, it could be `RDS` (Relational Database SErvice), or `EBS` (Elastic Block Store).

![rate](rate.png)

The rate shown above is the rate for RDS of instance type `Provisioned IOPS SSD (io1) Volumes`.

If you have created the instance (or could be created by another service), but not sure what that means to your bill.
Chances are you might not need it, or otherwise, be prepared for a higher bill amount.

How the bill are calculated for provisioned IOPS-month type of instance:

$0.11 * 1000 IOPS * number of hours

= $110 for 1 month

= $3.67 for 1 day

That's for 1000 IOPS for an instance.

---

Also, please take note that:
1. Provisioned IOPS SSD (io1) volumes are **not included** in the AWS Free Tier
2. They are not charged by usage of I/O, but the **amount of IOPS enabled/provisioned**.

So if you enable an instance of 8000 IOPS of io1, but only used a bit of it, you will still be charged for

$0.11 * 8000 * number of hours


<br />
Plus, there will be a charge for the storage rate. Refer to the image attached above.

`$0.138 per GB-month`

<br />

So, if you are not sure, probably a General Purpose SSD (gp2) volume is your right choice.

Refer to the [EBS pricing](https://aws.amazon.com/ebs/pricing/) for another example. (the IOPS-month rate is applicable for RDS as well)




Billing for AWS Provisioned IOPS (io1)


There are time when you have multiple AWS access keys and secrets.

Each key are able to access the AWS resources/services, depending on the given permissions.

Ideally those keys only have access to the resources that are needed, nothing more.

However, it might still happen that you are accessing the same services, but for different accounts.

Let say pushing files to S3 bucket, but instead of pushing to your work/company AWS account, you want to push it to your personal one.

So you want to make sure you are passing in the right configurations for the command.

#### AWS Profile

What you are looking for is AWS *profile* management. (I made that up, but you get the idea.)

You can have a quick look at your current profiles using this command.

```
$ cat ~/.aws/config
```

Well, to save you some typings, here's mine.

```
[default]
region = ap-southeast-1
output = text

[profile docker-repository]
region = us-west-2

[profile eb-cli]
aws_access_key_id =
aws_secret_access_key =


[profile chinloong]
aws_access_key_id =
aws_secret_access_key =
region = ap-southeast-1
```

You guessed it right. **default** configurations will be used if no profile is spcified explicitly.

New profile can be created by following the pattern you can derived from the file.

`[profile staging]`


and passed it as an argument in the command as

`--profile staging`

For example:

I am trying to deploy files to S3 bucket to use it in static web hosting.

```
s3-deploy './public/**' --cwd './public/' --profile chinloong --bucket your-bucket-name --deleteRemoved --gzip
```

Bad news is, it won't work.

You will probably get:

```
(node:82129) UnhandledPromiseRejectionWarning: Upload error: CredentialsError: Missing credentials in config (CredentialsError: Missing credentials in config
```

#### The missing part

```
$ cat ~/.aws/credentials
```

Make sure these two configs are there.

```
aws_access_key_id =
aws_secret_access_key =
```

Did I mentioned about the profile name?

Before I forgot, you can specify the profile name those configs are for.
But watchout for the missing **profile** word.


The full block looks like this. (Instead of `[profile staging]`)

```
[staging]
aws_access_key_id =
aws_secret_access_key =
```

You are now good to go!


#### Explanation

So we have

```
~/.aws/config
```

and

```
~/.aws/credentials
```

In short, use

`~/.aws/credentials` for sensitive config like your access key and secret.


`~/.aws/config` for less sensitive config like `region=us-west-2` or `max_concurrent_requests=10`


Hope that clears up things a bit for you! 😀

You can also set the profile as environment variable.

```AWS_PROFILE=staging s3-deploy ...```


Full explanation?

Read it here. [https://docs.aws.amazon.com/cli/latest/userguide/cli-config-files.html](https://docs.aws.amazon.com/cli/latest/userguide/cli-config-files.html)

and here [https://docs.aws.amazon.com/cli/latest/topic/config-vars.html](https://docs.aws.amazon.com/cli/latest/topic/config-vars.html)


Billing for AWS Provisioned IOPS (io1)

2 May 2018

aws/config vs aws/credentials

9 May 2018