Elastically grow/shrink instances into cloud/virtualized environments. There are four use cases for the connector.
First, if the Controller detects that the load on the machine instances hosting an application is too high, the aws-connector-extension may be used to automate creation of new virtual machines to host that application. The end goal is to reduce the load across the application by horizontally scaling up application machine instances.
Second, if the Controller detects that the load on the machine instances hosting an application is below some minimum threshold, the aws-connector-extension may be used to terminate virtual machines running that application. The end goal is to save power/usage costs without sacrificing application performance by horizontally scaling down application machine instances.
Third, if the Controller detects that a machine instance has terminated unexpectedly when the connector refreshes an application machine state, the aws-connector-extension may be used to create a replacement virtual machine to replace the terminated application machine instance. This is known as our failover feature.
Lastly, the aws-connector-extension may be used to stage migration of an application from a physical to virtual infrastructure. Or the aws-connector-extension may be used to add additional virtual capacity to an application to augment a preexisting physical infrastructure hosting the application.
Always feel free to fork and contribute any changes directly via GitHub.
For any support questions, please contact AppDynamics Center of Excellence.
3.6 and above
|2 DEC 2015|
1) Removed typica library and using AWS client library 2) Fix for Name not specified error 3) Added option to provide name for the AWS instance 4) Added all AWS supported regions and instance types
1) Added support to provide SubnetID and Security Group Id
1) Code changes to make the connector work with 4.3 controller.