Attachments can be added to Support case comments
Attachments can now be added to support case comments. Previously, attachments could only be added when creating a case. Read more.
Close AWS accounts using the Stax Console
AWS accounts can now be closed using the Stax Console. Read more.
Close AWS accounts using the Stax API
AWS accounts can now be closed using the Stax API. This functionality will be available in the Stax Console in the future. Read more.
Stax Workloads Update
An update has been applied to Stax Workloads to improve performance and reliability:
- Fixed an issue where a Stax Workloads manifest would fail schema validation when using the ProtectedResources key.
These changes have been applied automatically by Stax. There is no impact to service expected as a result of this update. Should you experience any issues, please raise a support case.
Update to Rules - S3 Buckets Should Not Be Publicly Open
Stax has changed how Rules relating to S3 buckets being publicly open are evaluated by including the FULL_CONTROL**is not granted to groupsAllUsers**orAllAuthenticatedUsers check.
If you observe buckets that were previously compliant now showing as non-compliant, it is likely due to the stricter requirement for the bucket to meet the additional control described above. For more information and remediation, visit S3 Buckets shouldn't be Publicly Open.
| Impacted Rule Name | Impacted Bundles
|
|---|---|
| S3 Buckets should not be Publicly Open for Reads |
|
| S3 Buckets should not be Publicly Open for Reads and Writes (Previously: S3 Buckets should not be Publicly Open) |
|
| S3 Buckets should not be Publicly Open for Writes |
|
| S3 Buckets should not be publicly open for read operations |
|
| S3 Buckets should not be publicly open for read and write operations (Previously: S3 Buckets should not be publicly open) |
|
Changes to Stax Rule Names
A number of Rule names have been updated to improve usability and clarity. This change applies to the following Rule Bundles:
- APRA, version 1.0
- EC2 Best Practice, version 1.0
- IAM Best Practice, version 1.0
- RDS Best Practice, version 1.0
- SNS Best Practice, versions 1.0 and 1.1
- SQS Best Practice, versions 1.0 and 1.1
- S3 Best Practice, versions 1.0 and 1.1
- Stax Foundation Compliance, version 1.0
In addition to these changes, Stax has added more detail to Rule descriptions, across all Rule Bundles, to provide a more detailed understanding of each Rule's intent and evaluation. These changes do not impact how Rules are evaluated.
If you have any questions regarding this change, please reach out to your Customer Success Manager or raise a support case with your inquiry.
Identity Service Updates
An update has been applied to the Stax Identity Service to improve performance and reliability.
The update implements security and stability updates to the underlying software, as well as some visual updates to various screens. No functional changes have been introduced.
These changes have been applied automatically by Stax during the advertised maintenance window. There is no impact to service expected as a result of this upgrade. Should you experience any issues, please raise a support case.
To ensure you receive notice of upcoming changes to Stax, make sure you're subscribed to the status page.
New Rule to check that Lambda Functions are in use
A new Rule has been released to allow organizations to check that all Lambda Functions are in use, defined by a configurable threshold.
To enable this Rule, see Add a Rule from the Catalog.
New Hub Peering functionality for Stax Networks
You can now use Stax to manage peering between your Stax Networking Hub and another Stax Networking Hub, or with a standalone AWS Transit Gateway. Read more.
New Rule to check that Security Hub is enabled in all regions
A new Rule has been released to allow organizations to validate that Security Hub is enabled in all Stax-managed AWS accounts in all regions with active resources.
To enable this Rule, see Add a Rule from the Catalog.