#AmazonVpc

@awsrecentnews.bsky.social

1 week ago

AWS announces pricing for VPC Encryption Controls AWS is launching pricing for VPC Encryption Controls, a security and compliance feature that enables you to audit and enforce encryption-in-transit of all traffic flows within and across Virtual Private Clouds (VPCs) in a region. VPC Encryption controls can be enabled in two modes: Monitor mode detects presence of any unencrypted traffic within your VPCs, and Enforce Mode ensures all data-in-transit is encrypted and prevents the bring up of any resources that allow unencrypted traffic within your VPC. Starting March 1, 2026, VPC Encryption Controls will transition from a free preview to a paid feature. You will be charged a fixed hourly rate for every non-empty VPC (VPC that has network interfaces in them) that has Encryption Controls enabled in either monitor or enforce mode. There will be no charge for empty VPCs that have encryption controls enabled. When you enable encryption support on a Transit Gateway, standard VPC Encryption Controls charges apply to all VPCs attached to that Transit Gateway irrespective of their encryption controls mode (monitor, enforce or off) even if they are empty. To learn more about VPC Encryption Controls and view detailed regional pricing, visit the VPC Encryption Controls documentation and VPC pricing page.

🆕 AWS will start charging for VPC Encryption Controls on March 1, 2026. A fixed hourly rate applies to non-empty VPCs with controls enabled; empty VPCs and attached Transit Gateways are free. For details, see the VPC Encryption Controls and VPC pricing pages.

#AWS #AmazonVpc

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

1 week ago

AWS announces pricing for VPC Encryption Controls AWS is launching pricing for VPC Encryption Controls, a security and compliance feature that enables you to audit and enforce encryption-in-transit of all traffic flows within and across Virtual Private Clouds (VPCs) in a region. VPC Encryption controls can be enabled in two modes: Monitor mode detects presence of any unencrypted traffic within your VPCs, and Enforce Mode ensures all data-in-transit is encrypted and prevents the bring up of any resources that allow unencrypted traffic within your VPC. Starting March 1, 2026, VPC Encryption Controls will transition from a free preview to a paid feature. You will be charged a fixed hourly rate for every non-empty VPC (VPC that has network interfaces in them) that has Encryption Controls enabled in either monitor or enforce mode. There will be no charge for empty VPCs that have encryption controls enabled. When you enable encryption support on a Transit Gateway, standard VPC Encryption Controls charges apply to all VPCs attached to that Transit Gateway irrespective of their encryption controls mode (monitor, enforce or off) even if they are empty. To learn more about VPC Encryption Controls and view detailed regional pricing, visit the https://docs.aws.amazon.com/vpc/latest/userguide/vpc-encryption-controls.html and https://aws.amazon.com/vpc/pricing/.

AWS announces pricing for VPC Encryption Controls

AWS is launching pricing for VPC Encryption Controls, a security and compliance feature that enables you to audit and enforce encryption-in-transit of all traffic flows within and across Virtual Private Clouds (VPCs) in a regio...

#AWS #AmazonVpc

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

2 months ago

Amazon VPC Route Server now available in new regions Amazon VPC Route Server is now available in 16 new regions in addition to the 14 existing ones. VPC Route Server simplifies dynamic routing between virtual appliances in your Amazon VPC. It allows you to advertise routing information through Border Gateway Protocol (BGP) from virtual appliances and dynamically update the VPC route tables associated with subnets and internet gateway. With this launch, Amazon VPC Route Server is available in 30 AWS Regions: US East (Virginia), US East (Ohio), US West (Oregon), Europe (Ireland), Europe (Frankfurt), Asia Pacific (Tokyo), US West (N. California), Canada West (Calgary), Asia Pacific (Malaysia), Europe (Milan), Europe (Paris), Asia Pacific (Sydney), Europe (London), Canada (Central), Mexico (Central), South America (Sao Paulo),Asia Pacific (Seoul), Europe (Zurich), Europe (Stockholm), Middle East (UAE), Israel (Tel Aviv), Asia Pacific (Taipei), Asia Pacific (New Zealand), Asia Pacific (Melbourne), Middle East (Bahrain), Asia Pacific (Jakarta), Africa (Cape Town), Asia Pacific (Hong Kong), Asia Pacific (Osaka) and Asia Pacific (Thailand). To learn more about Amazon VPC Route Server, visit this https://docs.aws.amazon.com/vpc/latest/userguide/route-server-how-it-works.html.

Amazon VPC Route Server now available in new regions

Amazon VPC Route Server is now available in 16 new regions in addition to the 14 existing ones.

VPC Route Server simplifies dynamic routing between virtual appliances in your Amazon VPC. It al...

#AWS #AmazonVpc #AmazonVirtualPrivateCloud

0 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

2 months ago

