Skip to content

Latest commit

 

History

History
91 lines (83 loc) · 3.98 KB

File metadata and controls

91 lines (83 loc) · 3.98 KB

aws-cloudformation-performance-testing

If you are beginning your journey with Senzing, please start with Senzing Quick Start guides.

You are in the Senzing Garage where projects are "tinkered" on. Although this GitHub repository may help you understand an approach to using Senzing, it's not considered to be "production ready" and is not considered to be part of the Senzing product. Heck, it may not even be appropriate for your application of Senzing!

Synopsis

For use in testing versions of Senzing located on the staging server.

Launch AWS Cloudformation

  1. 🤔 Warning: This Cloudformation deployment will accrue AWS costs. With appropriate permissions, the AWS Cost Explorer can help evaluate costs.
  2. Visit AWS Cloudformation console
  3. In upper-right, click "Create stack" > "With new resources (standard)"
  4. In Create stack page
    1. Check ":radio_button: Upload a temporary file"
    2. Click "Choose file" button
    3. Select local copy of cloudformation.yaml
    4. In lower-right, click on "Next" button.
  5. In Specify stack details
    1. In Stack name
      1. Make a stack starting with your initials. (So we can see who owns a stack.) Example:
        1. mjd-1001
    2. In Parameters
      1. In Security responsibility
        1. Understand the nature of the security in the deployment.
        2. Once understood, enter "I AGREE".
      2. In Senzing installation
        1. Enter the version of senzingapi you want to test. Example: 2.5.0-21104
        2. Accept the End User License Agreement
      3. In Security
        1. Enter your email address. Example: [email protected]
    3. Other parameters are optional. The default values are fine.
    4. In lower-right, click "Next" button.
  6. In Configure stack options
    1. In lower-right, click "Next" button.
  7. In Review {stack-name}
    1. Near the bottom, in Capabilities
      1. Check ":ballot_box_with_check: I acknowledge that AWS CloudFormation might create IAM resources."
    2. In lower-right, click "Create stack" button.

Testing

  1. Visit AWS Cloudformation console
  2. Choose cloudformation stack that was deployed for testing
  3. Choose "Outputs" tab
    1. Open value for 0penFirst in a new browser tab
      1. Page will show warning because of the self-signed certificate used for HTTPS by the Application Load Balancer. Figure out how to proceed past the warning.
      2. You will be prompted for email and password. From the "Outputs" tab, use UserName and UserInitPassword values.
      3. Supply a new password.
    2. Open value for UrlApiServerHeartbeat in a new browser tab
      1. Verify that API server responds
      2. Change URL so that the URI is /api/entities/1
        1. Verify that an entity was returned
    3. Open value for UrlWebApp in a new browser tab
      1. In the "Entity Search" web app
        1. Search for "Robert Smith"
        2. Verify result
    4. Open value for UrlXterm in a new browser tab
      1. In XTerm window, enter
        1. G2Command.py
        2. (g2cmd) getEntityByEntityID 1
        3. Verify result
    5. Open value for UrlSwagger in a new browser tab
      1. Specify server
        1. Servers, choose {protocol}://{host}:{port}{path}
        2. protocol: https
        3. host: On "Outputs" tab, value of Host. Be careful of leading or trailing spaces.
        4. port: 443
        5. path: /api
        6. Verify "Computed URL:"
      2. Try URIs
        1. GET /heartbeat
        2. GET /entities/{entitId}