102 posts tagged with "Changed"

Version 1.4.3 of stax2aws has been released. See how to upgrade stax2aws.

Changes:

• add --open-browser command line option that automatically opens a client browser with the token code populated

Version 1.4.2 of stax2aws has been released. See how to upgrade stax2aws.

Changes:

• add supported environment variables to command help

• validate the session duration --session-duration maximum value

Stax API endpoint Fetch All Tasks by Status has been deprecated and will be removed from stax-au1, stax-us1 and stax-eu1 on Sunday 14th August at 0200 UTC (Monday 15th August at 1200 AEST).

In addition, a change is being made to the API endpoint Fetch Status of task in stax-au1, stax-us1 and stax-eu1 such that any tasks created on or after Sunday 14th August at 0200 UTC (Monday 15th August at 1200 AEST) will have a 30 day expiry. Any tasks older than 30 days will be removed from the system, responding with a 404 NOT FOUND status.

These changes are being made to improve the way Stax manages tasks.

If you have any concerns, please raise a support case.

An update has been applied to Stax's Compliance module to improve performance and reliability.

The update implements stability updates to the underlying software and lays the foundation for upcoming feature releases.

No functional changes have been introduced. Should you experience any issues, please raise a support case.

Stax has changed how Rules relating to S3 buckets being publicly open are evaluated by including the FULL_CONTROL**is not granted to groupsAllUsers**orAllAuthenticatedUsers check.

If you observe buckets that were previously compliant now showing as non-compliant, it is likely due to the stricter requirement for the bucket to meet the additional control described above. For more information and remediation, visit S3 Buckets shouldn't be Publicly Open.

A number of Rule names have been updated to improve usability and clarity. This change applies to the following Rule Bundles:

• APRA, version 1.0

• EC2 Best Practice, version 1.0

• IAM Best Practice, version 1.0

• RDS Best Practice, version 1.0

• SNS Best Practice, versions 1.0 and 1.1

• SQS Best Practice, versions 1.0 and 1.1

• S3 Best Practice, versions 1.0 and 1.1

• Stax Foundation Compliance, version 1.0

In addition to these changes, Stax has added more detail to Rule descriptions, across all Rule Bundles, to provide a more detailed understanding of each Rule's intent and evaluation. These changes do not impact how Rules are evaluated.

If you have any questions regarding this change, please reach out to your Customer Success Manager or raise a support case with your inquiry.

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, as well as some visual updates to various screens. 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.

To ensure you receive notice of upcoming changes to Stax, make sure you're subscribed to the status page.

Managing Views in Stax is now simpler with improvements released today. A Manage Segments button has been added to simplify adding, editing, and deleting a View's segments. For multi-dimensional Views, the interface has been simplified to rename Dimensions to Columns and Conditions to Rows. This makes it easier to understand your multi-dimensional Views and how they will be segmented.

Version 1.2.0 of the Python SDK has been released.

This change sets the default logging level from DEBUG to INFO. It also removes the configuration of loggers that were out of scope of this SDK, such as boto3, botocore, nose and urllib3. Previously these loggers were being configured to level WARNING. Users of the SDK should check and ensure the logging of these libraries is configured to their desired level.

See Stax Python SDK for more details.

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

To get started, see Permission Sets in the docs.