Amazon VPC Route Server now available in new regions Amazon VPC Route Server is now available in 16 new regions in addition to the 14 existing ones. VPC Route Server simplifies dynamic routing between virtual appliances in your Amazon VPC. It allows you to advertise routing information through Border Gateway Protocol (BGP) from virtual appliances and dynamically update the VPC route tables associated with subnets and internet gateway. With this launch, Amazon VPC Route Server is available in 30 AWS Regions: US East (Virginia), US East (Ohio), US West (Oregon), Europe (Ireland), Europe (Frankfurt), Asia Pacific (Tokyo), US West (N. California), Canada West (Calgary), Asia Pacific (Malaysia), Europe (Milan), Europe (Paris), Asia Pacific (Sydney), Europe (London), Canada (Central), Mexico (Central), South America (Sao Paulo),Asia Pacific (Seoul), Europe (Zurich), Europe (Stockholm), Middle East (UAE), Israel (Tel Aviv), Asia Pacific (Taipei), Asia Pacific (New Zealand), Asia Pacific (Melbourne), Middle East (Bahrain), Asia Pacific (Jakarta), Africa (Cape Town), Asia Pacific (Hong Kong), Asia Pacific (Osaka) and Asia Pacific (Thailand). To learn more about Amazon VPC Route Server, visit this page.

🆕 Amazon VPC Route Server is now in 16 new regions, totaling 30. It simplifies dynamic routing via BGP, updating subnet route tables. Available in US, Europe, Asia Pacific, Canada, Mexico, South America, and Africa.

#AWS #AmazonVpc #AmazonVirtualPrivateCloud

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

2 months ago

Amazon VPC IPAM policies now support RDS and Application Load Balancers Amazon Virtual Private Cloud (VPC) IP Address Manager (IPAM) now supports policies for Amazon Relational Database Service (RDS) instances and Application Load Balancers (ALB). This feature enables IP administrators to centrally configure and enforce IP allocation strategies for these resources, improving operational posture and simplifying network and security management. Using IPAM policies, IP administrators can centrally define public IP allocation rules for AWS resources, such as RDS instances, Application Load Balancers and Network Address Translation (NAT) Gateways when used in regional availability mode, and Elastic IP addresses. The IP allocation policy configured centrally cannot be superseded by individual application teams, ensuring compliance at all times. Before this feature, IP administrators had to educate database administrators and application developers about IP allocation requirements for RDS instances and Application Load Balancers, and rely on them to always comply with best practices. Now, you can add IP-based filters for RDS and ALB traffic in your networking and security constructs like access control lists, route tables, security groups, and firewalls, with confidence that public IPv4 address assignments to these resources always come from specific IPAM pools. The feature is available in all AWS commercial regions and the AWS GovCloud (US) Regions, in both Free Tier and Advanced Tier of VPC IPAM. When used with the Advanced Tier of VPC IPAM, customers can set policies across AWS accounts and AWS regions. To get started please see the https://docs.aws.amazon.com/vpc/latest/ipam/define-public-ipv4-allocation-strategy-with-ipam-policies.html. To learn more about IPAM, view the https://docs.aws.amazon.com/vpc/latest/ipam/what-it-is-ipam.html. For details on pricing, refer to the IPAM tab on the https://www.amazonaws.cn/en/vpc/pricing/.

Amazon VPC IPAM policies now support RDS and Application Load Balancers

Amazon Virtual Private Cloud (VPC) IP Address Manager (IPAM) now supports policies for Amazon Relational Database Service (RDS) instances and Application Load Balancers (ALB). This feature e...

#AWS #AwsGovcloudUs #AmazonVpc

0 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

2 months ago

Amazon VPC IPAM policies now support RDS and Application Load Balancers Amazon Virtual Private Cloud (VPC) IP Address Manager (IPAM) now supports policies for Amazon Relational Database Service (RDS) instances and Application Load Balancers (ALB). This feature enables IP administrators to centrally configure and enforce IP allocation strategies for these resources, improving operational posture and simplifying network and security management. Using IPAM policies, IP administrators can centrally define public IP allocation rules for AWS resources, such as RDS instances, Application Load Balancers and Network Address Translation (NAT) Gateways when used in regional availability mode, and Elastic IP addresses. The IP allocation policy configured centrally cannot be superseded by individual application teams, ensuring compliance at all times. Before this feature, IP administrators had to educate database administrators and application developers about IP allocation requirements for RDS instances and Application Load Balancers, and rely on them to always comply with best practices. Now, you can add IP-based filters for RDS and ALB traffic in your networking and security constructs like access control lists, route tables, security groups, and firewalls, with confidence that public IPv4 address assignments to these resources always come from specific IPAM pools. The feature is available in all AWS commercial regions and the AWS GovCloud (US) Regions, in both Free Tier and Advanced Tier of VPC IPAM. When used with the Advanced Tier of VPC IPAM, customers can set policies across AWS accounts and AWS regions. To get started please see the IPAM policies documentation page. To learn more about IPAM, view the IPAM documentation. For details on pricing, refer to the IPAM tab on the Amazon VPC Pricing Page.

🆕 Amazon VPC IPAM now supports RDS and ALB, centralizing IP allocation for better network and security management. Available globally, it simplifies compliance and IP management. For details, see the IPAM documentation.

#AWS #AwsGovcloudUs #AmazonVpc

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

3 months ago

