134 posts tagged with "Added"

We're always working to improve Stax to make it more useful for our customers. Today, two new features have been released for Networks in the Stax Console, with the aim of making networking features more accessible.

View VPC Config Items For Each VPC​

The VPCs page now shows which items have been configured for all your VPCs at a glance. Without inspecting each VPC individually, you can now see when the following VPC Config items are enabled:

• Internet Gateway (IGW)

• NAT Gateway (NGW)

• Virtual Private Gateway (VPGW)

• CloudWatch VPC Flow Logs (CFL)

The full name of VPC Config item can be viewed by hovering your mouse cursor over the label.

Enable and Disable CloudWatch VPC Flow Logs on Stax VPCs​

When you create or edit a Networking Hub or VPC using [Stax Networks]((/hc/en-us/articles/4452164778383), you can now choose to enable CloudWatch Logs for VPC Flow Logs in the Stax Console.

When you enable this feature, Stax will automatically save your VPC's flow logs to CloudWatch Log Groups. These logs reside in the same account as your VPC or Transit VPC, making them easy to access when working with the VPC in question.

We'd love to hear what you think of these new features. If you have any questions about these new features, please raise a support case with your thoughts.

Stax has added a new Stax Workload default parameter, StaxAwsOrgId, to allow access to your AWS Organization ID when deploying Stax Workloads.

Use this new parameter to easily access your AWS Organization ID value to allow Organization-wide IAM permissions.

For more information on using AWS Organizational IAM permissions, see this blog post from AWS.

Example:​

The following example grants s3:GetObject on a S3 bucket access to all accounts in your AWS Organization. ```yaml AWSTemplateFormatVersion: "2010-09-09" Parameters: StaxAwsOrgId: Type: "String" Resources: S3Bucket: Type: "AWS::S3::Bucket" Properties: BucketName: "my-s3-bucket" S3BucketPolicy: Type: "AWS::S3::BucketPolicy" Properties: Bucket: !Ref S3Bucket PolicyDocument: Statement: - Action: - "s3:GetObject" Effect: Allow Resource: Fn::Join: - "" - - "arn:aws:s3:::" - !Ref S3Bucket - /Principal: "" Condition: StringEquals: aws:PrincipalOrgID: - !Ref StaxAwsOrgId

Stax has added new functionality to the Data page which allows you to group your costs.

With this new functionality, you can quickly and easily drill into the different areas of your AWS spend. Group your costs by pre-configured views, AWS accounts, tags values, or any other field on the Data page.

Multiple groups can be applied. Some scenarios of this which we have found helpful include:

• Grouping by account and then by service for a quick breakdown of the how we are using AWS

• Filtering to RDS and grouping by ARN to view the costs of our specific databases

• Grouping by kind to show the breakdown between AWS credits, saving plan charges, and our usage

Stax has made changes to the Stax Workloads API to make it easier to find Workloads you have deployed into your Stax-managed AWS accounts. These filters are available in the API and the SDK.

The new filters available are:

| Filter Name | Description | | --- | --- | | account_names | Comma-delimited list of Stax Account Names. Returns all Workloads deployed to these Accounts Names. | | account_types | Comma-delimited list of Stax Account Types. Returns all Workloads deployed to these Account Types. | | account_ids | Comma-delimited list of Stax Account IDs. Returns all Workloads deployed to these Account IDs. | | catalogue_names | Comma-delimited list of Stax Workload Catalogue Names. Returns all Workloads deployed with these Workload Catalogue Names. | | catalogue_ids | Comma-delimited list of Stax Workload Catalogue IDs. Returns all Workloads deployed with these Catalogue IDs. | | catalogue_version | Only return Workloads launched from this Stax Workload Catalogue Version (eg. 1.0.0). Requires catalogue_ids to also be provided. |

Examples​

Example 1: Return all Stax Workloads deployed to accounts of type 'billing'​

GET https://api.au1.staxapp.cloud/20190206/workloads?account_types=billing

Example 2: Return all Stax Workloads with a specific Catalog ID and Version​

GET https://api.au1.staxapp.cloud/20190206/workloads?catalogue_ids=b5e1c1a5-ee96-4ea3-8343-8704f5f67596&catalogue_version=2.0.1

Stax has updated the Global Filters drop-down to include data that you are needing access to every day or every week. With this change, you will be able to quickly scan through the list of Views and Segments that you use the most and quickly change between them. By adding this functionality, we've removed a few unnecessary clicks each and every time you want to change the data that you are looking at.

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:

• Atom: https://stax.io/changelog/atom.xml

• RSS: https://stax.io/changelog/rss.xml

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.

What does this mean for me?​

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.

For more details about Stax Events, check out the docs.