It is possible to easily deploy and run
.NET generated applications in AWS Elastic Beanstalk.
Before deployment, using a new Environment in the Knowledge Base is recommended to generate a new deployment version that runs locally in the Tomcat or IIS of the computer used to work with GeneXus connected to the AWS RDS database, or any Cloud Database. In this way, you can make the configurations that will be used in the production database.
Before starting, make sure that you have MSDeploy installed on your machine (only if you use
- Amazon Web Services Account.
- AWS Access Key creation for managing AWS Resources from the Command Line Interface.
- An AWS RDS Database.
- MSDeploy installed on your machine.
* See minimal required policy to Deploy to EBS without FullAccess.
1. Before making a deployment, you must configure your Data Store to connect to the target Database, which may be an AWS RDS Database. (ref.: Cloud Database)
2. Run a Build All.
3. Go to the Build menu and select the Deploy Application option.
4. In the Deployment screen:
1. Select the Main objects to be included in the deployment.
2. In Target, select the option "AWS Elastic Beanstalk".
3. Set the following properties as indicated below:
1. AWS Access Key/Secret Access Key: Enter your AWS Access Key generated from: AWS Access Key creation.
2. AWS Default Region: Select your preferred region (localization) for your Deployment.
3. Application Name: It's the name used to display the application. After deployment, it will be visible from AWS Elastic Beanstalk Portal.
4. Application Version: The Application version name. Every deployment must have a different version name (or will fail).
5. Application Environment Name: Your environment name. Defaults to "Production", but you can create other environments such as "Test", "Preproduction".
5. After selecting the main objects and configuring the necessary properties for the automatic deployment, press the Deploy button. It will build the WAR package (when JAVA) or a Web Deploy ZIP (for .NET), as well as upload and deploy it in AWS Elastic Beanstalk.
6. You can check the Application URL, Status and Configuration from AWS Elastic Beanstalk Portal.
"The instance profile aws-elasticbeanstalk-ec2-role associated with the environment does not exist."
Solution: Log in to AWS Console. Create any Elastic Beanstalk Environment through the Console, as it will create automatically the necessary IAM profile 'aws-elasticbeanstalk-ec2-role'. You can delete the environment after.
What is AWS Elastic Beanstalk