Amazon CloudFront integrates with VPC IPAM to support BYOIP Amazon CloudFront now supports bringing your own IP addresses (BYOIP) for Anycast Static IPs via VPC IP Address Manager (IPAM). This capability enables network administrators to use their own public IPv4 address pools with CloudFront distributions, simplifying IP address management across AWS's global infrastructure. CloudFront typically uses rotating IP addresses to serve traffic. CloudFront Anycast Static IPs enables customers to provide a dedicated list of IP addresses to partners and customers, enhancing security and simplifying network management. Previously, customers implementing Anycast Static IPs received AWS-provided static IP addresses for their workloads. With IPAM's unified interface, customers can now create dedicated IP address pools using BYOIP and assign them to CloudFront Anycast Static IP lists. Customers do not need to change the existing IP address space for their applications when they migrate to CloudFront, thus maintaining existing allow-lists and branding. The feature is available within Amazon VPC IPAM in all commercial AWS Regions, excluding the AWS GovCloud (US) Regions, and China (Beijing, operated by Sinnet) and China (Ningxia, operated by NWCD). To learn more about CloudFront BYOIP feature, view the https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/bring-your-own-ip-address-using-ipam.html. For details on pricing, refer to the IPAM tab on the https://aws.amazon.com/vpc/pricing/.

Amazon CloudFront integrates with VPC IPAM to support BYOIP

Amazon CloudFront now supports bringing your own IP addresses (BYOIP) for Anycast Static IPs via VPC IP Address Manager (IPAM). This capability enables network administrators to use their own public ...

#AWS #AmazonVpc #AmazonCloudfront

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

3 months ago

Amazon CloudFront integrates with VPC IPAM to support BYOIP Amazon CloudFront now supports bringing your own IP addresses (BYOIP) for Anycast Static IPs via VPC IP Address Manager (IPAM). This capability enables network administrators to use their own public IPv4 address pools with CloudFront distributions, simplifying IP address management across AWS's global infrastructure. CloudFront typically uses rotating IP addresses to serve traffic. CloudFront Anycast Static IPs enables customers to provide a dedicated list of IP addresses to partners and customers, enhancing security and simplifying network management. Previously, customers implementing Anycast Static IPs received AWS-provided static IP addresses for their workloads. With IPAM's unified interface, customers can now create dedicated IP address pools using BYOIP and assign them to CloudFront Anycast Static IP lists. Customers do not need to change the existing IP address space for their applications when they migrate to CloudFront, thus maintaining existing allow-lists and branding. The feature is available within Amazon VPC IPAM in all commercial AWS Regions, excluding the AWS GovCloud (US) Regions, and China (Beijing, operated by Sinnet) and China (Ningxia, operated by NWCD). To learn more about CloudFront BYOIP feature, view the BYOIP CloudFront documentation. For details on pricing, refer to the IPAM tab on the Amazon VPC Pricing Page.

🆕 Amazon CloudFront supports BYOIP for Anycast Static IPs via VPC IPAM, letting customers use their own IPv4 pools, simplifying IP management, and keeping existing allow-lists. Available in most commercial regions except AWS GovCloud and China.

#AWS #AmazonVpc #AmazonCloudfront

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

3 months ago

Introducing VPC encryption controls: Enforce encryption in transit within and across VPCs in a Region AWS announces VPC encryption controls, a new capability that helps organizations audit and enforce encryption in transit for all traffic within and across VPCs in a Region, simplifying compliance with regulatory frameworks like HIPAA, PCI DSS, and FedRAMP through automated monitoring and enforcement modes.

Introducing VPC encryption controls: Enforce encryption in transit within and across VPCs in a Region

AWS announces VPC encryption controls, a new capability that helps organizations audit and enforce encryption in transit for all traffic within an...

#AWS #AmazonVpc #Announcements #Launch #News

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

3 months ago

Amazon VPC IPAM now supports policies to enforce IP allocation strategy Amazon Virtual Private Cloud (VPC) IP Address Manager (IPAM) supports policies to centrally configure and enforce your desired IP allocation strategy. This ensures resources launch with public IPv4 addresses from specific IPAM pools, improving operational posture, and simplifying network and security management. Using IPAM policies, the IP administrator can centrally define public IP allocation rules for AWS resources, such as Network Address Translation (NAT) Gateways when used in regional availability mode and Elastic IP addresses. The IP allocation policy configured centrally cannot be superseded by individual application teams, ensuring compliance at all times. Before this feature, IP administrator had to educate application owners across their organization, and rely on them to always comply with IP allocation best practices. IPAM policies improve your operational model multi-fold. Now, you can add IP based filters in your networking and security constructs like access control lists, route tables, security groups, and firewalls, with confidence that public IPv4 addresses assignments to AWS resources always come from specific IPAM pools. The feature is available in all AWS commercial regions and the AWS GovCloud (US) Regions, in both Free Tier and Advanced Tier of VPC IPAM. When used with the Advanced Tier of VPC IPAM, customers can set policies across AWS accounts and AWS regions. To get started please see the https://docs.aws.amazon.com/vpc/latest/ipam/define-public-ipv4-allocation-strategy-with-ipam-policies.html. To learn more about IPAM, view the https://docs.aws.amazon.com/vpc/latest/ipam/what-it-is-ipam.html. For details on pricing, refer to the IPAM tab on the https://www.amazonaws.cn/en/vpc/pricing/.

Amazon VPC IPAM now supports policies to enforce IP allocation strategy

Amazon Virtual Private Cloud (VPC) IP Address Manager (IPAM) supports policies to centrally configure and enforce your desired IP allocation strategy. This ensures resources launch with publ...

#AWS #AmazonVpc #AwsGovcloudUs

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

3 months ago

