104 posts tagged with "Changed"

When the UserCreateEvent, UserUpdateEvent, and UserDeleteEvent events occur, Stax Events now includes the user's status in the userStatus property.

See the Security Events Schema documentation for this property's expected values.

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

• Fixed an issue where the Workloads API would accept a Catalog Item Version from a different Catalog Item resulting in the Workload being created/updated with a Version from an incorrect Catalog. If an invalid Catalog Item Version is used, the API will now return a 400 "Bad Request" response, along with an error payload detailing the 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.

On the Data page, the new Marketplace Product property can be used to filter and group records by whether or not they are AWS Marketplace purchases. This is particularly useful when comparing AWS consumption in Stax to that which appears on your AWS invoice, and when considering chargeback/showback models internally. This information was previously only available when exporting data from the Data page using the Export Data button. Read more.

Additionally, a number of minor improvements have been made to the Data page:

• Common properties such as Kind, Account, Region, etc. have been moved to the top of the property list when configuring filters or groupings

• When grouping data, the Sum of Usage Cost field has been renamed to Total Usage Cost. Sum of Financial Cost has been renamed to Total Financial Cost

• Formatting of negative numbers has been improved

The Stax Accounts API has been uplifted to expose the AWS account Canonical user ID.

This change extends the Stax Accounts API to display the AwsAccountCanonicalUserId.

Stax now supports using /31 CIDR blocks when using Stax to create virtual interfaces for use with for AWS Direct Connect.

Previously, only CIDR blocks of size /30 or larger could be used for virtual interfaces.

To make use of this change, enter a CIDR block of size /31 when creating a virtual interface.

Stax Permission Sets now supports increased limits for Assignments. The maximum number of Assignments for a Permission Set is now 50. Previously this limit was 10.

An assignment defines who can utilize the Permission Set and where. This increase enables you to assign access in a more granular fashion to suit your requirements.

To get started, see Permission Sets in the docs.

An update has been applied to Stax Workloads:

• Fixed enforcement of the maxmimum number of resources (AWS CloudFormation templates) allowed. Previously the limit was not properly enforced.

• The resource limit has been revised to 10 based on customer usage patterns and performance evaluation. See Create a workload manifest for more.

• Improved Workloads resilience to network connectivity issues. Workloads will now re-attempt deployment tasks for up to 20 minutes in situations where network connectivity is impaired.

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 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.