An update has been applied to Stax's Compliance module to improve performance and reliability.
The update implements stability updates to the underlying software and lays the foundation for upcoming feature releases.
No functional changes have been introduced. Should you experience any issues, please raise a support case.
You can now use Stax to visualize the Savings Plans purchased by your organization. The Savings Plans tab in the Cost module allows you to view a summary of all Savings Plans and visualize details about them. Read more.
This feature will be released to all Stax customers over the following weeks.
Update (July 18, 2022): This feature has been released to all Stax customers.
Additional interface VPC endpoints are now available in Networking Hubs:
Amazon FSx
Amazon SES
AWS Backup
AWS Database Migration Service
Dark mode functionality has been removed from the Stax console.
For users wishing to view Stax in a dark color scheme, consider using a browser plugin such as DarkReader. Note that Stax is unable to provide support for these plugins.
Attachments can now be added to support case comments. Previously, attachments could only be added when creating a case. Read more.
AWS accounts can now be closed using the Stax Console. Read more.
AWS accounts can now be closed using the Stax API. This functionality will be available in the Stax Console in the future. Read more.
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.
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) |
|
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.