AWS security-ir documentation change
Summary
Clarified billing cycle details and removed redundant cancellation timing information
Security assessment
The changes only update billing cycle explanations without modifying security controls or addressing vulnerabilities. No security-related content was added or modified beyond operational details.
Diff
diff --git a/security-ir/latest/userguide/cancel-membership.md b/security-ir/latest/userguide/cancel-membership.md index b1ebfdbe9..9b2a02a1f 100644 --- a//security-ir/latest/userguide/cancel-membership.md +++ b//security-ir/latest/userguide/cancel-membership.md @@ -11 +11,14 @@ A role having the CancelMembership permission for AWS Security Incident Response -Once a membership has been canceled, you will be unable to view historic case data. Cancellations occur at the end of the billing cycle. If you cancel during the month, your membership will be available until the end of the month. Any resources or investigations that are `Active` or `ready to close` will be terminated upon final membership cancellation at the end of the billing cycle. +Once a membership has been canceled, you will be unable to view historic case data. If you cancel during the month, your membership will be available until the end of the month. Any resources or investigations that are `Active` or `ready to close` will be terminated upon final membership cancellation at the end of the billing cycle. + +###### Important + +AWS Security Incident Response does not follow standard anniversary billing cycle that happens every month. Service billing runs month to month. Some examples: + + * Dec 29, Jan 29 + + * Jan 29, Feb 26 (Non leap year) + + * Feb 26, March 29 + + +