This is the 4th version of the Video Ad Server: A flowchart of the main network architecture built around the AWS Server; that hosted the majority of the main parts. The AWS Cloud Server was utilized in many ways: The AWS CloudFront Server was setup with [progressive & streaming] distributions. Which are optimized & working directly with Simple Storage Service (S3), Amazon Elastic Compute Cloud (EC2), Amazon Elastic Load Balancing, and Amazon Route 53. The Amazon Elastic Compute Cloud (EC2) Instances were running multiple [AMIs] Amazon Machine Image's (Each with different server functions) such as: Red5 (Streaming Media Server), Xuggler (Media Encoding), KalturaCE (Media Management Console: All in one Solution [Community Edition] for 'X' User Accounts which included online re-mixing of video, HD Video, Syndication Options, Sharing Abilities, Advertising Integration... Specifically I had set an OpenX Open Video Advertising (OVA) Server to work with the videos which would be 'Managed' and 'Delivered' thru this AMI) & Ubuntu (Server). Also a Wowza Media Server 3, 3rd party server addition, was offered by [Wowza & AWS] as an addition to your AWS Account thats separate from any processes on the main server. Creating a Wowza Streaming Media Server which was not on EC2, S3, CloudFront nor any other main AWS Solution. Amazon CloudFront works seamlessly with dynamic web applications running in Amazon EC2 or your origin running outside of AWS without any custom coding or proprietary configurations, making the service simple to deploy and manage. You can use a single Amazon CloudFront distribution to deliver your entire website, including both static and dynamic (or interactive) content.