Skip to content
  • ZipCode Api
  • Blog
  • About RedLine13
RedLine13
RedLine13
Primary Navigation Menu
Menu
  • Start Testing
  • Demo
  • Pricing
  • JMeter
  • Partners
  • Docs
    • Documentation Home
    • AWS Set Up for load testing
    • AWS Approval for Large Tests
    • PHP, NodeJS, Python Load Tests
    • Scalability
    • Jenkins Plugin Setup
    • Premium Features
    • Knowledge Base

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

  • Cost-Effective Cloud Load Testing
  • Guest Post: Load Testing with Locust and JMeter on RedLine13
  • Executing Gatling Tests with The SBT + Java RedLine13 Plugin
  • Selenium Load Testing: When and How
  • RedLine13 Basic vs Premium Subscription

Related

  • Case Study: iCIMS, The Talent Acquisition Software Experts
  • How to Run a Multi-Region Test – Available in Paid and Free Plans
  • Cost-Effective Cloud Load Testing
  • Guest Post: Load Testing with Locust and JMeter on RedLine13
  • Selenium Load Testing: When and How
  • Selecting Custom OpenJDK version for JMeter
  • Executing Gatling Tests with The SBT + Java RedLine13 Plugin
  • JMeter Alternatives: k6 and Gatling
  • RedLine13 Basic vs Premium Subscription
  • Speak the Lingo using Load Testing Terms

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

Designed using Responsive Brix. Powered by WordPress.