14 posts tagged with "Removed"

On Thursday 30 January 2025, Stax’s changelog will cease supporting two notification channels you may be making use of: Email subscriptions and Slack notifications.

To continue receiving notifications when Stax releases new changelog entries, consider signing up to the new Changelog RSS/Atom feeds:

RSS: https://support.stax.io/changelog/rss.xml

Atom: https://support.stax.io/changelog/atom.xml

For existing consumers of the RSS and Atom feeds, a redirect will be implemented but you may wish to update to the new URLs now.

Stax has deprecated stax2aws versions 1.4.3 and older. These versions of the Stax Command Line Interface (CLI) utilized a device authorization grant solution which is no longer supported. Stax has removed the obsolete device flow resources from Stax-managed security accounts.

All users are required to upgrade to version 1.5.0 of stax2aws to continue using the Stax CLI.

If you have questions or concerns regarding the changes, please reach out by raising a support case.

As announced on 15 December 2023, the following deprecated Stax API endpoints have been removed from stax-au1, stax-us1, and stax-eu1 and are no longer supported by Stax API/SDK:

**- Fetch IDAM Users **GET /20190206/idam/user

**- Fetch IDAM User ** GET /20190206/idam/user/{org_id}

The following endpoints should be used instead:

-** Fetch Stax Users and Federated Users** GET /20190206/users

• Fetch Stax User and Federated User GET /20190206/users/{user_id}

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

As announced on 7 December 2023, the stax-audit-bus EventBridge rule has been removed from all Stax-managed AWS accounts. Please review our guide for more information.

As per the announcement last week, the "Lambdas must have unique roles" check has been deprecated and removed from the rules catalog.

This rule is only part of the Stax rule catalog, and is not used as part of any compliance or best practice rule bundles.

On December 20, 2022 a new OperationStatus, CREATED, was added to the Tasks API and announced on the changelog.

Due to unanticipated compatibility challenges, this change has now been reverted. While the change may be reintroduced in future, any release will be accompanied by a reasonable notice period to help customers to prepare for the change.

The following OperationStatus values have also been removed to simplify usage, as they are not currently available through the API:

• COMPLETED_WITH_WARNING

• ABORTED

• TIMED_OUT

Review the developer documentation for up-to-date details of the Stax API.

The Explore the cost of your services feature in the Cost module has now been deprecated and removed from the console. Read more.

The Tag Policy feature in the Cost module has now been deprecated and removed from the console. Read more.

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 is always working to ensure the security of the platform and our customers. As a result, from time to time, changes are introduced to remove insecure or outdated technology. Transport Layer Security (TLS) 1.2 is the industry-agreed recommended minimum cryptographic protocol for HTTP traffic. As a result, SSL and TLS versions older than TLS 1.2 are no longer supported by the Stax API.

From 2020-09-11 the Stax API will require all communication to use TLS 1.2. We maintain support of the following cipher suites: Supported SSL/TLS protocols and ciphers for regional, private, and WebSocket API endpoints in API Gateway.

What does this mean for me?​

Ensure any app or integration you've built to use the Stax API supports TLS 1.2. While most applications and programming languages have supported TLS 1.2 for several years, if yours doesn't, you may need to upgrade your application.

If you're using the Stax SDK, you should not need to make any changes. The Stax SDK requires Python 3.6+, which has built in support for TLS 1.2 (as do most modern programming language versions).

If you have any questions regarding this change, please raise a support case with your enquiry.