107 posts tagged with "Changed"

An update has been applied to Stax Workloads to improve performance and reliability:

• Fixed an issue where the Workloads API would accept invalid characters for the Workload name. Workload names will now be correctly validated against the pattern ^[a-zA-Z][-a-zA-Z0-9]*$. If the Workload name is invalid, the API will return a 400 "Bad Request" response, along with an error payload detailing the schema error.

• Fixed an issue where the Workloads API would accept invalid parameter formats. If an invalid parameter format is provided, the API will now return a 400 "Bad Request" response, along with an error payload detailing the schema error.

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.

The Permission Sets page now allows for deletion of Permission Sets.

When no longer required, Permission Sets can be deleted from the Stax Console. Permission Sets can only be deleted when all Permission Set Assignments have been deleted.

For more information, see Permission Sets in the docs.

The Workloads page now shows deployed workloads in a list.

This improves usability and functionality, while allowing up to 100 deployed Workloads to be displayed at a time. Additionally, you can now click on the View AWS CloudFormation Stack button beside each Workload to log into the Workload's AWS account and view the associated CloudFormation stack.

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.