Changed
View All Tags
Version 1.1.3 of the Python SDK has been released.
This change introduces a bug fix to ensure that credentials don't expire before the SDK has a chance to renew them, and removes some functionality that wasn't being used.
For more details about the Python SDK, check it out on Github.
An update has been applied to Stax Workloads to improve performance and reliability:
Fixed a bug where the deployment tasks where not queued correctly. Workloads will now correctly execute a maximum of 50 deployments concurrently, per Stax organization. Additional deploy requests will be queued and actioned once capacity becomes available.
These changes have been applied automatically by Stax. There is no impact to service expected as a result of this upgrade.
The Notifications page has been redesigned to provide a more intuitive and simple user experience. Notifications are now managed through a tabulated window, with each delivery channel located on a seperate tab.
Stax also now supports sending notifications via Microsoft Teams, in addition to the existing email, webhook, and Slack delivery channels. Simply create an incoming webhook for your Teams channel and select the notifications you'd like to receive. For more information, see the documentation.
AWS has had a Local Zone in Osaka for some time (ap-northeast-3). Recently, this region has been increased in capacity and released to the general public for use.
This region does not yet meet Stax's minimum requirements for a new region. In line with our AWS Region Policy, we have disabled activity in the region for Stax-managed AWS accounts using a Stax Policy. This restriction is in place until such a time as the region does meet Stax's minimum requirements.
If you anticipate this restriction impacting you, or if you have intentions to use this region, please raise a support case.
Stax is enhancing the validation around tags applied to networking resources created using Stax Networks. Stax Networks supports tagging networking resources to allow enhanced flexibility in how you identify resources it creates.
The Stax API will now perform additional validation against tags supplied for your these resources. The validation is designed to help you comply with AWS's guidance for tagging EC2 resources.
The updated API schema for your region (stax-au1, stax-eu1, stax-us1) provides more information.
If you have any questions about how this change may impact you, please raise a support case.
Version 1.1.2 of the Python SDK has been released.
This is an update to lock the dependency openapi-spec-validator to version 0.2.9. This is due to breaking validation changes being introduced in the most recent versions of the dependency.
For more details about the Python SDK, check it out on Github.
The "Security groups should be used actively" rule is available to help organizations manage their use of security groups.
AWS prevents users from deleting the default security groups. To prevent against false positives from being raised because of this, Stax has updated the rule definition. The rule no longer considers default security groups as in-scope, and as such will not cause failures if default security groups are unused.
This change affects the following bundles:
EC2 Best Practices (version 1.0)
APRA (version 1.0)
The custom organization-level rule, if in use
These changes have been applied automatically by Stax. There is no impact to service expected as a result of this update.
If you have any questions about this change and what it means for you, please contact support.
Version 1.3.0 of stax2aws has been released. This update adds a new argument that allows users to specify the ARN of a role to assume.
This is useful when regularly logging in to one or more accounts and roles.
Before you can use this new feature, you must upgrade stax2aws to version 1.3.0 or later.
When using stax2aws, simply add the --role-arn (-r) argument specifying the ARN of the role to assume. stax2aws will then suppress the role selection prompt and automatically assume the specified role.
shell stax2aws login \ -i stax-au1 -o mega-corp -p my-stax2aws-profile \ -r arn:aws:iam::123456789012:role/staxid-readonly-role
stax2aws will update the profile in its configuration to use this role. Future invocations will not require the role ARN to be specified. If you need to change the role ARN to be assumed by a particular profile, simply issue the --role-arn argument again.
The Stax roles Cost & Compliance Admin & Read Only now allow users to request a password reset for their own Stax user account. Users in these roles no longer have to rely on an administrator to reset their password.
For more information on the roles available within Stax, see Accessing Stax.
An update has been applied to Stax Workloads to improve performance and reliability:
Fixed a bug where deleting workloads that were already in a deleted state would briefly block deletion of the associated workload catalogue.
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.