actions VS aws-node-termination-handler

https://azure.github.io/actions/ would probably be a good place to start.

# Docs for the Azure Web Apps Deploy action: https://github.com/Azure/webapps-deploy # More GitHub Actions for Azure: https://github.com/Azure/actions name: Build and deploy Node.js app to Azure Web App on: push: branches: - master workflow_dispatch: jobs: build: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - name: Set up Node.js version uses: actions/setup-node@v1 with: node-version: '18.x' - name: npm install, build, and test run: | npm install npm run build --if-present npm run test --if-present env: DB_USER: ${{ secrets.DB_USER_PROD }} DB_USER_PW: ${{ secrets.DB_USER_PW_PROD }} DB_NAME: ... DB_HOST: ... DB_PORT: ... DB_TYPE: ... - name: Zip artifact for deployment run: zip release.zip ./* -r - name: Upload artifact for deployment job uses: actions/upload-artifact@v3 with: name: node-app path: release.zip deploy: runs-on: ubuntu-latest needs: build environment: name: 'Production' url: ${{ steps.deploy-to-webapp.outputs.webapp-url }} steps: - name: Download artifact from build job uses: actions/download-artifact@v2 with: name: node-app - name: unzip artifact for deployment run: unzip release.zip - name: 'Deploy to Azure Web App' id: deploy-to-webapp uses: azure/webapps-deploy@v2 with: app-name: 'x-server-prod' slot-name: 'Production' publish-profile: ${{ secrets.AZUREAPPSERVICE_PUBLISHPROFILE_2C89E24A84EF471D9669C85CCA28D457 }} package: . - name: Delete zip file run: rm release.zip

To interact with Azure services, you will need to use specific Azure Actions for GitHub. These actions are provided by Microsoft and can be found in their official GitHub repository: https://github.com/Azure/actions

GitHub Actions for Azure: This GitHub Action allows developers to automate tasks on the Microsoft Azure platform. With this action, developers can easily integrate Azure services into their workflows, such as Azure Functions, App Services, and Kubernetes. This can help streamline DevOps workflows by automating tasks such as deployment, testing, and scaling on the Azure platform.

# Docs for the Azure Web Apps Deploy action: https://github.com/Azure/webapps-deploy # More GitHub Actions for Azure: https://github.com/Azure/actions # More info on Python, GitHub Actions, and Azure App Service: https://aka.ms/python-webapps-actions name: Build and deploy Python app to Azure Web App - cbmrs on: push: branches: - master workflow_dispatch: jobs: build: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - name: Set up Python version uses: actions/setup-python@v1 with: python-version: '3.10' - name: Create and start virtual environment run: | python -m venv venv source venv/bin/activate - name: Install dependencies run: pip install -r requirements.txt # Optional: Add step to run tests here (PyTest, Django test suites, etc.) - name: Upload artifact for deployment jobs uses: actions/upload-artifact@v2 with: name: python-app path: | . !venv/ deploy: runs-on: ubuntu-latest needs: build environment: name: 'production' url: ${{ steps.deploy-to-webapp.outputs.webapp-url }} steps: - name: Download artifact from build job uses: actions/download-artifact@v2 with: name: python-app path: . - name: 'Deploy to Azure Web App' uses: azure/webapps-deploy@v2 id: deploy-to-webapp with: app-name: 'cbmrs' slot-name: 'production' publish-profile: ${{ secrets.AzureAppService_PublishProfile_01e00190d8174a8490a3de88abd5b3ef }}

The GitHub Actions for Azure repository is where you can find the latest and greatest information on the official GitHub actions available to deploy your workloads to Azure using GitHub. You can of course search for these in the GitHub marketplace as well!

GitHub Actions for deploying to Azure

Disaster recovery is a critical component of any IT infrastructure. It ensures that your applications and data are protected in the event of an unexpected outage or disaster. In this blog post, we will explore different disaster recovery strategies for Amazon Elastic Compute Cloud (EC2) deployments.

When you are using compute you have a lot of options. One of these options is Amazon EC2. In a world where more and more workloads become serverless. You might still have this use-case that is better off on EC2. But, how do you combine EC2 with compliance and security? In this blog post we will explore how we can build a compliant and secure EC2 stack.

In this article, a WEB application using the latest version of Angular in a built Docker image will be hosted on Amazon EC2 (Elastic Compute Cloud) and deployed by Amazon ECS (Elastic Container Service) using an Amazon ECR (Elastic Container Registry) containers repository.

The single most important development in hosting since the invention of EC2 is defined by its own 3-letter acronym: k8s. Kubernetes has won the “container orchestrator” space, becoming the default way that teams across industries are managing their compute nodes and scheduling their workloads, from data pipelines to web services.

EC2

Then in 2020, I started working with AWS. My first two years with AWS were mostly interacting with the Node.js apps I've deployed in EC2 and reviewing logs since we had a DevOps engineer who managed the cloud infrastructure.

If you want to learn more about EC2 and get detailed information, I suggest you start your journey by visiting https://aws.amazon.com/ec2/. This is the best place to begin learning about EC2.

AWS - Cloud Computing AWS - EC2 Wikipedia - Cloud Computing Guru99 - Cloud Computing Cloudflare - Cloud Computing Cloudzero - Statistics Zippia - Statistics

Say that we have an application running behind a public-facing Application Load Balancer (ALB). The load balancer's target can be any supported target, including ECS containers, EC2 instances or even Lambda functions. Because the application is only available to authenticated users, we want to find a solution to identify them.

Although I'll use Lambda functions in the examples, we can transfer the concepts to other compute resources, like EC2 instances, and ECS or EKS containers.