Added
View All Tags
If a changelog is published in the forest, and nobody sees it, did it really happen?
We want you to know about great new Stax features as soon as they're available. Stax has today introduced an RSS/Atom feed for changelog entries, so you can subscribe to receive them in whichever fashion suits your needs best.
You can subscribe to the feeds using the following URLs:
When you create a VPC using [Stax Networks]((/hc/en-us/articles/4452164778383), VPC Flow Logs are stored in an S3 bucket in your logging account by default. With this new feature, Stax provides you with the capability to direct flow logs to a CloudWatch Log Group, in addition to the S3 bucket. This CloudWatch log group resides in the same account as the VPC, making it easy to access these logs when you need them.
This feature must be enabled using the Stax API, or via the Python SDK. More information on how to set it up can be found in the docs.
Stax has added a new Network Access Control List (NACL) entry for the Private Subnet in your Stax VPCs. This new NACL is configured with Rule #201 and will permit inbound UDP traffic from the ephemeral ports 1024-65535.
Any existing rules with #201 not created by Stax will need to be removed to ensure the addition is successful. To ensure that this is applied to your Stax VPCs you will need to trigger an update of your Stax VPCs. You can trigger an update by either changing the configuration of, or modifying the tags associated with your VPC.
If you have any questions regarding this change, please raise a support case with your enquiry.
You can now retrieve AWS accounts from the Stax API based on their name with the new account_names filter. The filter allows you to provide a comma-delimited list of account names for retrieval.
For more details about the Stax API and the new account names filter, check out the Fetch Accounts route in your local API's docs.
You can now stay informed about more events occurring within your environment. Stax Events has been enhanced to include 8 new event types.
| Event Name | Details |
|---|---|
| PolicyCreateEvent | Stax Policy created |
| PolicyUpdateEvent | Stax Policy updated |
| PolicyDeleteEvent | Stax Policy deleted |
| PolicyAttachToOrganizationEvent | Stax Policy attached to Stax Organization |
| PolicyDetachFromOrganizationEvent | Stax Policy detached from Stax Organization |
| ApiTokenCreateEvent | Stax API token created |
| ApiTokenUpdateEvent | Stax API token updated |
| ApiTokenDeleteEvent | Stax API token deleted |
For more details about Stax Events, check out the docs.
You can now use Stax to provision your Direct Connect resources and manage the associations of your Stax Networks to a Direct Connect connection.
Stax Networks supports Hosted and Dedicated Direct Connect connections. It enables you to create Private or Transit virtual interfaces depending on your network requirements.
You can create a Transit virtual interface to enable Direct Connect connectivity to your entire Stax Networking Hub or a Private virtual interface to connect individual VPCs.
For more details about Stax Networks and Direct Connect, check out the docs.
You can now stay informed about more events occurring within your environment. Stax Events has been enhanced to include 5 new event types. These events inform you about changes to Accounts and Account Types within Stax.
| Event Name | Details | | ------------------------ | ------------------------- | | AccountCreateEvent | AWS account created | | AccountUpdateEvent | AWS account updated | | AccountTypeCreateEvent | Stax account type created | | AccountTypeUpdateEvent | Stax account type updated | | AccountTypeDeleteEvent | Stax account type deleted |
For more details about Stax Events, check out the docs.
You can now stay informed about more events occurring within your environment. Stax Events has been enhanced to include 10 new event types. These events inform you about changes to Users and Groups within Stax.
| Event Name | Details | --- | --- | UserCreateEvent | Stax user created | UserUpdateEvent | Stax user updated | UserDeleteEvent | Stax user deleted | UserPasswordResetEvent | Password reset email sent to Stax user | UserEmailVerificationEvent | Email address verification email sent to Stax user | GroupCreateEvent | Stax group created | GroupUpdateEvent | Stax group updated | GroupDeleteEvent | Stax group deleted | GroupAddMemberEvent | Stax user added to Stax group | GroupRemoveMemberEvent | Stax user removed from Stax group
For more details about Stax Events, check out the docs.
To further ensure the security of your AWS accounts Stax will begin forwarding CloudTrail events for Stax resources within your AWS accounts to Stax infrastructure.
In a future release of Stax, these events will be used to pre-emptively raise tickets for the Stax team to action.
Added: New CloudWatch Alarms based on CloudWatch Metrics for the CloudTrail CloudWatch Log Group within each AWS account
Added: New Stax role to perform FilterLog on the CloudTrail CloudWatch Log Group within each AWS account
Added: New SNS Topic and Lambda Function to forward these events to Stax infrastructure within the foundation Logging AWS account
If you have any questions regarding this change, please raise a support case with your enquiry.
To improve the user experience when creating Stax Account Types, two improvements have been introduced.
Added: Reuse of old Account Type names. Previously, Stax Account Type names could not be reused after an Account Type is deleted. This behavior has been changed to permit name reuse.
Fixed: Improved error handling for Account Type creation. In the event that an attempt was made to create an Account Type with the same name as an existing Account Type, the operation would fail silently with no error. An error will now be displayed.