Amazon EC2 Connector
Overview
The Amazon EC2 Connector allows Mendix makers to integrate with AWS EC2.
It provides the following functionality:
- Describe Instances
- Start Instance
- Stop Instance
Pre-requisite – It requires AWS Authentication Module.
For more information about our AWS Connector strategy, please see the Mendix Evaluation Guide
Documentation
1 Introduction
This Amazon EC2 Connector allow you to integrate with the Amazon EC2 service on AWS.
Amazon Elastic Compute Cloud (Amazon EC2) provides scalable computing capacity in the Amazon Web Services (AWS) Cloud. Using Amazon EC2 eliminates your need to invest in hardware up front, so you can develop and deploy applications faster. You can use Amazon EC2 to launch as many or as few virtual servers as you need, configure security and networking, and manage storage. Amazon EC2 enables you to scale up or down to handle changes in requirements or spikes in popularity, reducing your need to forecast traffic.
The Amazon EC2 Connector provides the following actions:
- Describe Instances
- Start Instance
- Stop Instance
1.1 Typical Use Cases
- Application to manage the use of existing EC2 instances
1.2 Features
- List existing instances
- Start and stop instances
1.3 Limitations
- Limited to a single AWS zone
1.4 Prerequisites
- Mendix Studio Pro 9.22.0
- An AWS Account that has access to the Amazon EC2 service
- IAM user should be created with API keys for AccessKey and SecretKey
1.5 Dependencies
2 Installation
- Download the Amazon EC2 Connector from the Marketplace
3 Configuration
If you are using Static Credentials update the following constants:
- AWSEC2Connector.AccessKey
- AWSEC2Connector.SecretKey
If you are using Session based Credentials update the following constants:
- AWSEC2Connector.ClientCertificateID
- AWSEC2Connector.ProfileARN
- AWSEC2Connector.RoleARN
- AWSEC2Connector.SessionName
- AWSEC2Connector.TrustAnchorARN
Change the AWSEC2Connector.UseStaticCredentials constant to false
4 Troubleshooting
- If you are running into issues with authentication and are using Session Based Credentials verify that the generated Role has both access to the Translate service and the AWS Roles Anywhere service.
5 Read More