Skip to content

Quickstarts for deploying Azure Spring Cloud Reference Architecture - using Terraform, ARM Template, Bicep or Azure CLI

License

Notifications You must be signed in to change notification settings

kkizer/azure-spring-cloud-reference-architecture

 
 

Repository files navigation

Quickstart - Azure Spring Cloud Reference Architecture

Azure Spring Cloud

Azure Spring Cloud is a fully managed service for Spring Boot apps that lets you focus on building the apps that run your business without the hassle of managing infrastructure. Simply deploy your JARs or code and Azure Spring Cloud will automatically wire your apps with the Spring service runtime. Once deployed you can easily monitor application performance, fix errors, and rapidly improve applications.

Azure Spring Cloud is jointly built, operated, and supported by Microsoft and VMware. You can use Azure Spring Cloud for your most demanding applications and be assured that Microsoft and VMware are standing behind the service to ensure your success.

Quickstart Overview

This repository contains instructions for creating an Azure Spring Cloud reference architecture that can be used for experimenting with Spring Boot applications in a typical enterprise landing zone design for a regulated organization. It uses a hub and spoke architecture with a single spoke. East/West traffic (traffic between resources in the hub and resources in the spoke) is filtered with Network Security Groups and North/South traffic (traffic between the Internet and resources in the hub or spoke) is routed through and mediated with an instance of Azure Firewall.

lab image

Additional features of this quickstart are:

  • Azure Spring Cloud is deployed using vnet-injection to allow for mediation inbound and outbound traffic to the Azure Spring Cloud Instance and deployed applications.
  • The Azure Firewall instance has been configured to write its logs to a Log Analytics Workspace. You can leverage these Kusto queries to analyze Azure Firewall log data written to Log Analytics.
  • Hub and Spoke Virtual Networks are configured to use Azure Firewall for DNS queries utilizing the DNS Proxy feature of Azure Firewall.
  • Azure Private DNS zones for Azure Spring Cloud and support services deployed with Private Endpoints
  • A single Windows Server 2016 Virtual Machine the hub Virtual Network for testing access to applications deployed into the Azure Spring Cloud instance. This virtual machine is configured with the Microsoft Monitoring Agent and is integrated with the Log Analytics Workspace. This VM is not exposed to the internet and is only accessible via Azure Bastion (for brevity, both the VM and Azure Bastion are not shown in the diagram).
  • Log Analytics Workspace where Azure Spring Cloud, Azure Firewall, and the virtual machine deliver logs and metrics.
  • Instance of Azure Key Vault deployed with a Private Endpoint for secrets and certificates storage for applications deployed to Azure Spring Cloud
  • Instance of Azure Database for MySQL deployed with a Private Endpoint. This can be used to deploy the sample app described in this document.
  • Instance of Azure Bastion for connection to the Windows Server 2016 virtual machine running in the hub virtual network.

Deployment Process

There are three methods to deploy the architecture in the diagram documented in this repo.

ARM, Terraform, CLI and Bicep scripts will deploy Azure Spring Cloud in a secure environment. Once the core infrastructure has been deployed, the Post Installation process can be followed to test sample applications.

Build your solutions today!

Azure Spring Cloud abstracts away the complexity of infrastructure management and Spring Cloud middleware management, so you can focus on building your business logic and let Azure take care of dynamic scaling, patches, security, compliance, and high availability. With a few steps, you can provision Azure Spring Cloud, create applications, deploy, and scale Spring Boot applications and start monitoring in minutes. We will continue to bring more developer-friendly and enterprise-ready features to Azure Spring Cloud.

We would love to hear how you are building impactful solutions using Azure Spring Cloud. Get started today – deploy Spring applications to Azure Spring Cloud using this quickstart!

Resources

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

About

Quickstarts for deploying Azure Spring Cloud Reference Architecture - using Terraform, ARM Template, Bicep or Azure CLI

Resources

License

Code of conduct

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • HCL 36.5%
  • Bicep 31.0%
  • Shell 28.5%
  • PowerShell 4.0%