Standard Output is JSON, use aws configure to change the output to text

AWS Tools installed under Ubuntu

curl "https://bootstrap.pypa.io/get-pip.py" -o "get-pip.py"

sudo python get-pip.py

sudo pip install awscli

AWS CLI Client configure

aws configure

How to remove

sudo pip uninstall awscli

 

 

sudo rm -rf /usr/local/aws

sudo rm /usr/local/bin/aws

How to Resize a Disk from AWS CentoOS Image

Then create a new AMI. On boot, the cloud-init "growpart" module will grow the root partition to the total EBS size. Clearly, if that's not what you what, change or ignore that advice.

You can also fix this manually with a repartition and a reboot, but this will not automatically work as a new image.

# fdisk /dev/xvda <<END

u

d

n

p

1

2048

w

END

# reboot

# (after reboot)

# resize2fs /dev/xvda1

# df -h / # should now be entire EBS volume

Statt selbst zu schreiben, verlinke ich hier 🙂

https://rasm.io/blog/2013/statische-website-auf-amazon-s3-hosten/

Kurz Beschreibung

Das Bucket muss so heißen wie die Domain. Dem Bucket sagen, wer alles zugreifen soll.

Am Besten per Policy

{
“Version”: “2012-10-17”,
“Statement”: [
{
“Sid”: “AddPerm”,
“Effect”: “Allow”,
“Principal”: “*”,
“Action”: “s3:GetObject”,
“Resource”: “arn:aws:s3:::mein.bucket.com/*”
}
]
}

Der DNS Eintrag vom S3 Bucket kann bis zu 20 min gehen.

Danach in Route 53 ein A Record anlegen und Alias auswählen und nun müßte dort das S3 Bucket auftauchen mit dem selben Namen.
Wenn nein, mal den Record anlegen mit irgendwas und dann nochmal aufrufen.

Dann ist man auch schon fertig.

Import you must give permission to the bucket itself and /*

{
“Version”: “2012-10-17”,
“Statement”: [
{
“Sid”: “Stmt1333333300”,
“Effect”: “Allow”,
“Action”: [
“s3:DeleteObject”,
“s3:GetObject”,
“s3:PutObject”,
“s3:GetObjectAcl”,
“s3:PutObjectAcl”
],
“Resource”: [
“arn:aws:s3:::my.bucket.com/*”,
“arn:aws:s3:::my.bucket.com”
]
}
]
}

http://stackoverflow.com/questions/38774798/accessdenied-for-listobjects-for-s3-bucket-when-permissions-are-s3