Deploy the Environment

Create a new Application

1. Find Elastic Beanstalk and select Elastic Beanstalk.

2. Select Applications and then click Create application.

3. Enter fcj-aws-application for Application name. Click Create.

Create a new Environment

1. Go to the console of our fcj-aws-application application and click Create new application.

2. In Environment tier, Select Web server environment.

3. Type fcj-aws-application-prod-env for both Environment name and Domain.

4. Click Check availability to check if your name is valid.

5. In Platform, select Managed platform for Platform type and then choose .NET Core on Linux.

6. Select Sample application for Application code to utilize AWS providing source code.

• In Presets section, select High availability for building high availability environment.
• Click Next.

7. Select Create and use new service role to generate new service role automatically.

• Select aws-keypair and fcj-aws-ec2-instance-profile created in the previous steps.
• Click Next.

9. Select fcj-aws-vpc.

10. Select 2 Private Subnet for Instance Subnets.

11. Scroll down then select Next.

12. Select 1 minute for Monitoring interval, that means EC2 instance will send metrics for each minute.

• When initialization, Elastic Beanstalk creates a new Security Group for EC2 Instance, so we can skip EC2 security groups section.

13. Select Load balanced for Environment type then type the number of minimum instances and maximum instances.

14. Instance types, select t2.micro.

15. In the Load balancer subnets section, select 2 Public Subnet.

16. Select Application load balancer and Dedicated for Load balancer type.

17. Select Next.

18. Select Enhanced for Health reporting system.

19. Select Activated for Log streaming so we can view logs using CloudWatch.

20. Enter your email to receive significant messages from Elastic Beanstalk Environment.

21. Deployment policy select Rolling and leave others as their default values.

• Deployment policy types:

  • All at once: Deploy the new version to all instances simultaneously. All instances in your environment are out of service for a short time while the deployment occurs.
  • Rolling: Deploy the new version in batches. Each batch is taken out of service during the deployment phase, reducing your environment’s capacity by the number of instances in a batch.
  • Rolling with additional batch: Deploy the new version in batches, but first launch a new batch of instances to ensure full capacity during the deployment process.
  • Immutable: Deploy the new version to a fresh group of instances by performing an immutable update.
  • Traffic splitting: Deploy the new version to a fresh group of instances and temporarily split incoming client traffic between the existing application version and the new one.

22. Select Activated for Instance log streaming.

• Select Next.

23. Review your choices and select Submit.

24. Wait for about 10 minutes for the environment to be created.