Skip to main content

Fetch All Tasks by Status and 30 Day Task Expiry

Stax
Stax
Stax Team

Stax API endpoint Fetch All Tasks by Status has been deprecated and will be removed from stax-au1, stax-us1 and stax-eu1 on Sunday 14th August at 0200 UTC (Monday 15th August at 1200 AEST).

In addition, a change is being made to the API endpoint Fetch Status of task in stax-au1, stax-us1 and stax-eu1 such that any tasks created on or after Sunday 14th August at 0200 UTC (Monday 15th August at 1200 AEST) will have a 30 day expiry. Any tasks older than 30 days will be removed from the system, responding with a 404 NOT FOUND status.

These changes are being made to improve the way Stax manages tasks.

If you have any concerns, please raise a support case.

Improvements to Stax Compliance

Stax
Stax
Stax Team

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.

Visualize your Savings Plans in Stax

Stax
Stax
Stax Team

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.

Dark mode removed from the Stax Console

Stax
Stax
Stax Team

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.

Stax Workloads Update

Stax
Stax
Stax Team

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
Stax
Stax Team

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 Best Practices, version 1.0 * 1.1
  • Organization
S3 Buckets should not be Publicly Open for Reads
  • S3 Best Practices, version 1.0 * 1.1
  • Organization
S3 Buckets should not be Publicly Open for Reads and Writes
(Previously: S3 Buckets should not be Publicly Open)
  • S3 Best Practices, version 1.0 * 1.1
  • Organization
S3 Buckets should not be Publicly Open for Writes
  • S3 Best Practices, version 1.0 * 1.1
  • Organization
S3 Buckets should not be publicly open for read operations
  • Public Exposure, version 1.0
S3 Buckets should not be publicly open for read and write operations
(Previously: S3 Buckets should not be publicly open)
  • Public Exposure, version 1.0