S3 SSE without request header

You must include the provide a request header, x-amz-server-side-encryption.  S3 SSE

 encrypts each object with a unique key.  Unfortunately there is no way to enable SSE for a bucket where SSE happens automatically. There is no such bucket policy or bucket setting.  Some third party tools take care of automatically using SSE, such as S3 browser: http://s3browser.com/amazon-s3-server-side-encryption.php. You can enable encryption for already uploaded files, and it can also be configured to automatically apply encryption during uploading.

Creating prefixed zone in Route 53 for hosting web site in S3

In this example, we will create a hosted zone to host our S3 web site.   

In this case the S3 bucket is in one account and Route 53 provider to outside world is in another account.  This example is showing DNS chaining as well as how to configure the DNS service to host your S3 bucket web site on AWS.

1    1. Create a hosted zone (in this example: oracle.migrating2cloud.com) on the account that is hosting the S3 bucket and is not your Route 53 DNS service that is accessible to the outside world.

-Create a hosted zone

-Go to records sets and get the Delegation set to be used for your current DNS provider which is the Route 53 service in your other account.     Click on check box next to oracle.migrating2cloud.com and click Go to record sets button:

 - Get the DNS records by clicking the check box next to the oracle.migrating2cloud.com with record set type of NS. These DNS entries will be used in Route 53 in the other account.

2    2. Add record set for migrating2cloud.com domain name in Route 53 on my second (aka: public DNS Route 53 account) account called Oracle.migrating2cloud using the DNS records created when you created the hosted zone in the first account.

-       Go to Route 53 hosted zones 

-       Click check box next to migrating2cloud.com hosted zone and select go to record sets

-       Click create a record set button.

      -       Enter oracle in the name. 

      -       Type is NS – Name Server

      -       Enter the DNS records created in your other account:

3. You now need to create a web site (in S3) and create a Route 53 record set (for example: database.oracle.migrating2cloud.com) to point the S3 bucket with same name (database.oracle.migrating2cloud.com) with an HTML file. Follow instructions in other posting. http://cloudconclave.blogspot.com/2013/05/hosting-prefixed-domain-name-web-site.html

      4.  After completing this task, you should see your web page. http://database.oracle.migrating2cloud.com. 

Hosting prefixed domain name web site on S3 using Route 53

This the process for hosting a domain with a prefix.  For example, you have the domain name migrating2cloud.com already hosted.  Assuming you also have core prefix (aws.migrating2cloud.com) already built.  You now want to create specific prefixes (for example boston.aws.migrating2cloud.com) to hold localized information.

1. Create in S3 bucket in the account where the web site on S3 will be hosted. The bucket name needs to the same name as the web site. In this example: boston.aws.migrating2cloud.com
2. Check radial button next to "Enable website hosting" to make this a S3 bucket that holds a web site. Type in a name for the base html page. In this case, index.html
3. Upload the index.html file into the bucket. Example HTML file is below:
4. Try accessing the web site boston.aws.migrating2cloud.com. It will not work. There is nothing pointing the ‘internet’ (no DNS Name mapping in our DNS provider which in this case is AWS Route 53) to your web site on S3.
5. Create a record set in your Route 53 Hosted zone for aws.migrating2cloud.com for your S3 web site bucket.
A. Go into the Route 53 service
B.Go into the record sets by checking the box next to the hosted zone (aws.migrating2cloud.com) and clicking on “Go to Record Sets”
C. Click “Create Record Set”
The record set has the following values:
- Name: boston
- Type: A- IPv4 address
- Alias with target name: Click and drop down box will show you boston.aws.migrating2cloud.com S3 endpoint
6. Does it work … no … set permissions on the index.html
7. Set permissions on the index.html as well. For open/download by everyone.


More on how point your zone apex and zone www records to Route 53 from your domain name is parked (AWS is not a domain registry)

http://cloudconclave.blogspot.com/2012/10/aws-route-53-domain-name-configuration.html
http://cloudconclave.blogspot.com/2012/07/aws-ec2-amazon-cloud-domain-name-and-ip_11.html

<head> <title>Boston AWS Training</title> </head> <h1> Boston AWS Training </h1> <body> <a href="http://migrating2cloud.com">Main Site</a> </body> <br> <br> <a href="http://cloudconclave.blogspot.com">Cloud Blog</a> <a href="http://www.amazon.com/-/e/B005350FIO">Amazon Author Central</a> </html>