Changed
View All Tags
Version 1.3.1 of stax2aws has been released. This update fixes a bug where stax2aws would report that no roles were available in certain circumstances.
You should upgrade stax2aws to version 1.3.1 or later if you experience this bug.
The Stax Accounts service has been uplifted to improve core operating processes.
This change decreases the time taken to provision new Stax-managed AWS accounts, and improves the reliability of this process. Additionally, the Security Foundation Account now manages Amazon GuardDuty members via AWS Organizations, instead of individually by invitation. This change to the Amazon GuardDuty configuration is in alignment with the latest AWS offerings and recommended best practices.
You don't need to do anything to take advantage of these improvements. Next time you create a new AWS account using the Stax Console, API, or SDK, the upgraded Accounts service will be utilized.
An update has been applied to the Stax Identity Service to improve performance and reliability.
This system update lays the foundation for upcoming feature releases.
These changes have been applied automatically by Stax. There is no impact to service expected as a result of this upgrade. Should you experience any issues, please raise a support case.
An update has been applied to the Stax Identity Service to improve performance and reliability.
This system update lays the foundation for upcoming feature releases.
These changes have been applied automatically by Stax during the advertised maintenance window. There is no impact to service expected as a result of this upgrade. Should you experience any issues, please raise a support case.
Stax has added additional Stax Networks code examples to the Python SDK.
Check out the Python SDK to get started.
Stax has introduced a new Rule for monitoring IAM User API key rotation, regardless of whether the keys are active or inactive.
This is particularly useful for situations where IAM User Keys may be deactivated either temporarily or permanently prior to deletion.
Add this Rule on the Rules page to get started.
An update has been applied to the Stax Identity Service to improve performance and reliability.
The update implements security and stability updates to the underlying software. No functional changes have been introduced.
These changes have been applied automatically by Stax during the advertised maintenance window. There is no impact to service expected as a result of this upgrade. Should you experience any issues, please raise a support case.
Stax has introduced an improved interface to make it easier to filter and group data on the Data page.
The new left-hand panel allows you to explore possible filtering and grouping criteria. Power users can still use the filtering and grouping fields on the Data page to manually enter criteria.
Choose the criteria you want to filter by using the checkboxes, or choose Group to group on it. Click Search at the bottom of the panel to show the changes on the Data page.
Once the data is filtered as desired, you can show and hide columns using the new Show/Hide Columns button at the top left-hand size of the data table.
Stax Cost & Compliance now allows the following values to be set when creating Cost Spike Alerts:
Alert sensitivity
Minumum dollar increase
Cost Spike Alerts can help you keep an eye on those parts of your AWS account that are prone to exceeding their monthly budget, or have unpredictable costs that you need to stay on top of.
For guidance on configuring these alerts, check out the documentation.
We have redesigned the pages in Notifications to provide a clearer view of your personal and organization notifications. It is easier now to browse notifications by Email, Slack, Webhook or Microsoft Teams by selecting the appropiate tab at the top of the page.
We have also redesigned the create workflow. The first step allows you to select the target Segment and notification destination. The second step allows selecting the notifications you wish to receive.