AWS NAT Gateway now supports regional availability Amazon Web Services (AWS) announces regional availability mode for NAT Gateways. With this launch, you can create a single NAT Gateway that automatically expands and contracts across availability zones (AZs) in your Virtual Private Cloud (VPC) based on your workload presence, to maintain high availability while offering simplified setup and management. A NAT Gateway enables instances in a private subnet to connect to services outside your VPC using the NAT Gateway's IP address. With this launch, you can create a NAT Gateway and set its availability to regional. You do not need a public subnet to host a regional NAT Gateway. You also do not have to create and delete NAT Gateways, and edit your route tables every time your workloads expand to new availability zones. You simply create a NAT Gateway with regional mode, choose your VPC, and it automatically expands and contracts across all availability zones based on your workload's presence, maintaining high availability. You can use this feature with Amazon provided IP addresses or bring your own IP addresses. This capability is available in all commercial AWS Regions, except the AWS GovCloud (US) Regions and the China Regions. To learn more about VPC NAT Gateway and this feature, please visit our https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html

AWS NAT Gateway now supports regional availability

Amazon Web Services (AWS) announces regional availability mode for NAT Gateways. With this launch, you can create a single NAT Gateway that automatically expands and contracts across availability zones (AZs) in your Virtual Pr...

#AWS #AmazonVpc

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

3 months ago

Amazon VPC IPAM automates IP assignments from Infoblox IPAM Today, AWS launched the ability for Amazon VPC IP Address Manager (IPAM) to automatically acquire non-overlapping IP address allocations from Infoblox Universal IPAM. This feature minimizes manual processes between cloud and on-premises administrators, reducing the turnaround time. With this launch, you can automatically acquire non-overlapping IP addresses from your on-premises Infoblox Universal IPAM into your top-level AWS IPAM pool and organize them into regional pools based on your business requirements. When you acquire non-overlapping IPs, you reduce the risk of service disruptions because your IPs don’t conflict with on-premise IP addresses. Previously, in hybrid cloud environments, administrators had to use offline means such as tickets or emails to request and allocate IP addresses, which was often error-prone and time-consuming. This integration automates the manual process, improving operational efficiency. This feature is available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where Amazon VPC IPAM is supported, excluding AWS China Regions and AWS GovCloud (US) Regions. To learn more about IPAM, view the https://docs.aws.amazon.com/vpc/latest/ipam/integrate-infoblox-ipam.html. For details on pricing, refer to the IPAM tab on the https://aws.amazon.com/vpc/pricing/.

Amazon VPC IPAM automates IP assignments from Infoblox IPAM

Today, AWS launched the ability for Amazon VPC IP Address Manager (IPAM) to automatically acquire non-overlapping IP address allocations from Infoblox Universal IPAM. This feature minimizes manual processes between cl...

#AWS #AmazonVpc

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

3 months ago

Amazon VPC IPAM automates IP assignments from Infoblox IPAM Today, AWS launched the ability for Amazon VPC IP Address Manager (IPAM) to automatically acquire non-overlapping IP address allocations from Infoblox Universal IPAM. This feature minimizes manual processes between cloud and on-premises administrators, reducing the turnaround time. With this launch, you can automatically acquire non-overlapping IP addresses from your on-premises Infoblox Universal IPAM into your top-level AWS IPAM pool and organize them into regional pools based on your business requirements. When you acquire non-overlapping IPs, you reduce the risk of service disruptions because your IPs don’t conflict with on-premise IP addresses. Previously, in hybrid cloud environments, administrators had to use offline means such as tickets or emails to request and allocate IP addresses, which was often error-prone and time-consuming. This integration automates the manual process, improving operational efficiency. This feature is available in all AWS Regions where Amazon VPC IPAM is supported, excluding AWS China Regions and AWS GovCloud (US) Regions. To learn more about IPAM, view the IPAM documentation. For details on pricing, refer to the IPAM tab on the Amazon VPC Pricing Page.

🆕 AWS introduced Amazon VPC IPAM to automate IP assignments, reducing manual processes and speeding up IP allocation. Available globally except AWS China and GovCloud, it boosts efficiency by eliminating time-consuming, error-prone manual IP management.

#AWS #AmazonVpc

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

4 months ago

AWS Transfer Family SFTP connectors now support VPC-based connectivity AWS Transfer Family SFTP connectors now support VPC-based connectivity, allowing secure file transfers between Amazon S3 and remote SFTP servers through your existing VPC infrastructure without exposing endpoints to the internet.

AWS Transfer Family SFTP connectors now support VPC-based connectivity

AWS Transfer Family SFTP connectors now support VPC-based connectivity, allowing secure file transfers between Amazon S3 and remot...

#AWS #AmazonVpc #AwsTransferFamily #AwsTransferForSftp #Migration&TransferServices #Storage

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

4 months ago

AWS Weekly Roundup: Amazon Quick Suite, Amazon EC2, Amazon EKS, and more (October 13, 2025) This week I was at the inaugural AWS AI in Practice meetup from the AWS User Group UK. AI-assisted software development and agents were the focus of the evening! Next week I’ll be in Italy for Codemotion (Milan) and an AWS User Group meetup (Rome). My sessions there will be about AI agents and context […]

AWS Weekly Roundup: Amazon Quick Suite, Amazon EC2, Amazon EKS, and more (October 13, 2025)

