Using AWS Elastic Beanstalk as a guide for application configuration

PaaS services fit in that world in between serverless and roll-your-own infrustructure.  AWS Elastic Beanstalk is a PaaS service exposes their their service usage to teach you the right way to deploy web applications. The EB team eats their own AWS dogfood and generates a full featured environment via a generated CloudFormation template that you can examine and leverage.

For this example we will deploy Apache Tika document parser as a service. We'll leverage a previous blog article PaaS Document Parsing With Tika and EBS for the instructions.  A shortened version is below

Topology Discussion

This diagram shows the components deployed to make an autoscaling web application that leverages Elastic Beanstalk , IAM, ALBs and other AWS goodness.

Resources and Services

Elastic Beanstalk uses these services to provision and deploy a simple no-database web application like the Apache Tika Parser.  We use the CLI to upload the configuration which Elastic Beanstalk then uses to generate a CloudFormation template that describes all  of the components.

This section needs to be fleshed out
AWS Resources and ServicesInformation
Elastic Beanstalk Application.tbd
Cloud Formation stack.tbd
Deployment configuration bucket.tbd
Launch Template.tbd
Security Groups.tbd
ALB.tbd
    ALB Listener.tbd
    ALB Target Groups.tbd
      Autoscale Group.tbd
      Autoscale Group Policy.tbd
      Cloudwatch Alarms.tbd
      EC2.tbd
      IAM Roles.tbd

      Video Version


      Short Version Deployment Instructions

      You must set up your environment for Elastic Beanstalk CLI deployments. 
      PrerequisiteCommand
      aws-access-id and aws-secret-key exist and are installed in ~/.aws/configMust be generated in console

      Can be added to config file by aws cli or by eb init in interactive mode.
      SSH pair exists and is available in ~/.sshCan be created externally or may be created be eb init interactive mode if ssh is installed
      Python is installedSee platform instructions
      ElasticBeanstalk CLI is installed
      https://github.com/aws/aws-elastic-beanstalk-cli-setup      		Clone the repository
      Run installer
      • python .\aws-elastic-beanstalk-cli-setup\scripts\ebcli_installer.py


      Steps

      These step describe deploying a pre-build Java jar file.
      Step Command
      open a command prompt .
      make a working directory .
      cd into the working directory CLI assumes the deployment is for thecurrent working directory 
      Download Apache tika into the working directory wget or use web site https://tika.apache.org/download.html
      Initialize the environment eb init <app-name> --platform corretto-8 --keyname <ssh key name> --region <region>

      Example (app named fsi-eb-teka and SSH key pair aws-eb):
      eb init fsi-eb-tika --platform corretto-8 --keyname aws-eb --region us-east-2
      Deploy the jar as an application eb create <app-name>-dev --cname <app-name>-dev --elb-type application --enable-spot -it t2.micro --envvars PORT=9998 --tags mytag=myvalue

      Example (app named fsi-eb-tika , append -dev for dev environment)
      eb create fsi-eb-tika-dev --cname fsi-eb-tika-dev --elb-type application --enable-spot -it t2.micro --envvars PORT=9998 --tags mytag=myvalue
      Verify GET app name returned by the create

      Example (deployment named fsi-eb-tiva-dev)
      fsi-eb-tika-dev.us-east-2.elasticbeanstalk.com
      Un-deploy eb terminate <app-name>

      Example (deployment named fsi-eb-tiva-dev)
      eb terminate fsi-eb-tika-dev --force


        Created 4/2020

        Comments

        Post a Comment

        Popular posts from this blog

        Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

        Image
        I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Update Driver  does  not  install the RNDI
        Read more

        Understanding your WSL2 RAM and swap - Changing the default 50%-25%

        Image
        The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaults to a maximum RAM size of 5
        Read more

        Almost PaaS Document Parsing with Tika and AWS Elastic Beanstalk

        Image
        The Apache Tika project provides a  library capable of parsing and extracting data and meta data from over 1000 file types.  Tika is available as a single jar file that can be included inside applications or as a deployable jar file that runs Tika as a standalone service. This blog describes deploying the Tika jar as an auto-scale service in Amazon AWS Elastic Beanstalk.  I selected Elastic Beanstalk because it supports jar based deployments without any real Infrastructure configuration. Elastic Beanstalk auto-scale should take care of scaling up and down for for the number of requests you get. Tika parses documents and extracts their text completely in memory. Tika was deployed for this blog using EC2 t2.micro instances available in the AWS free tier. t2.micro VMs are 1GB which means that you are restricted in document complexity and size. You would size your instances appropriately for your largest documents.   Preconditions An AWS account. AWS access id and secret key.
        Read more