Changed
View All Tags
As announced on 19th April 2023, the GET /20190206/groups/{group_id} route now returns a 404 HTTP status code if the group_id provided has the status of DELETED or does not exist.
Previously, the archived record would be returned for a deleted group and "Groups": [] would be returned if the group did not exist.
As announced on 6th April 2023, the following changes were made to the GET /20190206/users API route:
This route no longer returns API tokens. The GET /20190206/api-tokens route should be used instead
This route no longer returns DELETED users by default. The previous behavior was to return all users regardless of their status. To get a list of deleted users, you will need to explicitly request it with the status_filter query string, e.g. /users?status_filter=DELETED
The GET /20190206/users/{user_id} route now returns a 404 HTTP status code if the user_id provided has the status of DELETED. Previously, this would return the archived record
The Rule*** S3 enforces object encryptionhas been renamed to *** ***Ensure all S3 buckets employ server-side encryption-at-rest, ***in the S3 Best Practices and Organization bundles. This change helps to align the rule name across different bundles making it easier for customers to search for this rule across bundles.
It's important to note that the name of the rule has not been changed in the CIS Benchmark bundle to align with the standard's specification.
Changes have been applied to Stax-managed AWS Organizational Units in accordance with Release 1 from the published release plan. This was initially announced on 4 April 2023.
Stax manages AWS Organizations in alignment with established best practices. As a result, Stax-managed AWS Organizations will be uplifted to adhere to the organizational structure recommended in the AWS Security Reference Architecture and the Organizing Your AWS Environment Using Multiple Accounts whitepaper. In addition to this, new functionality will be introduced to allow tenancies to better utilize Organizational Units (OUs) and service control policies (SCPs).
These changes will be released over the next 8 weeks. For a detailed outline of these changes, see the release plan here.
The Stax console now features a redesigned navigation interface. This new interface is designed to bring the most used features of Stax to the front, so you're able to access them easily.
For a detailed breakdown of the changes, see the docs.
On 21 March 2023, Stax will be releasing a change to the following rule to align with AWS definitions of public and private. Snapshots shared with specific AWS account IDs will no longer be marked as "public". This only affected the evaluation of public EBS snapshots, and may impact the compliance score of these rules.
| Bundle Name | Rule |
|---|---|
| Public Exposure Bundle v1.0.0 | EBS Snapshots are publicly exposed |
On 28 February 2023 at 0200 UTC (Tuesday, 28 February 1300 AEDT), Stax will update lifecycle configuration to expire non-current S3 object versions on the following S3 buckets in logging foundation account:
stax-config-<org-uuid>
stax-config-accesslogs-<org-uuid>
In each case above, the <org-uuid> placeholder is replaced by the UUID representing your Stax tenancy/AWS organization within Stax.
These S3 buckets are created and managed by Stax, and the usage of them is defined in the docs.
As announced on 18th of January, the Fetch Account Types API now excludes closed accounts from the response.
For more information, review the API documentation for your region: Stax API Documentation and Endpoints
As announced on 19 January 2023, Stax has introduced resource locking for all account operations. Instead of allowing multiple simultaneous operations on a single account and potentially causing conflict, Stax will return a 409 Conflictresponse. Read more