This week I was at the inaugural AWS AI in Practice meetup from the AW...

#AWS #AmazonConnect #AmazonEc2 #AmazonElasticKubernetesService #AmazonQDeveloper #AmazonRds #AmazonVpc #Launch #News #WeekInReview

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

4 months ago

Amazon VPC IPAM automates prefix list updates Today, AWS announced the ability for Amazon VPC IP Address Manager (IPAM) to automate prefix lists updates with prefix list resolver (PLR). This feature allows network administrators to automatically update prefix lists based on their business logic in IPAM improving their operational posture and reducing overhead. Using IPAM PLR, you can define business rules for synchronizing prefix lists with IP address ranges from various resources, such as VPCs, subnets and IPAM pools. These prefix lists can then be referenced in resources such as route tables and security groups across your AWS environment, based on your connectivity requirements. Previously, you had to manually update your prefix lists to add or remove IP address ranges based on changes to your AWS environment. This was operationally complex and error prone. IPAM PLR automates prefix list updates requiring no manual intervention, improving your operational posture. This feature is now available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where Amazon VPC IPAM is supported, including AWS China Regions, and AWS GovCloud (US) Regions. To learn more about this feature, view the https://docs.aws.amazon.com/vpc/latest/ipam/automate-prefix-list-updates.html. For details on pricing, refer to the IPAM tab on the https://aws.amazon.com/vpc/pricing/.

Amazon VPC IPAM automates prefix list updates

Today, AWS announced the ability for Amazon VPC IP Address Manager (IPAM) to automate prefix lists updates with prefix list resolver (PLR). This feature allows network administrators to automatically update prefix lists based on th...

#AWS #AmazonVpc

2 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

4 months ago

Amazon VPC IPAM automates prefix list updates Today, AWS announced the ability for Amazon VPC IP Address Manager (IPAM) to automate prefix lists updates with prefix list resolver (PLR). This feature allows network administrators to automatically update prefix lists based on their business logic in IPAM improving their operational posture and reducing overhead. Using IPAM PLR, you can define business rules for synchronizing prefix lists with IP address ranges from various resources, such as VPCs, subnets and IPAM pools. These prefix lists can then be referenced in resources such as route tables and security groups across your AWS environment, based on your connectivity requirements. Previously, you had to manually update your prefix lists to add or remove IP address ranges based on changes to your AWS environment. This was operationally complex and error prone. IPAM PLR automates prefix list updates requiring no manual intervention, improving your operational posture. This feature is now available in all AWS Regions where Amazon VPC IPAM is supported, including AWS China Regions, and AWS GovCloud (US) Regions. To learn more about this feature, view the AWS IPAM documentation. For details on pricing, refer to the IPAM tab on the Amazon VPC Pricing Page.

🆕 AWS announced Amazon VPC IPAM's prefix list resolver to automate updates, reducing manual overhead and improving operational efficiency. Now available in all supported regions, it syncs prefix lists based on business rules, eliminating manual updates.

#AWS #AmazonVpc

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

4 months ago

Amazon VPC Reachability Analyzer and Amazon VPC Network Access Analyzer are now available in AWS GovCloud (US) Regions With this launch, Amazon https://docs.aws.amazon.com/vpc/latest/reachability/getting-started.html and Amazon VPC https://docs.aws.amazon.com/vpc/latest/network-access-analyzer/what-is-network-access-analyzer.html are now available in both AWS GovCloud (US-West) and AWS GovCloud (US-East) Regions. VPC Reachability Analyzer allows you to diagnose network reachability between a source resource and a destination resource in your virtual private clouds (VPCs) by analyzing your network configurations. For example, Reachability Analyzer can help you identify a missing route table entry in your VPC route table that could be blocking network reachability between an EC2 instance in Account A that is not able to connect to another EC2 instance in Account B in your AWS Organization. VPC Network Access Analyzer allows you to identify unintended network access to your AWS resources, helping you meet your security and compliance guidelines. For example, you can create a scope to verify that all paths from your web-applications to the internet, traverse the firewall, and detect any paths that bypass the firewall. For more information, visit documentation for https://docs.aws.amazon.com/vpc/latest/reachability/what-is-reachability-analyzer.html and https://docs.aws.amazon.com/vpc/latest/network-access-analyzer/what-is-network-access-analyzer.html For pricing, refer to the Network Analysis tab on the https://aws.amazon.com/vpc/pricing/.

Amazon VPC Reachability Analyzer and Amazon VPC Network Access Analyzer are now available in AWS GovCloud (US) Regions

With this launch, Amazon docs.aws.amazon.com/vpc/latest/reachability/... and Amazon VPC https://docs.aws.amazon.com/vpc/latest/networ

#AWS #AmazonVpc

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

4 months ago

