Exanding size of your current EBS root volume

In some cases you may need to increase the size your EC2 instance root volume. Here are the steps to do this:

1. Create a volume from an existing EBS snapshot :
aws ec2 create-volume --snapshot-id snap-YourVolumesSnapshot --size 10 -- availability-zone az-asdf-1a 

2. Stop the instance:
was ec2 stop-instances --instance-id i-YourInstanceId

3. Detach the current volume:
was ec2 detach-volume --volume-id vol-TheSmallDefaultVolume

4. Attach the new volume:
was ec2 attach-volume --volume-id vol-TheLargerVolume --instance-id i- YourInstanceId --device /dev/sda1

5. Log into your bastion host:
ssh -i YourFile.pem ec2-user@10.__.__.__

7. Start the instance:
aws ec2 start-instances --instance-id i-YourInstanceId

8. Check the file system size: (It will still be the smaller size)
df –h

9. Resize the file system to the size of the volume
sudo resize2fs /dev/sda1

10. Check the file system size again:
df –h

Oracle Database size and network throughput : IOPS and network throughput

When configuring an Oracle Database on AWS EC2, you need to consider both storage (EBS) IOPS and network throughput.   With PIOPS, you can achieve up to 4K IOPS per EBS volumes.  However, the EC2 instances (assuming EBS optimized or 10 Gbps cluster compute) can be a potential bottle neck.  For example, the m2.2xlarge instance type has a maximum throughput of 0.5Gb.  Which means this instance type is limited to approximately 3750 * 16 KiB IOPS. Therefore, one 4K PIOPS volume would start to saturate the network.   Take into account the IOPS and instance network throughput when designing your Oracle Database on AWS EC2.

Redshift block size

Typical database block sizes range from 2 KB to 32 KB. Amazon Redshift uses a block size of 1 MB, which is more efficient and further reduces the number of I/O requests needed to perform any database loading or other operations that are part of query execution.