← Back to blog

AWS Penetration Testing Policy: What You Can Test and When to Ask

November 17, 2026
AWS Penetration Testing Policy: What You Can Test and When to Ask

You do not need AWS's approval to penetration test the permitted services in your own AWS account. You do need approval for a short list of activities, and some activities are banned outright. The line is drawn by what you test and how, not by who carries out the test. If your scope is your own workloads, with no denial-of-service, no simulated phishing and no covert red-team exercise, a CREST-accredited tester can usually start as soon as the scope is agreed. That matters if the test is urgent: no AWS ticket sits in the critical path.

This guide explains the policy in plain terms, shows where startups, schools and charities most often trip over it, and sets out what to agree before a tester touches your environment.

Solusec
solusec.co.uk
Test Your AWS Environment With Confidence
Solusec’s CREST-accredited experts provide penetration testing and clear, actionable findings to help strengthen your security posture.
Get a Pentest Quote

Key Takeaways

  • AWS allows testing of your own resources on permitted services without prior approval, including EC2, RDS, Lambda, CloudFront and Elastic Load Balancers.
  • DoS and DDoS tests, flooding, DNS zone walking, S3 bucket takeover and subdomain takeover are prohibited. Command-and-control, red team, simulated phishing and malware tests need a Simulated Events form.
  • Testing AWS's own infrastructure, or anything outside your account, is never allowed.
  • Your written scope matters more than the AWS policy: it should name accounts, services, IP ranges, test windows and a contact who can stop the test.
  • A pen test of your AWS estate, done properly, covers configuration and identity as well as the servers and applications running on it.

Table of Contents

What the AWS policy actually says

AWS publishes one penetration testing policy page. Its core rule is simple: customers may run security assessments or penetration tests against, or from, resources in their own account for a list of permitted services, without asking AWS first.

AWS's own knowledge centre guidance adds the limit that matters: assessments of AWS infrastructure outside your account, or of the AWS services themselves, are not allowed. If you find a security issue in an AWS service during a test, AWS asks you to report it to aws-security@amazon.com straight away.

In plain terms, you are the tenant and you may test your own flat. You may not test the building, or the neighbours' flats.

Why the policy is shaped this way

AWS is a shared platform. Your virtual servers sit on hardware and networks that other customers also use, which is why a test that could degrade shared capacity is restricted. If tenant separation on a shared platform interests you, this overview of multi-tenancy architecture, isolation models and risks explains why one tenant's activity must never reach another's.

Which services you can test without approval

The AWS policy lists the services where no approval is needed. At the time of writing they include:

  • Amazon EC2 instances, NAT Gateways and Elastic Load Balancers
  • Amazon RDS and Amazon Aurora
  • Amazon CloudFront and AWS WAF
  • Amazon API Gateways, AppSync, Lambda and Lambda Edge
  • Lightsail, Elastic Beanstalk, ECS and Fargate
  • Amazon OpenSearch Service, FSx, Transit Gateway, Bedrock AgentCore and Global Accelerator

The list has grown over the years and AWS can change it, so always check the current policy page before signing a scope. Do not rely on a blog post, including this one, for the exact list on the day of your test.

AWS also lets you run your testing tools from AWS IP space or from another cloud provider. Two exceptions apply: API Gateway and Bedrock AgentCore are prohibited for outbound testing, and command-and-control testing needs prior approval.

Services not on the list

If part of your estate uses a service that is not listed, you do not just go ahead. AWS's best-practice guidance says to contact your AWS account team, who work with the service team and AWS Trust & Safety. If you have no account team, you submit the Simulated Events form. The same guidance warns against routing scanning traffic from Bedrock AgentCore through a NAT gateway as a workaround.

The UK Ministry of Justice gives a useful real-world example. Its guidance for IT health checks on its Cloud Platform says teams should coordinate with the platform team so that AWS is notified about services outside the permitted list, such as ElastiCache or ECR. That is the pattern to copy: find the unlisted services at scoping stage, not on test day.

