14 posts tagged with "Removed"

A change has been introduced to the Stax Console and API to allow additional control over federated users within the Stax identity service. These users can now be disabled within the Stax API and Console, not only via a federated identity provider.

Additionally, the deprecated concept of Stax root users has been removed from the identity service.

• Changed: Federated users can now be deactivated through the Stax console

• Changed: Federated users can now be deactivated through the Stax API/SDK

• Removed: Root users are no longer included in the response to a GET request for the Stax API's /users endpoint

• Removed: Stax no longer supports filtering on root users

As per AWS best practices, all S3 buckets created by the Stax platform in customer AWS Accounts will have enforced encryption of data in transit using HTTPS (TLS).

This change does not impact buckets created by Stax customers either within the AWS Console/SDK/API, or via the Stax Workloads service.

This change applies to the following legacy S3 buckets in your AWS Accounts:

• juma-cloudtrail-*

• juma-cloudtrail-master-accesslogbucket-*

• juma-cloudtrail-master-jumaaccesslogbucket-*

• juma-jumatrail-*

• juma-config-*

• juma-session-manager-*

The following legacy S3 buckets will be removed in your AWS Accounts:

• stax-billing-*

• stax-billing-accesslogs-*

• juma-billing-*

Please note: The legacy S3 buckets that are removed contain only outdated billing information. These buckets have not been in use since February 2020 and as such no impact is expected by this removal. The best way to access your billing information is with Stax's Cost & Compliance module.

As per AWS best practices, all SNS topics created by the Stax platform in customer AWS Accounts have encryption enabled using KMS. One unused SNS Topic has been removed from accounts.

• Changed: Encrypted stax-assurance-cis-benchmark-EventIngestTopic topic in all accounts

• Changed: Encrypted staxtrail-<org-id> topic in logging account

• Changed: Encrypted cloudtrail-<org-id> topic in logging account

• Changed: Encrypted stax-assurance-event-processor-EventIngestTopic topic in security account

• Removed: stax-config-<org-id> topic in logging account, as it was not used

If you have your own sources publishing messages to these topics, you will need to configure the source with the right permissions to be able to continue publishing to the topic. For more information on this,see publishing to encrypted topics.

The stax:version tag will no longer be applied to CloudFormation stacks within new Workload deployments in Stax. This change has been introduced to improve the speed and reliability of Workload deployments.

Prior to this change, the tag was applied to all CloudFormation stacks deployed as part of a Workload.

Newly deployed Workloads will notice this change immediately. Any running Workload will retain this tag until the next Workload update, at which point it will be automatically removed by Stax.

The stax:version tag did not relate in any way to the version of the Workload deployed, rather it was used for Stax-internal purposes only.