Amazon VPC Reachability Analyzer and Amazon VPC Network Access Analyzer are now available in AWS GovCloud (US) Regions With this launch, Amazon VPC Reachability Analyzer and Amazon VPC Network Access Analyzer are now available in both AWS GovCloud (US-West) and AWS GovCloud (US-East) Regions. VPC Reachability Analyzer allows you to diagnose network reachability between a source resource and a destination resource in your virtual private clouds (VPCs) by analyzing your network configurations. For example, Reachability Analyzer can help you identify a missing route table entry in your VPC route table that could be blocking network reachability between an EC2 instance in Account A that is not able to connect to another EC2 instance in Account B in your AWS Organization. VPC Network Access Analyzer allows you to identify unintended network access to your AWS resources, helping you meet your security and compliance guidelines. For example, you can create a scope to verify that all paths from your web-applications to the internet, traverse the firewall, and detect any paths that bypass the firewall. For more information, visit documentation for VPC Reachability Analyzer and VPC Network Access Analyzer. For pricing, refer to the Network Analysis tab on the Amazon VPC Pricing Page.

🆕 AWS GovCloud (US) now offers VPC Reachability and Network Access Analyzers to diagnose network issues and secure VPCs. Available in US-West and US-East regions. For details, see VPC documentation and pricing.

#AWS #AmazonVpc

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

4 months ago

AWS Weekly Roundup: Amazon Q Developer, AWS Step Functions, AWS Cloud Club Captain deadline, and more (September 22, 2025) Three weeks ago, I published a post about the new AWS Region in New Zealand (ap-southeast-6). This led to an incredible opportunity to visit New Zealand, where I met passionate builders and presented at several events including Serverless and Platform Engineering meetup, AWS Tools and Programming meetup, AWS Cloud Clubs in Auckland, and AWS Community […]

AWS Weekly Roundup: Amazon Q Developer, AWS Step Functions, AWS Cloud Club Captain deadline, and more (September 22, 2025)