What is prohibited and what needs a form

There are three buckets, and it helps to keep them apart.

BucketExamplesWhat you do
Allowed without approvalTesting your own EC2, RDS, Lambda, CloudFront and other permitted servicesAgree scope with your tester and proceed
Needs a Simulated Events formCommand-and-control (C2), red, blue and purple team tests, iPerf, simulated phishing, malware testingSubmit the form and keep the approval reference
ProhibitedDNS zone walking, DNS hijacking and pharming via Route 53, DoS and DDoS, flooding, S3 bucket takeover, subdomain takeoverDo not test; use separate AWS policies where they exist

The prohibited and approval-required activities come from the AWS policy page. DDoS simulation and network stress testing are governed by their own AWS policies rather than the standard pen test rule.

Traffic limits on EC2

Even permitted testing has guardrails. The EC2 policy forbids stress or load traffic above 1 Gbps or 1 Gpps in aggregate for more than a minute, traffic that looks abusive, and traffic that could affect other customers, as summarised in the Ministry of Justice guidance. A normal vulnerability-focused pen test sits well inside these limits. A careless automated scan against a small instance can still cause trouble, which is why rate limits belong in your scope document.

When you do need to ask AWS

For network stress tests that exceed the EC2 policy limits, AWS says to submit a Simulated Event request at least 14 business days before testing, with a full plan covering risks and expected outcomes, according to its knowledge centre. For other simulated events, the form needs a full description, details, risks and desired outcomes.

AWS testing approval routes and lead time

For C2 testing, the form is submitted through the AWS Support Center console. It routes to AWS Trust & Safety, and AWS's best-practice article says to keep the approval reference with your authorisation records.

The practical distinction in that article is whether the exercise mimics an unannounced adversary. Testing your own environment with the knowledge of your team needs no pre-approval for permitted services. A covert red-team exercise needs coordination with AWS so that your activity is not treated as real abuse.

Does the policy slow down an urgent test?

For most small organisations, no. The common request is a test of a web application, an API, or the servers and load balancers behind them. All of those sit in permitted services, so there is no waiting period on AWS's side.

Delays come from elsewhere:

  • Unclear scope. Nobody can say which AWS accounts, regions and domains are in or out.
  • Unlisted services. A managed cache or container registry turns up late and needs a conversation with AWS.
  • Third-party ownership. Part of the application is run by a supplier, and you cannot authorise testing of it.
  • The wrong test type. Someone asks for a simulated phishing campaign or a red-team exercise, which does need a form.

If you need a CREST penetration test quickly, settle these four points first. A tester can then work from a clear written scope rather than a back-and-forth by email.

Scoping an AWS test: what to agree before it starts

The AWS policy tells you what AWS permits. It does not tell you what is sensible or lawful for your organisation. Your tester needs written authority from whoever owns the systems, and the scope should be precise.

  1. Accounts and regions. List the AWS account IDs and regions in scope. Many startups have a forgotten second account created for an experiment.
  2. Services. Name each service in use and check it against the permitted list. Flag anything unlisted early.
  3. Targets. Give domains, IP ranges, application URLs and API endpoints. Exclude anything you do not own.
  4. Test type. State whether the test is external, internal to your virtual network, application-level, configuration review, or a combination. If you want a simulated phishing or a red-team element, say so now.
  5. Windows and rate limits. Agree when testing runs and the maximum request rate, especially for small instances that could be knocked over by aggressive scanning.
  6. Stop contact. Name a person who can halt the test and a person who can restore a service.
  7. Third parties. Note any managed service or supplier component that you cannot authorise.

The Ministry of Justice guidance makes a related point worth borrowing: scope the web application and the cloud configuration as code, and avoid overlapping with the platform team's own responsibilities, so two teams are not testing the same thing without knowing.

What a good AWS test looks at

