AWS announces Flexible Cost Allocation on AWS Transit Gateway AWS announces general availability of Flexible Cost Allocation on AWS Transit Gateway, enhancing how you can distribute Transit Gateway costs across your organization. Previously, Transit Gateway only used a sender-pay model, where the source attachment account owner was responsible for all data usage related costs. The new Flexible Cost Allocation (FCA) feature provides more versatile cost allocation options through a central metering policy. Using FCA metering policy, you can choose to allocate all of your Transit Gateway data processing and data transfer usage to the source attachment account, the destination attachment account, or the central Transit Gateway account. FCA metering policies can be configured at an attachment-level or individual flow-level granularity. FCA also supports middle-box deployment models enabling you to allocate data processing usage on middle-box appliances such as AWS Network Firewall to the original source or destination attachment owners. This flexibility allows you to implement multiple cost allocation models on a single Transit Gateway, accommodating various chargeback scenarios within your AWS network infrastructure. Flexible Cost Allocation is available in all commercial https://docs.aws.amazon.com/network-manager/latest/cloudwan/what-is-cloudwan.html#cloudwan-available-regions where Transit Gateway is available. You can enable these features using the AWS Management Console, AWS Command Line Interface (CLI) and the AWS Software Development Kit (SDK). There is no additional charge for using FCA on Transit Gateway. For more information, see the Transit Gatewayhttps://docs.aws.amazon.com/vpc/latest/tgw/metering-policy.html

AWS announces Flexible Cost Allocation on AWS Transit Gateway

AWS announces general availability of Flexible Cost Allocation on AWS Transit Gateway, enhancing how you can distribute Transit Gateway costs across your organization.

Previously, Transit Gateway only us...

#AWS #AwsTransitGateway

AWS announces Flexible Cost Allocation on AWS Transit Gateway AWS announces general availability of Flexible Cost Allocation on AWS Transit Gateway, enhancing how you can distribute Transit Gateway costs across your organization. Previously, Transit Gateway only used a sender-pay model, where the source attachment account owner was responsible for all data usage related costs. The new Flexible Cost Allocation (FCA) feature provides more versatile cost allocation options through a central metering policy. Using FCA metering policy, you can choose to allocate all of your Transit Gateway data processing and data transfer usage to the source attachment account, the destination attachment account, or the central Transit Gateway account. FCA metering policies can be configured at an attachment-level or individual flow-level granularity. FCA also supports middle-box deployment models enabling you to allocate data processing usage on middle-box appliances such as AWS Network Firewall to the original source or destination attachment owners. This flexibility allows you to implement multiple cost allocation models on a single Transit Gateway, accommodating various chargeback scenarios within your AWS network infrastructure. Flexible Cost Allocation is available in all commercial AWS Regions where Transit Gateway is available. You can enable these features using the AWS Management Console, AWS Command Line Interface (CLI) and the AWS Software Development Kit (SDK). There is no additional charge for using FCA on Transit Gateway. For more information, see the Transit Gateway documentation pages.

🆕 AWS Flexible Cost Allocation for Transit Gateway lets you distribute data costs across accounts, supporting various models and chargebacks, previously sender-pay, now free in all commercial regions.

#AWS #AwsTransitGateway

AWS Network Firewall now supports AWS Transit Gateway native integration https://aws.amazon.com/network-firewall/ now supports native integration with https://aws.amazon.com/transit-gateway/ for simplified deployment and management of network security across your global AWS infrastructure. This capability is available in 5 AWS Regions, allowing customers to implement security controls more efficiently. AWS Transit Gateway interconnects your Amazon Virtual Private Clouds (VPCs) and on-premises networks, while AWS Network Firewall provides comprehensive security controls for those VPCs. Native attachment simplifies connecting these services, providing centralized security control without complex VPC configurations. Additionally, you can configure one or multiple Availability Zones (AZs) for high availability, maintaining traffic flow within the same AZ. This integration is available in the following https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/: Africa (Cape Town), Asia Pacific (Hyderabad), Europe (Stockholm), Europe (Zurich), and Middle East (UAE). There are no additional charges for this native integration beyond standard pricing of https://aws.amazon.com/network-firewall/pricing/ and https://aws.amazon.com/transit-gateway/pricing/. To get started, visit the AWS Network Firewall service https://docs.aws.amazon.com/network-firewall/latest/developerguide/firewall-creating.html.  

AWS Network Firewall now supports AWS Transit Gateway native integration

https://aws.amazon.com/network-firewall/ now supports native integration with https://aws.amazon.com/transit-gateway/ for simplified deployment and management of network securi...