Three weeks ago, I published a post about the new AWS Region in New Zealand (ap-sou...

#AWS #AmazonBedrock #AmazonQDeveloper #AmazonVpc #AwsStepFunctions #News #WeekInReview

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

5 months ago

AWS Transfer Family SFTP connectors now support VPC-based connectivity AWS Transfer Family SFTP connectors now support VPC-based connectivity, allowing secure file transfers between Amazon S3 and remote SFTP servers through your existing VPC infrastructure without exposing endpoints to the internet.

AWS Transfer Family SFTP connectors now support VPC-based connectivity

AWS Transfer Family SFTP connectors now support VPC-based connectivity, allowing secure file transfers between Amazon S3 and remot...

#AWS #AmazonVpc #AwsTransferFamily #AwsTransferForSftp #Migration&TransferServices #Storage

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

5 months ago

AWS Weekly Roundup: Amazon Q Developer, AWS Step Functions, AWS Cloud Club Captain deadline, and more (September 22, 2025) Three weeks ago, I published a post about the new AWS Region in New Zealand (ap-southeast-6). This led to an incredible opportunity to visit New Zealand, where I met passionate builders and presented at several events including Serverless and Platform Engineering meetup, AWS Tools and Programming meetup, AWS Cloud Clubs in Auckland, and AWS Community […]

AWS Weekly Roundup: Amazon Q Developer, AWS Step Functions, AWS Cloud Club Captain deadline, and more (September 22, 2025)

Three weeks ago, I published a post about the new AWS Region in New Zealand (ap-sou...

#AWS #AmazonBedrock #AmazonQDeveloper #AmazonVpc #AwsStepFunctions #News #WeekInReview

2 1 1 0

AWS News(Unofficial)

@awsnews.bsky.social

6 months ago

Amazon CloudWatch Observability Access Manager Now Supports VPC Endpoints AWS announces VPC endpoints for Amazon CloudWatch Observability Access Manager (OAM). CloudWatch OAM enables you to programmatically manage cross-account observability settings within a region. The new VPC endpoints enhance your security posture by keeping traffic between your VPC and CloudWatch OAM within the AWS network, eliminating the need to traverse the public internet. You can use Observability Access Manager to create and manage links between source accounts and monitoring accounts, enabling you to monitor and troubleshoot applications that span multiple accounts within a Region. With the new VPC endpoints, you can establish secure, private, and reliable connections between your VPC and CloudWatch Observability Access Manager. This allows you to maintain private connectivity while managing cross-account observability links and sinks, even from VPCs without internet access. This feature supports both IPv4 and IPv6 addressing, and you can use AWS PrivateLink's built-in security controls—like security groups and VPC endpoint policies—to help secure access to your observability resources. CloudWatch Observability Access Manager VPC endpoints are now available in all https://aws.amazon.com/about-aws/global-infrastructure/regions_az/, the AWS GovCloud (US) Regions, and the China Regions. To start using VPC endpoints for CloudWatch Observability Access Manager, refer to https://docs.aws.amazon.com/general/latest/gr/cloudwatchoam.html for a list of supported Regional endpoints. To learn more about AWS PrivateLink, see https://docs.aws.amazon.com/vpc/latest/privatelink/privatelink-access-aws-services.html.

Amazon CloudWatch Observability Access Manager Now Supports VPC Endpoints

AWS announces VPC endpoints for Amazon CloudWatch Observability Access Manager (OAM). CloudWatch OAM enables you to programmatically manage cross-account observability se...

#AWS #AmazonCloudwatch #AmazonVpc #AwsGovcloudUs

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

6 months ago

Amazon CloudWatch Observability Access Manager Now Supports VPC Endpoints AWS announces VPC endpoints for Amazon CloudWatch Observability Access Manager (OAM). CloudWatch OAM enables you to programmatically manage cross-account observability settings within a region. The new VPC endpoints enhance your security posture by keeping traffic between your VPC and CloudWatch OAM within the AWS network, eliminating the need to traverse the public internet. You can use Observability Access Manager to create and manage links between source accounts and monitoring accounts, enabling you to monitor and troubleshoot applications that span multiple accounts within a Region. With the new VPC endpoints, you can establish secure, private, and reliable connections between your VPC and CloudWatch Observability Access Manager. This allows you to maintain private connectivity while managing cross-account observability links and sinks, even from VPCs without internet access. This feature supports both IPv4 and IPv6 addressing, and you can use AWS PrivateLink's built-in security controls—like security groups and VPC endpoint policies—to help secure access to your observability resources. CloudWatch Observability Access Manager VPC endpoints are now available in all commercial AWS regions, the AWS GovCloud (US) Regions, and the China Regions. To start using VPC endpoints for CloudWatch Observability Access Manager, refer to CloudWatch OAM endpoints for a list of supported Regional endpoints. To learn more about AWS PrivateLink, see accessing AWS services through AWS PrivateLink.

🆕 AWS supports VPC endpoints for CloudWatch, securing traffic within its network for private observability management across accounts, available in all commercial regions and AWS GovCloud.

#AWS #AmazonCloudwatch #AmazonVpc #AwsGovcloudUs

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

6 months ago

AWS extends Traffic Mirroring support on new instance types Amazon Virtual Private Cloud (Amazon VPC) Traffic Mirroring is now supported on additional instance types. Amazon VPC Traffic Mirroring allows you to replicate the network traffic from EC2 instances within your VPC to security and monitoring appliances for use cases such as content inspection, threat monitoring, and troubleshooting. With this release, VPC Traffic Mirroring can be enabled on all Nitro v4 instances. You can see the complete list of instances that support VPC Traffic Mirroring in our https://docs.aws.amazon.com/vpc/latest/mirroring/what-is-traffic-mirroring.html#supported-instance-types. You can see the complete list of instances built on different Nitro system versions in our https://docs.aws.amazon.com/ec2/latest/instancetypes/ec2-nitro-instances.html. VPC Traffic Mirroring is supported on these additional instance types in all regions. To learn more about VPC Traffic Mirroring, please visit the VPC Traffic Mirroring https://docs.aws.amazon.com/vpc/latest/mirroring/what-is-traffic-mirroring.html.

AWS extends Traffic Mirroring support on new instance types

Amazon Virtual Private Cloud (Amazon VPC) Traffic Mirroring is now supported on additional instance types. Amazon VPC Traffic Mirroring allows you to replicate the network tra...

#AWS #AmazonVirtualPrivateCloud #AmazonVpc #AwsGovcloudUs

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

6 months ago

AWS extends Traffic Mirroring support on new instance types Amazon Virtual Private Cloud (Amazon VPC) Traffic Mirroring is now supported on additional instance types. Amazon VPC Traffic Mirroring allows you to replicate the network traffic from EC2 instances within your VPC to security and monitoring appliances for use cases such as content inspection, threat monitoring, and troubleshooting. With this release, VPC Traffic Mirroring can be enabled on all Nitro v4 instances. You can see the complete list of instances that support VPC Traffic Mirroring in our documentation. You can see the complete list of instances built on different Nitro system versions in our AWS Nitro Systems documentation. VPC Traffic Mirroring is supported on these additional instance types in all regions. To learn more about VPC Traffic Mirroring, please visit the VPC Traffic Mirroring documentation.

🆕 AWS extends Traffic Mirroring support to all Nitro v4 instances, enabling network traffic replication for security and monitoring in Amazon VPC. Full list in documentation.

#AWS #AmazonVirtualPrivateCloud #AmazonVpc #AwsGovcloudUs

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

6 months ago

Amazon VPC IPAM adds in-console CloudWatch alarm management Today, Amazon Web Services announced improved Amazon CloudWatch alarm integration for Amazon VPC IP Address Manager (IPAM). This enhancement provides better visibility and management of existing CloudWatch alarms directly from the IPAM console. With this new integration, you can quickly identify potential IP address management issues and take proactive actions across your organization. The enhanced integration brings IPAM-related CloudWatch alarms directly into the IPAM console, providing a unified view of alarm states across all IPAM pages. This visibility enables quick response to potential IP address management issues. You can now create CloudWatch alarms directly from the IPAM console - clicking the ‘Create Alarm’ option redirects you to CloudWatch with relevant fields pre-populated, streamlining IP usage alert setup. A new resource-level "Alarms" tab offers comprehensive visibility into all alarms associated with specific IPAM resources, making it easier to manage and monitor your IP address space effectively. This improved integration is particularly valuable for networking teams managing IP address spaces, as it helps prevent issues through better visibility and easier management of existing alarms. The console also provides proactive monitoring suggestions for resources without associated alarms, helping ensure comprehensive monitoring coverage across your IP address management infrastructure. This feature is now available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where Amazon VPC IPAM is supported, including AWS China Regions, and AWS GovCloud (US) Regions. To learn more about monitoring IPAM with CloudWatch, view the https://docs.aws.amazon.com/vpc/latest/ipam/cloudwatch-ipam.html. For details on pricing, refer to the IPAM tab on the https://aws.amazon.com/vpc/pricing/.

Amazon VPC IPAM adds in-console CloudWatch alarm management

Today, Amazon Web Services announced improved Amazon CloudWatch alarm integration for Amazon VPC IP Address Manager (IPAM). This enhancement provides better visibility and management o...

#AWS #AmazonCloudwatch #AwsGovcloudUs #AmazonVpc

0 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

6 months ago

Amazon VPC IPAM adds in-console CloudWatch alarm management Today, Amazon Web Services announced improved Amazon CloudWatch alarm integration for Amazon VPC IP Address Manager (IPAM). This enhancement provides better visibility and management of existing CloudWatch alarms directly from the IPAM console. With this new integration, you can quickly identify potential IP address management issues and take proactive actions across your organization. The enhanced integration brings IPAM-related CloudWatch alarms directly into the IPAM console, providing a unified view of alarm states across all IPAM pages. This visibility enables quick response to potential IP address management issues. You can now create CloudWatch alarms directly from the IPAM console - clicking the ‘Create Alarm’ option redirects you to CloudWatch with relevant fields pre-populated, streamlining IP usage alert setup. A new resource-level "Alarms" tab offers comprehensive visibility into all alarms associated with specific IPAM resources, making it easier to manage and monitor your IP address space effectively. This improved integration is particularly valuable for networking teams managing IP address spaces, as it helps prevent issues through better visibility and easier management of existing alarms. The console also provides proactive monitoring suggestions for resources without associated alarms, helping ensure comprehensive monitoring coverage across your IP address management infrastructure. This feature is now available in all AWS Regions where Amazon VPC IPAM is supported, including AWS China Regions, and AWS GovCloud (US) Regions. To learn more about monitoring IPAM with CloudWatch, view the CloudWatch IPAM documentation. For details on pricing, refer to the IPAM tab on the Amazon VPC Pricing Page.

🆕 Amazon VPC IPAM now integrates CloudWatch alarms for better IP management. Create and monitor alarms directly from IPAM for specific resources. Available globally. See CloudWatch IPAM docs for details.

#AWS #AmazonCloudwatch #AwsGovcloudUs #AmazonVpc

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

6 months ago

Amazon VPC now supports IPv4 ingress routing for large IP Pools Amazon VPC now allows customers to route inbound internet traffic destined for large pools of public IP addresses, to a single elastic network interface (ENI) within a VPC. Prior to this enhancement, internet gateways only accepted traffic destined to public IP addresses that were associated with network interfaces in the VPC. There are limits to the number of IP addresses that can be associated with network interfaces. These limits depend on the instance type and can be found in our https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AvailableIpPerENI.html. There are use cases in Telco, Internet of Things (IoT) and other industries that require customers to route inbound traffic destined for public IP pools, larger than the allowed limits, to a single network interface. Customers would earlier perform address translation to consolidate traffic for such large number of IP addresses. This enhancement removes the need to perform address translation on inbound internet connections for these Telco and IoT use cases. Customers can bring their own public IP pools (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-byoip.html) and configure their VPC Internet Gateway to accept traffic belonging to this BYOIP pool and route it to a network interface. They can also use this feature with VPC Route Server and dynamically update their routes in events of failure. Refer to our public https://docs.aws.amazon.com/vpc/latest/userguide/dynamic-routing-route-server.html for details on VPC Route Server. This enhancement is now available across all AWS commercial, AWS China and GovCloud regions. To learn more about this feature, please refer to our https://docs.aws.amazon.com/vpc/latest/userguide/advanced-routing.html.

Amazon VPC now supports IPv4 ingress routing for large IP Pools

Amazon VPC now allows customers to route inbound internet traffic destined for large pools of public IP addresses, to a single elastic network interface (ENI) within a VPC.

Prior to...

#AWS #AmazonVirtualPrivateCloud #AmazonVpc

0 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

6 months ago

Amazon VPC now supports IPv4 ingress routing for large IP Pools Amazon VPC now allows customers to route inbound internet traffic destined for large pools of public IP addresses, to a single elastic network interface (ENI) within a VPC. Prior to this enhancement, internet gateways only accepted traffic destined to public IP addresses that were associated with network interfaces in the VPC. There are limits to the number of IP addresses that can be associated with network interfaces. These limits depend on the instance type and can be found in our documentation. There are use cases in Telco, Internet of Things (IoT) and other industries that require customers to route inbound traffic destined for public IP pools, larger than the allowed limits, to a single network interface. Customers would earlier perform address translation to consolidate traffic for such large number of IP addresses. This enhancement removes the need to perform address translation on inbound internet connections for these Telco and IoT use cases. Customers can bring their own public IP pools (BYOIP documentation) and configure their VPC Internet Gateway to accept traffic belonging to this BYOIP pool and route it to a network interface. They can also use this feature with VPC Route Server and dynamically update their routes in events of failure. Refer to our public documentation for details on VPC Route Server. This enhancement is now available across all AWS commercial, AWS China and GovCloud regions. To learn more about this feature, please refer to our documentation.

🆕 Amazon VPC now supports IPv4 ingress routing for large IP pools, allowing inbound traffic to large public IP sets to route to a single ENI, eliminating the need for address translation for Telco and IoT use cases. Available in all AWS regions.

#AWS #AmazonVirtualPrivateCloud #AmazonVpc

0 0 0 0

Posts tagged #AmazonVpc