16 posts tagged with "Deprecated"

The Tag Policy feature in the Cost & Compliance module will be deprecated on 1 ** December 2022. **To ensure you are not impacted, follow this guide to prepare for the change.

The PhoneNumber and Tags attributes have been deprecated from the User APIs.

These attributes will be removed from the API on 1 ** December 2022** and from this date will be ignored on Create and Update requests, and not returned in GET requests.

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.

Stax has released a new Config Aggregator named stax-assurance-<stax_organization_id> in your security foundation account. It is an organizational aggregator with the intention of deprecating the current multi-account aggregator juma-assurance-<security_aws_account_id>, to simplify the configuration and management. You will find the aggregator in the AWS region according to your Stax Installation region.

For organizations where the security foundation account is not set up as the organization's delegated administrator account for AWS Config (with service principal config.amazonaws.com), this aggregator will not be created.

During the week beginning 29 November 2021, Stax will start the process of removing the aggregator juma-assurance-<security_aws_account_id> from your security foundation account.

Update: The juma-assurance-<security_aws_account_id> aggregator removal work has been completed for all Stax tenancies.

Stax has deprecated its automatic CloudFormation template validation for Workload Catalog items.

When deploying a Workload Manifest file, Stax will validate the structure of the Manifest, ensure that all CloudFormation templates are reachable, and that the CloudFormation templates themselves are valid JSON or YAML. It will no longer query AWS's Validate Template API to validate the CloudFormation template(s) when a manifest is uploaded.

This feature has been deprecated as, in some instances, it prevented deployment of sophisticated Workloads and templates that relied on specific AWS account and region combinations.

The API endpoints affected are:

• Create Workload Catalog Item: stax-au1 stax-us1 stax-eu1

• Update Workload Catalog Item: stax-au1 stax-us1 stax-eu1

Consider leveraging the AWS CLI/API directly when developing CloudFormation templates to ensure their validity.

These changes have been applied automatically by Stax. Should you experience any issues, please raise a support case.

Stax will update its account bootstrap process from July 1, 2021. After this time, the AWS account alias will no longer be generated or modified.

For existing accounts that already have an alias, the alias will remain unchanged.

This does not prevent you from creating an account alias at a later stage.