On premise mapped to AWS

A question that often comes up when companies are migrating Oracle workloads to AWS is: "How do my on premise IT architecture components map to AWS?".  Here are some of the most common components mapping from on premise to AWS:

AWS RDS caching query results

The first place to look when attempting to speed query performance when running AWS RDS MySQL is the MySQL query cache size:
http://survivalguides.wordpress.com/2012/07/11/change-the-query-cache-size-amazon-aws-rds/

With support of MySQL 5.6 for AWS RDS, MySQL RDS now has support for memcached:
http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.MySQL.Options.html

AWS CloudFront : points of interest when running Oracle

When using a content delivery network such as AWS CloudFront, one of the first questions is making sure the latest content is at the edge location.  The time-to-live (TTL) is set using the cache-control directive : Cache-Control max-age directive lets you specify how long (in seconds) you want the object to remain in the cache before CloudFront gets the object again from the origin server.  The minimum expiration time CloudFront supports is 0 seconds and the maximum is in the year 2038.   The default, if not set, is 24 hours.   Setting to 0 does not mean the web page will always go to the origin for its content.  It means that CloudFront delegates the authority for cache control to the origin, i.e. the origin server decides whether or not, and if for how long CloudFront caches the objects.

Using CloudFront with Oracle applications such as EBusiness Suite, Peoplesoft, or Siebel would be an interesting exercise as these products have very dynamic web pages.  There is the potential of pointing CloudFront to an AWS ELB which is front of an Oracle Applications deployment.  Not sure how much this would improve performance of the application?