#AWS #AwsNetworkFirewall #AwsTransitGateway

AWS Network Firewall now supports AWS Transit Gateway native integration AWS Network Firewall now supports native integration with AWS Transit Gateway for simplified deployment and management of network security across your global AWS infrastructure. This capability is available in 5 AWS Regions, allowing customers to implement security controls more efficiently. AWS Transit Gateway interconnects your Amazon Virtual Private Clouds (VPCs) and on-premises networks, while AWS Network Firewall provides comprehensive security controls for those VPCs. Native attachment simplifies connecting these services, providing centralized security control without complex VPC configurations. Additionally, you can configure one or multiple Availability Zones (AZs) for high availability, maintaining traffic flow within the same AZ. This integration is available in the following AWS Regions: Africa (Cape Town), Asia Pacific (Hyderabad), Europe (Stockholm), Europe (Zurich), and Middle East (UAE). There are no additional charges for this native integration beyond standard pricing of AWS Network Firewall and AWS Transit Gateway. To get started, visit the AWS Network Firewall service documentation.

🆕 AWS Network Firewall now integrates natively with AWS Transit Gateway in 5 regions for simplified global network security, offering high availability and no extra charges beyond standard pricing.

#AWS #AwsNetworkFirewall #AwsTransitGateway

AWS Network Firewall introduces automated domain lists and insights https://aws.amazon.com/network-firewall/ now offers automated domain lists and insights, a feature that enhances visibility into network traffic and simplifies firewall rule configuration. This new capability analyzes HTTP and HTTPS traffic logs from the last 30 days and provides insights into frequently accessed domains, enabling quick rule creation based on observed network traffic patterns. Many organizations now use allow-list policies to limit access to approved destinations only. Automated domain lists reduce the time and effort required to identify necessary domains, configure initial rules, and update allow lists as business needs change. This feature helps quickly identify legitimate traffic while maintaining a restrictive default stance, balancing security with operational efficiency. This feature is supported in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where AWS Network Firewall is available today. There is no additional cost to generate automated domain lists and insights on AWS Network Firewall. To get started, visit the AWS Network Firewall console and enable analysis mode for your firewall. For more information, please refer to the AWS Network Firewall service https://docs.aws.amazon.com/network-firewall/latest/developerguide/quotas.html.

AWS Network Firewall introduces automated domain lists and insights

https://aws.amazon.com/network-firewall/ now offers automated domain lists and insights, a feature that enhances visibility into network traffic and simplifies firewall r...

#AWS #AwsNetworkFirewall #AwsTransitGateway #AmazonVpc

AWS Network Firewall introduces automated domain lists and insights AWS Network Firewall now offers automated domain lists and insights, a feature that enhances visibility into network traffic and simplifies firewall rule configuration. This new capability analyzes HTTP and HTTPS traffic logs from the last 30 days and provides insights into frequently accessed domains, enabling quick rule creation based on observed network traffic patterns. Many organizations now use allow-list policies to limit access to approved destinations only. Automated domain lists reduce the time and effort required to identify necessary domains, configure initial rules, and update allow lists as business needs change. This feature helps quickly identify legitimate traffic while maintaining a restrictive default stance, balancing security with operational efficiency. This feature is supported in all AWS Regions where AWS Network Firewall is available today. There is no additional cost to generate automated domain lists and insights on AWS Network Firewall. To get started, visit the AWS Network Firewall console and enable analysis mode for your firewall. For more information, please refer to the AWS Network Firewall service documentation.

🆕 AWS Network Firewall introduces automated domain lists and insights

#AWS #AwsNetworkFirewall #AwsTransitGateway #AmazonVpc

AWS Weekly Roundup: New Asia Pacific Region, DynamoDB updates, Amazon Q developer, and more (January 13, 2025) As we move into the second week of 2025, China is celebrating Laba Festival (腊八节), a traditional holiday, which marks the beginning of Chinese New Year preparations. On this day, Chinese people prepare Laba congee, a special porridge combining various grains, dried fruits, and nuts. This nutritious mixture symbolizes harmony, prosperity, and good fortune — […]

AWS Weekly Roundup: New Asia Pacific Region, DynamoDB updates, Amazon Q developer, and more (January 13, 2025)

As we move into the s...

#AWS #AmazonConnect #AmazonDynamodb #AmazonQDeveloper #AmazonSagemaker #Announcements #AwsChatbot #AwsPrivatelink #AwsTransitGateway #Launch #News #WeekInReview

