AWS SF Summit 2015 migration sessions

Here are the AWS SF 2015 Summit decks and video replays:
1. AWS Cloud Transformation Framework:
http://www.slideshare.net/AmazonWebServices/application-portfolio-migration
https://www.youtube.com/watch?v=_FjCMWlskMU&index=11&list=PLhr1KZpdzukeD0iBeDI9WqZLYtuaFaaGc
The CAF white paper serves as the foundation for this session: http://d0.awsstatic.com/whitepapers/aws_cloud_adoption_framework.pdf 

2. AWS application modernization with a focus on security:
http://www.slideshare.net/AmazonWebServices/cloud-migration-application-modernization-and-security-for-partners
https://www.youtube.com/watch?v=UpeV4OqB6Us&index=26&list=PLhr1KZpdzukeD0iBeDI9WqZLYtuaFaaGc

3. AWS Partner session:
http://www.slideshare.net/AmazonWebServices/implementing-service-oriented-architecture

All sessions can be found on Slideshare and Youtube here:
http://www.slideshare.net/AmazonWebServices/tag/2015sfsummit?adbsc=awssummit2015_20150411_43646046&adbid=586959582653648896&adbpl=tw&adbpr=66780587
https://www.youtube.com/playlist?list=PLhr1KZpdzukeD0iBeDI9WqZLYtuaFaaGc&adbsc=awssummit2015_20150411_43648896&adbid=586713471154159616&adbpl=tw&adbpr=66780587

Migrating to AWS : Amazon.com

Nice session on how Amazon.com has migrated several different types of workloads to AWS:

1. Rehost - Amazon.com web site : Details on an existing workload migrated to AWS.  'Classic' web site migration of web application to AWS.

2. Rearchitecture  - Database migration : Migrating application data to AWS from a traditional data store to AWS is way to reduce costs.  This use cases uses an Information Lifecycle approach to moving data off of a live production databases to S3. 

3. Replace - Application replacement : Deprecation of an order system, and implementing the new order system on AWS.

4. Green field : Using AWS for development of a new video service used internally at Amazon.

The video goes into details on how AWS can reduce costs, improve development productivity, enable elastic infrastructure, increase scalability, and improve high availability. 

https://www.youtube.com/watch?v=f45Uo5rw6YY

Accenture AWS re:Invent Enterprise Migrations Session

Accenture migrations at scale presentation at AWS re:Invent 2014:
accenture-reinvent-breakout-session-deck-migration-to-cloud-v3-aws-template-final-cs

Micro Focus Enterprise Server and development tools on AWS

These are two different situations where the server lends itself to the cloud and developer tools do not.

1.     Micro Focus Enterprise server - This is like an application server for COBOL applications that ran on the mainframe (cloud 1.0) and have been moved to open systems to save cost.  This server can run on AWS EC2 with no problems (will need to check the OS they are running...if not windows or linux will be an issue to migrate OS platforms).  Running MF Enterprise Server in AWS (cloud 2.0) makes all the sense in the world as these applications are running very simple UI interfaces and the application is made for hosted/cloud computing.

2.     Micro Focus Enterprise Developer - This product runs in Eclipse or MS Visual Studio environment.  It does not lend itself to the cloud (at least a virtual server environment) as each developer has their own developer tool (lends itself more to a VDI environment).  If there were not that many developers, each run could have their own Windows EC2 instance.   What could also be done is to have one Windows EC2 Instance and each developer have their own login which would give them their own desktop.  When doing this, you would have to make sure you size the one instance accordingly (as their could be many concurrent users).