Cloud deployment overview (AWS, Azure) in Spring Boot - Mini Project: Build & Apply

Cloud deployment overview (AWS, Azure)

📖 Scenario: You are a developer preparing to deploy a simple Spring Boot application to the cloud. You want to understand the basic setup steps for deploying your app on two popular cloud platforms: AWS and Azure.This project will guide you through creating a basic deployment configuration for both AWS and Azure, helping you see how cloud deployment works in a simple, clear way.

🎯 Goal: Build a basic deployment configuration for a Spring Boot app on AWS and Azure. You will create initial deployment data, add configuration details, apply core deployment logic, and finalize the deployment setup.

📋 What You'll Learn

Create initial deployment data for AWS and Azure

Add configuration variables for deployment environment

Apply deployment logic to prepare the app for cloud

Complete the deployment configuration with final settings

💡 Why This Matters

🌍 Real World

This project models how developers prepare deployment configurations for cloud platforms like AWS and Azure before deploying applications.

💼 Career

Understanding cloud deployment basics is essential for roles like cloud engineer, DevOps engineer, and backend developer working with cloud infrastructure.

1

Create initial deployment data

Create a dictionary called deployment_data with two keys: 'AWS' and 'Azure'. Each key should have a nested dictionary with 'app_name' set to 'springboot-app' and 'region' set to 'us-east-1' for AWS and 'eastus' for Azure.

Spring Boot

# Your code here

Hint

Use a dictionary with keys 'AWS' and 'Azure'. Each value is another dictionary with 'app_name' and 'region'.

2

Add deployment environment configuration

Create a variable called environment and set it to the string 'production'. This will represent the deployment environment for both AWS and Azure.

Spring Boot

deployment_data = {
    'AWS': {'app_name': 'springboot-app', 'region': 'us-east-1'},
    'Azure': {'app_name': 'springboot-app', 'region': 'eastus'}
}
# Your code here

Hint

Just create a variable named environment and assign it the value 'production'.

3

Apply deployment logic to prepare app

Use a for loop with variables cloud and config to iterate over deployment_data.items(). Inside the loop, add a new key 'environment' to each config dictionary and set it to the value of the environment variable.

Spring Boot

deployment_data = {
    'AWS': {'app_name': 'springboot-app', 'region': 'us-east-1'},
    'Azure': {'app_name': 'springboot-app', 'region': 'eastus'}
}
environment = 'production'
# Your code here

Hint

Use a for loop to add the 'environment' key to each cloud config.

4

Complete deployment configuration

Add a new key 'deployment_status' with value 'ready' to the deployment_data['AWS'] dictionary to mark AWS deployment as ready.

Spring Boot

deployment_data = {
    'AWS': {'app_name': 'springboot-app', 'region': 'us-east-1'},
    'Azure': {'app_name': 'springboot-app', 'region': 'eastus'}
}
environment = 'production'

for cloud, config in deployment_data.items():
    config['environment'] = environment
# Your code here

Hint

Add the 'deployment_status' key with value 'ready' to the AWS config.

Practice

1. What is the main benefit of deploying a Spring Boot application on cloud platforms like AWS or Azure?

easy

A. You don't need to manage physical servers yourself

B. You must write your own operating system

C. You have to buy hardware for deployment

D. You need to install Spring Boot manually on each device

Solution

1. Step 1: Understand cloud deployment basics

   Cloud platforms provide infrastructure so you don't manage physical servers.

2. Step 2: Identify the benefit for Spring Boot apps

   Deploying on AWS or Azure means your app runs online without hardware management.

3. Final Answer:

   You don't need to manage physical servers yourself -> Option A

4. Quick Check:

   Cloud deployment = no physical server management [OK]

Hint: Cloud means no physical server hassle [OK]

Common Mistakes:

• Thinking you must buy or manage hardware
• Confusing cloud with local installation
• Assuming manual OS installation is needed

2. Which AWS service is commonly used to deploy Spring Boot applications with minimal server management?

easy

A. AWS Elastic Beanstalk

B. AWS Lambda

C. Amazon EC2

D. Amazon S3

Solution

1. Step 1: Review AWS services for app deployment

   Amazon EC2 is virtual servers, AWS Lambda is serverless functions, Elastic Beanstalk manages app deployment, and S3 is storage.

2. Step 2: Choose the service for easy Spring Boot deployment

   Elastic Beanstalk automates deployment and scaling for Spring Boot apps with minimal server management.

3. Final Answer:

   AWS Elastic Beanstalk -> Option A

4. Quick Check:

   Elastic Beanstalk = easy app deployment [OK]

Hint: Elastic Beanstalk automates app deployment on AWS [OK]

Common Mistakes:

• Choosing EC2 which requires manual server setup
• Confusing Lambda with full app hosting
• Selecting S3 which is only for storage

3. Given this Azure deployment option for a Spring Boot app: Azure App Service, what is the expected behavior after deployment?

medium

A. You need to install Java manually on each server

B. You must manually configure virtual machines and load balancers

C. The app runs on managed infrastructure with automatic scaling

D. The app only runs locally on your development machine

Solution

1. Step 1: Understand Azure App Service features

   Azure App Service provides managed hosting with automatic scaling and patching.

2. Step 2: Identify expected app behavior after deployment

   The Spring Boot app runs online on managed infrastructure without manual VM setup or Java installation.

3. Final Answer:

   The app runs on managed infrastructure with automatic scaling -> Option C

4. Quick Check:

   Azure App Service = managed, scalable hosting [OK]

Hint: Azure App Service manages servers and scaling [OK]

Common Mistakes:

• Thinking manual VM setup is required
• Assuming app runs only locally
• Believing manual Java install is needed

4. You deployed a Spring Boot app on AWS EC2 but it is not accessible from the internet. What is the most likely cause?

medium

A. AWS Lambda function is missing

B. Security group does not allow inbound HTTP traffic

C. Spring Boot app is not installed

D. Amazon S3 bucket is empty

Solution

1. Step 1: Check network access for EC2 instance

   EC2 instances need security groups allowing inbound HTTP (port 80) or HTTPS (port 443) traffic.

2. Step 2: Identify why app is inaccessible

   If security group blocks HTTP, the app won't be reachable even if running correctly.

3. Final Answer:

   Security group does not allow inbound HTTP traffic -> Option B

4. Quick Check:

   Security group rules control internet access [OK]

Hint: Check EC2 security group inbound rules first [OK]

Common Mistakes:

• Assuming app is not installed without checking network
• Confusing EC2 with Lambda or S3 services
• Ignoring firewall/security group settings

5. You want to deploy a Spring Boot app on Azure with minimal management and automatic scaling. Which approach best fits this need?

hard

A. Use Azure Virtual Machines and manually configure scaling

B. Run the app on a local server and connect to Azure SQL Database

C. Store the app in Azure Blob Storage

D. Deploy on Azure App Service with autoscale enabled

Solution

1. Step 1: Compare Azure deployment options for minimal management

   Azure Virtual Machines require manual setup and scaling; Blob Storage is for files; local servers are not cloud deployment.

2. Step 2: Identify best option for automatic scaling and minimal management

   Azure App Service provides managed hosting with autoscale features, ideal for Spring Boot apps.

3. Final Answer:

   Deploy on Azure App Service with autoscale enabled -> Option D

4. Quick Check:

   Azure App Service + autoscale = easy, scalable deployment [OK]

Hint: Choose managed service with autoscale for ease [OK]

Common Mistakes:

• Picking VMs which need manual scaling
• Confusing storage with app hosting
• Using local servers instead of cloud