AWS Weekly Roundup: New Asia Pacific Region, DynamoDB updates, Amazon Q developer, and more (January 13, 2025) As we move into the second week of 2025, China is celebrating Laba Festival (腊八节), a traditional holiday, which marks the beginning of Chinese New Year preparations. On this day, Chinese people prepare Laba congee, a special porridge combining various grains, dried fruits, and nuts. This nutritious mixture symbolizes harmony, prosperity, and good fortune — […]

AWS Weekly Roundup: New Asia Pacific Region, DynamoDB updates, Amazon Q developer, and more (January 13, 2025)

As we move into the s...

#AWS #AmazonConnect #AmazonDynamodb #AmazonQDeveloper #AmazonSagemaker #Announcements #AwsChatbot #AwsPrivatelink #AwsTransitGateway #Launch #News #WeekInReview

AWS Transit Gateway and AWS Cloud WAN enhance visibility metrics and Path MTU support AWS Transit Gateway (TGW) and AWS Cloud WAN now support per availability zone (AZ) metrics delivered to CloudWatch. Furthermore, both services now support Path Maximum Transmission Unit Discovery (PMTUD) for effective mitigation against MTU mismatch issues in their global networks. TGW and Cloud WAN allow customers to monitor their global network through performance and traffic metrics such as bytes in/out, packets in/out, and packets dropped. Until now, these metrics were available at an attachment level, and aggregate TGW and Core Network Edge (CNE) levels. With this launch, customers have more granular visibility into AZ-level metrics for VPC attachments. AZ-level metrics enable customers to rapidly troubleshoot any AZ impairments and provide deeper visibility in AZ-level traffic patterns across TGW and Cloud WAN. TGW and Cloud WAN now also support standard PMTUD mechanism for traffic ingressing on VPC attachments. Until now, jumbo sized packets exceeding the TGW/CNE MTU (8500 bytes) would get silently dropped on VPC attachments. With this launch, an Internet Control Message Protocol (ICMP) Fragmentation Needed response message is sent back to sender hosts allowing them to remediate packet MTU size and thus minimize packet loss due to MTU mismatches in their network. PMTUD support is available for both IPv4 and IPv6 packets. The per-AZ CloudWatch metrics and PMTUD support are available within each service in all AWS Regions where TGW or Cloud WAN are available. For more information, see the https://docs.aws.amazon.com/vpc/latest/tgw/transit-gateway-cloudwatch-metrics.html and https://docs.aws.amazon.com/network-manager/latest/cloudwan/cloudwan-metrics.html documentation pages.

AWS Transit Gateway and AWS Cloud WAN enhance visibility metrics and Path MTU support

AWS Transit Gateway (TGW) and AWS Cloud WAN now support per availability zone (AZ) metrics delivered to CloudWatch. Furthermore, both services now support ...

#AWS #AwsGovcloudUs #AwsCloudWan #AwsTransitGateway

AWS Transit Gateway and AWS Cloud WAN enhance visibility metrics and Path MTU support AWS Transit Gateway (TGW) and AWS Cloud WAN now support per availability zone (AZ) metrics delivered to CloudWatch. Furthermore, both services now support Path Maximum Transmission Unit Discovery (PMTUD) for effective mitigation against MTU mismatch issues in their global networks. TGW and Cloud WAN allow customers to monitor their global network through performance and traffic metrics such as bytes in/out, packets in/out, and packets dropped. Until now, these metrics were available at an attachment level, and aggregate TGW and Core Network Edge (CNE) levels. With this launch, customers have more granular visibility into AZ-level metrics for VPC attachments. AZ-level metrics enable customers to rapidly troubleshoot any AZ impairments and provide deeper visibility in AZ-level traffic patterns across TGW and Cloud WAN. TGW and Cloud WAN now also support standard PMTUD mechanism for traffic ingressing on VPC attachments. Until now, jumbo sized packets exceeding the TGW/CNE MTU (8500 bytes) would get silently dropped on VPC attachments. With this launch, an Internet Control Message Protocol (ICMP) Fragmentation Needed response message is sent back to sender hosts allowing them to remediate packet MTU size and thus minimize packet loss due to MTU mismatches in their network. PMTUD support is available for both IPv4 and IPv6 packets. The per-AZ CloudWatch metrics and PMTUD support are available within each service in all AWS Regions where TGW or Cloud WAN are available. For more information, see the AWS Transit Gateway and AWS Cloud WAN documentation pages.

🆕 AWS Transit Gateway and AWS Cloud WAN enhance visibility metrics and Path MTU support

#AWS #AwsGovcloudUs #AwsCloudWan #AwsTransitGateway