Skip to main content

User login events are now shown in enhanced activity feed

Stax
Stax
Stax Team

User login events are now shown in the Stax activity feed in the organization dashboard, allowing some users to view user login activity on a more granular level using query filters.

As part of this change, the logins panel has also been removed. Additionally, login token refresh events and login via API token events will no longer be recorded.

User login events are only visible to admin and operations users in Stax-managed organizations.

Stax user details now include last login time

Stax
Stax
Stax Team

Stax now shows the last login time for users for the following Stax API endpoints:

  • Fetch Stax Users and Federated Users
  • Fetch Current User
  • Fetch Stax User or Federated User
  • Fetch Stax User or Federated User
  • Delete Stax User

For more information, please refer to the API documentation for your Stax tenancy.

The last login time can also be viewed from the Stax console by clicking on a user in the Users table.

All users in a Stax-managed organization may see the last login time for their own user details. However, only users with the Admin or Operations role may see the last login time for other users in the organization as a security measure. Similarly, whether another user has MFA configured or not is now visible to only Admins or Operations users.

Ensure Best Practice Organization Configuration With Recommendations

Stax
Stax
Stax Team

Stax's new Recommendations feature is now available. It provides guidance and suggestions to help ensure your Stax-managed AWS Organization is configured in line with best practices.

See Recommendations in the docs for a detailed list of all the recommendations available in Stax. More recommendations will be added in time, but for now you can see guidance of when you have AWS Accounts or Foundation Services configured incorrectly, when basic security controls are not enabled, or when there are simple account hygiene steps to be taken to best configure your AWS Organization using Stax.

This feature is available to administrators of all Stax tenancies. To get started, log in to Stax and review the Recommendations pane on the Organization page.

Additional Guardrail to block creation of account-level AWS IAM Identity Center instances

Stax
Stax
Stax Team

A new Guardrail has been added under the AWS IAM Identity Center header titled Block creation of account-level instances for IAM Identity Center.

This Guardrail will prevent member AWS accounts for creating any account-level instances of IAM Identity Center, ensuring that only a centrally managed IAM Identity Centre exists within the AWS management account.

To enable this visit the configurable service page Configurable Guardrails.

Stax Python SDK v1.4.0 released

Stax
Stax
Stax Team

Version 1.4.0 of the Stax Python SDK has been released, which resolves some dependency issues relating to the use of the SDK.

Changes in this version include:

  • Unpin underlying dependencies, allowing users to use the SDK out of the box without needing to explicitly pin other dependencies for compatibility.
  • Python version classifiers have also been updated in the Python Package Index. Python 3.9 is now the new minimum version supported by the Stax Python SDK.
  • SDK operations are now derived from a new endpoint in the Stax API. The previous endpoint will continue to exist for now, but it may be retired in the future. Stax recommends using the newest version of the Stax Python SDK to minimise disruption.
    • Due to the above change, the teams.ReadApiTokens operation may take the optional access_key keyword argument (previously named AccessKey).

For more details about the Stax Python SDK, see the repository on GitHub.