create framework with no AWS console actions and all actions should be through the various AWS API calls

Your task is to create framework that simplifies the tasks associated with bringing online a set of fictitious services/applications e.g. deploy application 'stack' in AWS. The objective is to abstract away the complexities and various commands needed to 'deploy' the application set. Further, it should account for what has been deployed both in type and quantity. Assume that there are three services as listed: - Application fakeA: uses port 5555, communicates exclusively with application fakeB - Application fakeB: uses port 6666, communicates with applications fakeA and fakeC - Application fakeC: uses port 7777, communicates with application fakeB and accepts connection from the outside world on port 8888. You should always maintain this relationship when launching applications, that is, the below set relationship is are the complete application stack and if capacity demands, you should launch additional instances maintaining the same relationship: - Application fakeA has a single instance - Application fakeB has a single instance - Application fakeC has two instances Success criteria: - Launch all instances correctly from command line - Ability to shutdown incremental units of the application stack - Launch additional instances of the application stack - At any given time, be able to display quantity and state of the application stack Design Constraints Assume no action is actually taken within AWS console, all actions should be through the various AWS API calls. The framework should be written in Python, C/C++ or Java. Very limited use of Bash is acceptable, but discouraged. You can use any technology stack you wish even AWS services. You should make sure you can justify the choice in technology. The objectives imply state, please make sure you manage that state and make it applicable to the overall objectives of flexibility/extensibility. To avoid incurring costs, you should 'mock' services, just make sure they mimic the associated AWS call. Most importantly Your code must be well-structured and built in the spirit of maintainability and extensibility. Additional features are encouraged though not required: integration with dashboards/reporting infrastructure, reconcile current deployed versus actual (e.g. what is really already deployed), validate services are completely functional (e.g. up and running), integration with content management system of choice (e.g. SVN, Git, etc.).