The AWS policy is about permission. A useful test goes further than running a scanner against public IP addresses:

  • Internet-facing servers, load balancers and web applications for exploitable flaws
  • Identity and access management: over-broad roles, access keys left in code, and paths from a low-privilege user to an administrator
  • Storage permissions and public exposure of data
  • Network segmentation between environments
  • Secrets handling in serverless functions and containers

Accident, not attack, is behind many cloud exposures: a storage bucket made public, a role with wildcard permissions, a key committed to a repository. A test that looks at configuration alongside the running services catches those.

Who this matters to

Startups. Investors and enterprise customers increasingly ask for a recent penetration test report. Your AWS estate is likely the whole product, so scope it as a whole and keep a record of authorisation.

Schools, colleges and universities. If you run websites, portals or learning platforms on AWS, the same policy applies. Include any supplier-hosted components in your scope notes, because you cannot authorise testing of systems a supplier owns.

Charities. Donation platforms and case-management systems often sit on cloud hosting. Test the parts you control and ask suppliers what testing they have done on theirs.

Organisations working toward certification. A pen test is separate from Cyber Essentials, which is a certification assessment of your baseline controls. If a customer asks for both, the two can be planned together.

How we approach cloud testing at Solusec

We are a CREST-accredited provider, and you deal directly with the testers and assessors who do the work, not a sales team. Our cloud security assessment for AWS and Azure is the starting point for an AWS estate. For the internet-facing side, we also run infrastructure and network penetration testing and web application and API testing. SaaS companies can see how this applies to them on our page for SaaS providers.

If you want more detail on the AWS-specific rules and a checklist written for UK small businesses, our AWS penetration testing guide goes further. Teams on other platforms can read our guides to Google Cloud penetration testing and Azure penetration testing.

Fixed-price options and certification

If your AWS estate is small and your need is clear, a fixed-price test can be the quickest route. Our published prices are £3,000 for an external IP penetration test and £2,500 for a CMS website penetration test, both one-off fees. Larger or more complex cloud environments are scoped individually, and our penetration testing page shows how to start.

If a customer or funder wants Cyber Essentials fast, certification is £320 to £600 one-off, and an urgent turnaround is available for a further £100. A gap analysis is £300. Details are on our Cyber Essentials page, and Cyber Essentials Plus has its own page.

Solusec

If you are choosing a provider, our guide to how to choose a penetration testing provider lists the questions worth asking. To talk through an AWS scope, start from solusec.co.uk.

A note for UK public-sector and regulated work

If your work touches government or critical national infrastructure, a different scheme applies. CREST describes the NCSC CHECK scheme as a UK Government programme under which the NCSC approves providers to test public-sector and CNI systems. Team leaders need a UK Cyber Security Council Professional Title at Principal level, and team members at Practitioner level.

The NCSC's Assured CHECK Scheme Standard v1.1 from November 2024 also requires companies to agree the test scope with the customer, including threats, technologies, configuration and the types of test. The AWS policy sits alongside these rules and does not replace them.

FAQ

Do I need AWS approval to penetration test my own account?

Not for the permitted services. AWS states that customers can test against or from resources in their own account without prior approval. Approval is needed for simulated events such as C2, red team, simulated phishing and malware testing.

Can a tester test AWS itself?

No. Assessments of AWS infrastructure outside your account, or of AWS services themselves, are not allowed. If a tester finds an issue in an AWS service, it is reported to aws-security@amazon.com.

How long does an AWS approval take?

AWS asks for network stress test requests that exceed EC2 policy limits at least 14 business days before testing. Standard penetration testing of permitted services needs no approval, so there is no AWS waiting time.

Is DDoS testing allowed?

DoS and DDoS tests, including simulated ones, are prohibited under the standard policy. DDoS simulation is governed by AWS's separate DDoS testing policy, so it is not part of an ordinary penetration test scope.

What should I do about services that are not on the permitted list?

Raise them at scoping. Contact your AWS account team, who work with the service team and Trust and Safety, or submit the Simulated Events form if you have no account team.

Sources

This article was created with assistance of AI. We never use AI with your data unless given explicit permission.