aws-chaos-engineering-framework 2.0.3__py3-none-any.whl
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- aws_chaos_engineering_framework-2.0.3.dist-info/METADATA +245 -0
- aws_chaos_engineering_framework-2.0.3.dist-info/RECORD +7 -0
- aws_chaos_engineering_framework-2.0.3.dist-info/WHEEL +5 -0
- aws_chaos_engineering_framework-2.0.3.dist-info/entry_points.txt +2 -0
- aws_chaos_engineering_framework-2.0.3.dist-info/licenses/LICENSE +201 -0
- aws_chaos_engineering_framework-2.0.3.dist-info/top_level.txt +1 -0
- aws_chaos_framework.py +8818 -0
|
@@ -0,0 +1,245 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: aws-chaos-engineering-framework
|
|
3
|
+
Version: 2.0.3
|
|
4
|
+
Summary: Guarded AWS FIS orchestration and one-file chaos engineering extensions
|
|
5
|
+
Author: Fusion Technology Strategies
|
|
6
|
+
License-Expression: Apache-2.0
|
|
7
|
+
Project-URL: Homepage, https://github.com/fusiontechstrategies/AWS-Chaos-Engineering-Framework
|
|
8
|
+
Project-URL: Issues, https://github.com/fusiontechstrategies/AWS-Chaos-Engineering-Framework/issues
|
|
9
|
+
Project-URL: Security, https://github.com/fusiontechstrategies/AWS-Chaos-Engineering-Framework/security/policy
|
|
10
|
+
Classifier: Development Status :: 4 - Beta
|
|
11
|
+
Classifier: Environment :: Console
|
|
12
|
+
Classifier: Intended Audience :: Developers
|
|
13
|
+
Classifier: Intended Audience :: Information Technology
|
|
14
|
+
Classifier: Operating System :: OS Independent
|
|
15
|
+
Classifier: Programming Language :: Python :: 3
|
|
16
|
+
Classifier: Programming Language :: Python :: 3 :: Only
|
|
17
|
+
Classifier: Programming Language :: Python :: 3.10
|
|
18
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
19
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
20
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
21
|
+
Classifier: Programming Language :: Python :: 3.14
|
|
22
|
+
Classifier: Topic :: System :: Systems Administration
|
|
23
|
+
Classifier: Topic :: Software Development :: Testing
|
|
24
|
+
Requires-Python: <3.15,>=3.10
|
|
25
|
+
Description-Content-Type: text/markdown
|
|
26
|
+
License-File: LICENSE
|
|
27
|
+
Requires-Dist: boto3==1.43.82
|
|
28
|
+
Requires-Dist: botocore==1.43.82
|
|
29
|
+
Requires-Dist: PyYAML==6.0.3
|
|
30
|
+
Dynamic: license-file
|
|
31
|
+
|
|
32
|
+
# AWS Chaos Engineering Framework
|
|
33
|
+
|
|
34
|
+
**Break AWS safely before reality does.**
|
|
35
|
+
|
|
36
|
+
[](https://github.com/fusiontechstrategies/AWS-Chaos-Engineering-Framework/actions/workflows/ci.yml)
|
|
37
|
+
[](https://github.com/fusiontechstrategies/AWS-Chaos-Engineering-Framework/actions/workflows/codeql.yml)
|
|
38
|
+
[](https://www.python.org/)
|
|
39
|
+
[](LICENSE)
|
|
40
|
+
|
|
41
|
+
An enterprise-minded, one-file chaos engineering orchestrator for AWS Fault Injection Service and carefully guarded service extensions. It combines AWS FIS templates, strict blast-radius controls, exact account binding, automatic rollback, emergency stops, and privacy-conscious evidence reports in a tool that remains easy to inspect and deploy.
|
|
42
|
+
|
|
43
|
+
[](docs/images/source/aws-chaos-guarded-experiment.svg)
|
|
44
|
+
|
|
45
|
+
> [!WARNING]
|
|
46
|
+
> This software intentionally disrupts AWS resources. Use it only in isolated, non-production environments that you own or are explicitly authorized to test. Review every plan, alarm, target, permission, and rollback path before live use.
|
|
47
|
+
|
|
48
|
+
## Why this framework exists
|
|
49
|
+
|
|
50
|
+
AWS FIS is the preferred execution engine whenever it provides the required fault. The framework adds a consistent control plane around FIS and extends coverage to service scenarios that FIS does not directly expose.
|
|
51
|
+
|
|
52
|
+
- 60 executable experiment modes across AWS FIS and guarded extensions
|
|
53
|
+
- GovCloud-aware region and ARN validation
|
|
54
|
+
- Plan mode by default, with no AWS mutations
|
|
55
|
+
- Exact account, region, suite, and target binding for live runs
|
|
56
|
+
- CloudWatch alarm gates and continuous runtime safety checks
|
|
57
|
+
- Cooperative emergency stop and automatic recovery for reversible actions
|
|
58
|
+
- Dual approval for irreversible actions and safety bypasses
|
|
59
|
+
- Tag-scoped VPC discovery with exact target allowlisting
|
|
60
|
+
- Local, atomic JSON evidence reports with identifiers redacted by default
|
|
61
|
+
- A single Python application file with no framework or database
|
|
62
|
+
|
|
63
|
+
The framework does not replace AWS FIS. It makes FIS easier to govern and supplies a guarded extension layer for additional AWS services.
|
|
64
|
+
|
|
65
|
+
## Safety model
|
|
66
|
+
|
|
67
|
+
| Guardrail | Enforced behavior |
|
|
68
|
+
| --- | --- |
|
|
69
|
+
| Default mode | Plans and validates. It does not issue mutating AWS requests. |
|
|
70
|
+
| Identity binding | Live mode requires the active account, configured account, region, partition, and caller identity to agree. |
|
|
71
|
+
| Credentials | Temporary credentials are required by default. Long-term credentials need configuration and CLI approval. |
|
|
72
|
+
| Targets | Live extensions require exact allowlisting. Optional VPC discovery includes only resources with required safety tags. |
|
|
73
|
+
| Blast radius | Per-run and per-experiment limits are enforced before execution. |
|
|
74
|
+
| Stop controls | Extension runs require CloudWatch alarms by default. FIS templates require an alarm stop condition by default. |
|
|
75
|
+
| Confirmation | Live execution requires an exact, non-secret token containing the account, region, and suite. |
|
|
76
|
+
| Irreversible actions | Destructive actions require a stronger token plus two independent approvals. |
|
|
77
|
+
| Rollback | Reversible changes capture prior state, track AWS write attempts, and report recovery failures honestly. |
|
|
78
|
+
| Reports | Account, identity, alarm, and resource identifiers are omitted or redacted unless explicitly requested. |
|
|
79
|
+
|
|
80
|
+
Safety checks fail closed. Missing alarms, unresolved targets, mismatched identities, ambiguous target scopes, and unsupported experiment types stop live execution.
|
|
81
|
+
|
|
82
|
+
## Requirements
|
|
83
|
+
|
|
84
|
+
- Python 3.10 through 3.14
|
|
85
|
+
- An AWS identity with only the permissions needed by the selected experiments
|
|
86
|
+
- AWS FIS experiment templates for FIS-managed actions
|
|
87
|
+
- CloudWatch safety alarms for live extension runs
|
|
88
|
+
- A separate, explicitly approved test account or isolated test environment
|
|
89
|
+
|
|
90
|
+
The tool supports standard AWS partitions and both AWS GovCloud regions. CloudFront experiments are rejected when a GovCloud region is configured because CloudFront is not available in GovCloud.
|
|
91
|
+
|
|
92
|
+
## Quick start
|
|
93
|
+
|
|
94
|
+
Clone the repository and create an isolated Python environment:
|
|
95
|
+
|
|
96
|
+
```powershell
|
|
97
|
+
python -m venv .venv
|
|
98
|
+
.\.venv\Scripts\Activate.ps1
|
|
99
|
+
python -m pip install --upgrade pip
|
|
100
|
+
python -m pip install .
|
|
101
|
+
```
|
|
102
|
+
|
|
103
|
+
Create and validate a safe starter configuration:
|
|
104
|
+
|
|
105
|
+
```powershell
|
|
106
|
+
aws-chaos-framework --create-sample-config chaos.yaml
|
|
107
|
+
aws-chaos-framework --validate-config chaos.yaml
|
|
108
|
+
aws-chaos-framework --list-experiments
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
Plan a suite. Plan mode is the default:
|
|
112
|
+
|
|
113
|
+
```powershell
|
|
114
|
+
python .\aws_chaos_framework.py `
|
|
115
|
+
--config .\chaos.yaml `
|
|
116
|
+
--suite tagged_ec2_recovery `
|
|
117
|
+
--vpc-id vpc-0123456789abcdef0 `
|
|
118
|
+
--profile chaos-test
|
|
119
|
+
```
|
|
120
|
+
|
|
121
|
+
The included [example configuration](example-config.yaml) demonstrates tagged EC2 recovery and existing FIS template orchestration. Replace all placeholders before use.
|
|
122
|
+
|
|
123
|
+
## Moving from plan to live execution
|
|
124
|
+
|
|
125
|
+
Live mode is intentionally inconvenient. Complete these steps before enabling it:
|
|
126
|
+
|
|
127
|
+
1. Use an isolated test account or explicitly approved test environment.
|
|
128
|
+
2. Configure the exact account ID and region.
|
|
129
|
+
3. Use a dedicated, least-privilege role with temporary credentials.
|
|
130
|
+
4. Configure required target tags and an exact target allowlist.
|
|
131
|
+
5. Add CloudWatch safety alarms and verify their behavior.
|
|
132
|
+
6. Run and review the plan.
|
|
133
|
+
7. Print the exact confirmation token.
|
|
134
|
+
|
|
135
|
+
```powershell
|
|
136
|
+
python .\aws_chaos_framework.py `
|
|
137
|
+
--config .\chaos.yaml `
|
|
138
|
+
--suite tagged_ec2_recovery `
|
|
139
|
+
--profile chaos-test `
|
|
140
|
+
--show-live-token
|
|
141
|
+
```
|
|
142
|
+
|
|
143
|
+
Then provide that exact token with `--live`:
|
|
144
|
+
|
|
145
|
+
```powershell
|
|
146
|
+
python .\aws_chaos_framework.py `
|
|
147
|
+
--config .\chaos.yaml `
|
|
148
|
+
--suite tagged_ec2_recovery `
|
|
149
|
+
--profile chaos-test `
|
|
150
|
+
--live `
|
|
151
|
+
--confirm "LIVE:000000000000:us-gov-west-1:tagged_ec2_recovery"
|
|
152
|
+
```
|
|
153
|
+
|
|
154
|
+
Irreversible suites require `safety.allow_irreversible: true`, `--allow-irreversible`, and a token beginning with `LIVE-IRREVERSIBLE`. Safety bypasses also require matching approval in both configuration and the CLI.
|
|
155
|
+
|
|
156
|
+
## AWS FIS integration
|
|
157
|
+
|
|
158
|
+
Use `fis_template` to validate, start, monitor, and stop an existing AWS FIS experiment template. Before a live start, the framework checks:
|
|
159
|
+
|
|
160
|
+
- FIS execution-role partition and account ownership
|
|
161
|
+
- CloudWatch alarm stop conditions
|
|
162
|
+
- target selection modes and configured blast-radius limits
|
|
163
|
+
- exact ARN allowlists for explicit resources
|
|
164
|
+
- required tags for dynamically selected resources
|
|
165
|
+
- unbounded `ALL` or `PERCENT` selections
|
|
166
|
+
|
|
167
|
+
FIS remains responsible for its managed actions and recovery behavior. The framework monitors the experiment, applies framework safety checks while it runs, and requests a stop if an emergency condition occurs.
|
|
168
|
+
|
|
169
|
+
Useful AWS references:
|
|
170
|
+
|
|
171
|
+
- [AWS Fault Injection Service](https://aws.amazon.com/fis/)
|
|
172
|
+
- [AWS FIS actions reference](https://docs.aws.amazon.com/fis/latest/userguide/fis-actions-reference.html)
|
|
173
|
+
- [AWS FIS stop conditions](https://docs.aws.amazon.com/fis/latest/userguide/stop-conditions.html)
|
|
174
|
+
- [AWS FIS targets](https://docs.aws.amazon.com/fis/latest/userguide/targets.html)
|
|
175
|
+
- [AWS FIS in GovCloud](https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/govcloud-fis.html)
|
|
176
|
+
|
|
177
|
+
## Experiment catalog
|
|
178
|
+
|
|
179
|
+
The catalog covers AWS FIS plus extensions for EC2, EBS, EFS, VPC, RDS, Lambda, S3, SQS, SNS, Elastic Load Balancing, ECS, Kinesis, OpenSearch, CloudFront, WAF, KMS, IAM, Directory Service, AppStream, ECR, CodeCommit, and SES.
|
|
180
|
+
|
|
181
|
+
Every catalog entry declares its provider, risk, live support, rollback model, and whether FIS is preferred:
|
|
182
|
+
|
|
183
|
+
```powershell
|
|
184
|
+
python .\aws_chaos_framework.py --list-experiments
|
|
185
|
+
```
|
|
186
|
+
|
|
187
|
+
The catalog intentionally includes some gated entries. An action is not live-supported when it cannot provide a real fault, bounded targeting, or an honest recovery contract. Host-level EC2 faults are represented through `fis_template` so that AWS FIS and SSM-managed actions provide the execution semantics.
|
|
188
|
+
|
|
189
|
+
## Evidence and privacy
|
|
190
|
+
|
|
191
|
+
Each suite creates an atomic JSON report in `chaos-reports/` unless another output directory is selected. Reports include mode, framework version, action status, duration, mutation attempts, rollback attempts, and recovery outcomes.
|
|
192
|
+
|
|
193
|
+
By default, reports omit AWS identity and resource identifiers. These fields can be enabled separately:
|
|
194
|
+
|
|
195
|
+
```yaml
|
|
196
|
+
reporting:
|
|
197
|
+
include_identity: false
|
|
198
|
+
include_resource_ids: false
|
|
199
|
+
include_diagnostics: false
|
|
200
|
+
```
|
|
201
|
+
|
|
202
|
+
Reports and logs may still be operationally sensitive. Keep them out of source control and handle them according to your organization's data-classification rules. AWS API activity is recorded by CloudTrail when CloudTrail is configured for the account. The framework's local audit events are not a substitute for CloudTrail.
|
|
203
|
+
|
|
204
|
+
## Testing and release assurance
|
|
205
|
+
|
|
206
|
+
The release gate is fully offline and never contacts an AWS account. Deterministic fake clients exercise every advertised executable mode and fail immediately if plan mode attempts a write. Focused simulations also cover live policy rollback, route restoration and conflict refusal, WAF optimistic locking, IAM self-protection, FIS start guardrails, report no-overwrite behavior, redaction, configuration validation, and Botocore API request shapes.
|
|
207
|
+
|
|
208
|
+
Run the same checks locally:
|
|
209
|
+
|
|
210
|
+
```powershell
|
|
211
|
+
python -m pip install -r requirements-dev.txt
|
|
212
|
+
python -m ruff format --check .
|
|
213
|
+
python -m ruff check .
|
|
214
|
+
python -m pytest -q
|
|
215
|
+
python -m bandit -q -r .\aws_chaos_framework.py
|
|
216
|
+
python -m pip_audit -r .\requirements.txt
|
|
217
|
+
```
|
|
218
|
+
|
|
219
|
+
CI runs the test suite across supported Python versions and validates Python 3.12 on Windows and macOS. The release-candidate job builds normalized wheel and source archives twice, requires byte-identical results, installs each package independently, and preserves the exact six-file candidate as workflow evidence. CodeQL, Semgrep, Trivy, dependency auditing, secret scanning, and Dependabot are configured for the public repository.
|
|
220
|
+
|
|
221
|
+
See [TESTING.md](TESTING.md) for the complete offline gate and [RELEASING.md](RELEASING.md) for the exact asset contract. Tag automation can create only a draft GitHub release and cannot publish to a package registry.
|
|
222
|
+
|
|
223
|
+
## Design principles
|
|
224
|
+
|
|
225
|
+
- FIS first when AWS supplies a managed action
|
|
226
|
+
- No mutation without explicit live intent
|
|
227
|
+
- No target without exact scope
|
|
228
|
+
- No destructive action disguised as reversible
|
|
229
|
+
- No swallowed rollback error
|
|
230
|
+
- No secret or target inventory committed to the repository
|
|
231
|
+
- No claim of success when no resource was affected
|
|
232
|
+
|
|
233
|
+
## Contributing
|
|
234
|
+
|
|
235
|
+
Contributions are welcome. Start with [CONTRIBUTING.md](CONTRIBUTING.md), keep the runtime application in the single `aws_chaos_framework.py` file, and add offline tests for every behavior change. Pull requests must not require access to a real AWS account.
|
|
236
|
+
|
|
237
|
+
Security vulnerabilities should be reported privately as described in [SECURITY.md](SECURITY.md).
|
|
238
|
+
|
|
239
|
+
## License
|
|
240
|
+
|
|
241
|
+
Licensed under the [Apache License 2.0](LICENSE).
|
|
242
|
+
|
|
243
|
+
## Disclaimer
|
|
244
|
+
|
|
245
|
+
This project is community software and is not affiliated with, sponsored by, or endorsed by Amazon Web Services. AWS, AWS GovCloud, and related service names are trademarks of Amazon.com, Inc. or its affiliates. You are responsible for authorization, configuration, cost, availability impact, regulatory obligations, and recovery planning.
|
|
@@ -0,0 +1,7 @@
|
|
|
1
|
+
aws_chaos_engineering_framework-2.0.3.dist-info/METADATA,sha256=3Jh7vBdmq-RgTC48rsJzJFign07VTHxut1Hqs_w5RG4,12913
|
|
2
|
+
aws_chaos_engineering_framework-2.0.3.dist-info/RECORD,,
|
|
3
|
+
aws_chaos_engineering_framework-2.0.3.dist-info/WHEEL,sha256=YVMoNqKzERt-wjUZwJ33xBGAwnFl-4cqbYkTtWa4itE,91
|
|
4
|
+
aws_chaos_engineering_framework-2.0.3.dist-info/entry_points.txt,sha256=qx-UlOxRW-SWipgKfonO9s2-IK77PtQCeKTIUxSI4u0,65
|
|
5
|
+
aws_chaos_engineering_framework-2.0.3.dist-info/licenses/LICENSE,sha256=t3BUw3T7QmUvpjONaVp_1uKX4KFXNZi7igvhDOmca64,11374
|
|
6
|
+
aws_chaos_engineering_framework-2.0.3.dist-info/top_level.txt,sha256=2W4JvZKXJFhMZg5SisMW50MihYgFUMG6BW_YtRLIGbo,20
|
|
7
|
+
aws_chaos_framework.py,sha256=q8KzLCXjZ4Dvb3EmwLdj0pTwcBPMECF5f-_jKXIKNfM,348611
|
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright 2026 AWS Chaos Engineering Framework contributors
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
aws_chaos_framework
|