Skip to content
  • ZipCode Api
  • Blog
  • About RedLine13
RedLine13
Primary Navigation Menu
Menu
  • Start Testing
  • Demo
  • Pricing
  • Docs
    • Knowledge Base
    • AWS IAM Setup Instructions
    • Running a RedLine13 Load Test with Advanced Options
    • Scalability
    • Writing Open Load Tests in Your Language
    • Jenkins Plugin Setup
    • AWS Approval for Large Tests
    • Pro Features
  • JMeter
  • Partners

Improved Security with Instance Profiles

By: RedLine13

To provide finer grain control over what instances RedLine13 can start, stop, terminate we have added support for launching EC2 load agents with instance profiles.

Advanced Topic

This is an advanced topic and only supported for premium customers.

You can read the AWS Blog Post on Restricting with IAM Policy and instance-profiles.

To get started you must set up an instance profile, which is documented at “How to create IAM instance Profile“.

Setting up Policy

To use this feature you will have to update your policy.   Add

"iam:PassRole",

to the section that gives permission to the RedLine13 role.

Then limit the ability to stop or terminate your instances by using a condition:

{
    "Action": [
        "ec2:StopInstances",
        "ec2:TerminateInstances"
    ],
    "Effect": "Allow",
    "Resource": "*",
    "Condition": {
        "StringEquals": {
            "ec2:InstanceProfile": "arn:aws:iam::ACCOUNT:instance-profile/INSTANCE_PROFILE_NAME"
        }
    }
}

For a list of all permissions we require and detailed full policy you can read our Key Setup Instructions.

Using in RedLine Load Tests

This plugin is available for all tests, but you can setup defaults for your account.

a) Go to account settings: https://www.redline13.com/Account/settings

b) Configure your instance profile name or instance profile ARN

  • By selecting this checkbox, this instance-profile will be configured by default for every test.

instance-profile-name-setup

c) Override or turn on during load test start.

start-test-with-instance-profile

This feature furthers our approach to giving users fine grain control and limiting our access to launching and terminating only RedLine13 load agents.

2017-02-15
Previous Post: Using Selenium WebDriver to Run Scalable Load Tests
Next Post: Assigning Elastic IP to Load Agents

Recent Posts

  • Use Cases for the JMeter Dashboard Report
  • AWS Costs for Large JMeter Load Tests Run by Real Customers
  • AWS Multiple Account Setup for Load Testing – Securing your Application Environment
  • Merge Results for Data Analysis
  • Debug your JMeter Test with Output Files

Related

  • Free Load Test Trial
  • SAML SSO
  • E-Learning Companies and Load Testing
  • AWS Multiple Account Setup for Load Testing – Securing your Application Environment
  • AWS Costs for Large JMeter Load Tests Run by Real Customers
  • Why BlazeMeter Customers Chose RedLine13
  • Is BlazeMeter Scared Of RedLine13?
  • RedLine13 Customer HBO Latin America Speaks at Customer Advisory Board Meeting
  • ThinkLogic and High Volume Tests on RedLine13
  • Why ACT Moved from BlazeMeter – Highlights from the RedLine13 Customer Advisory Board Meeting

© RedLine13, LLC | Privacy Policy | Contract
Contact Us: info@redline13.com