AWS announces IPv6 support for EC2 Public DNS names EC2 Public DNS names can now resolve to IPv6 Global Unicast Address (AAAA record) associated with your EC2 instances and Elastic Network Interfaces (ENI). This allows customers to publicly access their IPv6-enabled Amazon EC2 instances over IPv6, using EC2 Public DNS names. Prior to this, EC2 Public DNS name resolved to the Public IPv4 address (A record) associated with the primary ENI of the instance. So, customers adopting IPv6, used the specific IPv6 address instead of a DNS name to access an IPv6-only Amazon EC2 instance, or used a custom domain by creating a hosted zone using Amazon Route 53. IPv6 support for EC2 Public DNS names allows customers to easily access their IPv6-only Amazon EC2 instances, or formulate a migration plan that allows them to access a dual stack instance via IPv6, with a simple DNS cut over. This feature is available in all AWS commercial and AWS GovCloud (US) Regions, and customers can set IPv6 support for EC2 Public DNS using the same VPC settings that customers use to enable IPv4-only EC2 Public DNS name today. To learn more about using IPv6 support for EC2 Public DNS name, please refer to our https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-naming.html.  

AWS announces IPv6 support for EC2 Public DNS names

EC2 Public DNS names can now resolve to IPv6 Global Unicast Address (AAAA record) associated with your EC2 instances and Elastic Network Interfaces (ENI). This allows customers to publicly access the...

#AWS #AmazonEc2 #Ipv6AtAws #AwsGovcloudUs

AWS announces IPv6 support for EC2 Public DNS names EC2 Public DNS names can now resolve to IPv6 Global Unicast Address (AAAA record) associated with your EC2 instances and Elastic Network Interfaces (ENI). This allows customers to publicly access their IPv6-enabled Amazon EC2 instances over IPv6, using EC2 Public DNS names. Prior to this, EC2 Public DNS name resolved to the Public IPv4 address (A record) associated with the primary ENI of the instance. So, customers adopting IPv6, used the specific IPv6 address instead of a DNS name to access an IPv6-only Amazon EC2 instance, or used a custom domain by creating a hosted zone using Amazon Route 53. IPv6 support for EC2 Public DNS names allows customers to easily access their IPv6-only Amazon EC2 instances, or formulate a migration plan that allows them to access a dual stack instance via IPv6, with a simple DNS cut over. This feature is available in all AWS commercial and AWS GovCloud (US) Regions, and customers can set IPv6 support for EC2 Public DNS using the same VPC settings that customers use to enable IPv4-only EC2 Public DNS name today. To learn more about using IPv6 support for EC2 Public DNS name, please refer to our documentation.

🆕 AWS now supports IPv6 for EC2 Public DNS names, allowing IPv6-enabled instances to resolve via AAAA records, simplifying access for IPv6-only instances and dual-stack migrations. Available in all regions, enabling via VPC settings.

#AWS #AmazonEc2 #Ipv6AtAws #AwsGovcloudUs

Amazon MemoryDB now supports Internet Protocol Version 6 (IPv6) https://aws.amazon.com/memorydb/ clusters now support the IPv6 protocol, allowing clients to connect to MemoryDB clusters using IPv6. You can now configure your cluster to accept only IPv6 connections or to accept both IPv4 and IPv6 connections. This allows you to work to meet IPv6 compliance requirements and more efficiently integrate with existing IPv6-based applications. The continued growth of the internet is rapidly depleting available Internet Protocol version 4 (IPv4) addresses. By supporting IPv6, MemoryDB helps customers simplify their network architecture by providing a significantly larger address space and eliminating the need to manage overlapping address spaces in their VPCs. Customers can now standardize their applications on IPv6 and future-proof their infrastructure while maintaining compatibility with existing IPv4 systems through dual-stack support. To get started, create your new MemoryDB cluster using the Amazon Web Services Management Console, CLI, or SDKs and choose which protocol(s) it supports by setting its network type. IPv6 is supported when using Valkey 7 and above, Redis OSS version 6.2 and above, in all AWS global regions and at no additional cost. To learn more about MemoryDB, visit the https://aws.amazon.com/memorydb/ product page.  

Amazon MemoryDB now supports Internet Protocol Version 6 (IPv6)

https://aws.amazon.com/memorydb/ clusters now support the IPv6 protocol, allowing clients to connect to MemoryDB clusters using IPv6. You can now configure your cluster to accept onl...

#AWS #AmazonMemorydb #AwsGovcloudUs #Ipv6AtAws

Amazon MemoryDB now supports Internet Protocol Version 6 (IPv6) Amazon MemoryDB clusters now support the IPv6 protocol, allowing clients to connect to MemoryDB clusters using IPv6. You can now configure your cluster to accept only IPv6 connections or to accept both IPv4 and IPv6 connections. This allows you to work to meet IPv6 compliance requirements and more efficiently integrate with existing IPv6-based applications. The continued growth of the internet is rapidly depleting available Internet Protocol version 4 (IPv4) addresses. By supporting IPv6, MemoryDB helps customers simplify their network architecture by providing a significantly larger address space and eliminating the need to manage overlapping address spaces in their VPCs. Customers can now standardize their applications on IPv6 and future-proof their infrastructure while maintaining compatibility with existing IPv4 systems through dual-stack support. To get started, create your new MemoryDB cluster using the Amazon Web Services Management Console, CLI, or SDKs and choose which protocol(s) it supports by setting its network type. IPv6 is supported when using Valkey 7 and above, Redis OSS version 6.2 and above, in all AWS global regions and at no additional cost. To learn more about MemoryDB, visit the Amazon MemoryDB product page.

🆕 Amazon MemoryDB now supports IPv6, allowing dual-stack or IPv6-only clusters to meet compliance and integrate with IPv6 apps. No additional cost; available globally with Redis 6.2+. Simplify network architecture with a larger address space.

#AWS #AmazonMemorydb #AwsGovcloudUs #Ipv6AtAws

AWS Network Manager and AWS Cloud WAN now support AWS PrivateLink and IPv6 AWS Network Manager and AWS Cloud WAN now support AWS PrivateLink and IPv6 based connectivity to the management endpoint of these services. Using PrivateLink, customers can now access AWS Network Manager or AWS Cloud WAN privately on the AWS network, without going through the public Internet. Additionally, customers can now access these services over IPv6 using dual-stack endpoints. With AWS Cloud WAN, you can use a central dashboard and network policies to create a global network that spans multiple locations and networks, allowing you to configure and manage different networks using the same technology. The Cloud WAN central dashboard, powered by AWS Network Manager, generates a complete view of the network to help you monitor network health, security, and performance. AWS Network Manager reduces the operational complexity of managing global networks across AWS and on-premises locations. Previously, you could access AWS Cloud WAN and AWS Network Manager using public IPv4 endpoints only. With this launch, you can now access these services’ APIs/CLI privately, without going through the public Internet. Additionally, these services now support IPv6 endpoints. To learn more about AWS Network Manager, refer https://docs.aws.amazon.com/network-manager/latest/tgwnm/what-are-global-networks.html#nm-privatelink, and for AWS Cloud WAN, refer https://docs.aws.amazon.com/network-manager/latest/cloudwan/what-is-cloudwan.html#cloudwan-privatelink.

AWS Network Manager and AWS Cloud WAN now support AWS PrivateLink and IPv6

AWS Network Manager and AWS Cloud WAN now support AWS PrivateLink and IPv6 based connectivity to the management endpoint of these services. Using PrivateLink,...

#AWS #AwsGovcloudUs #AwsPrivatelink #AwsCloudWan #Ipv6AtAws

AWS Network Manager and AWS Cloud WAN now support AWS PrivateLink and IPv6 AWS Network Manager and AWS Cloud WAN now support AWS PrivateLink and IPv6 based connectivity to the management endpoint of these services. Using PrivateLink, customers can now access AWS Network Manager or AWS Cloud WAN privately on the AWS network, without going through the public Internet. Additionally, customers can now access these services over IPv6 using dual-stack endpoints. With AWS Cloud WAN, you can use a central dashboard and network policies to create a global network that spans multiple locations and networks, allowing you to configure and manage different networks using the same technology. The Cloud WAN central dashboard, powered by AWS Network Manager, generates a complete view of the network to help you monitor network health, security, and performance. AWS Network Manager reduces the operational complexity of managing global networks across AWS and on-premises locations. Previously, you could access AWS Cloud WAN and AWS Network Manager using public IPv4 endpoints only. With this launch, you can now access these services’ APIs/CLI privately, without going through the public Internet. Additionally, these services now support IPv6 endpoints. To learn more about AWS Network Manager, refer documentation, and for AWS Cloud WAN, refer documentation.

🆕 AWS Network Manager and Cloud WAN now support AWS PrivateLink and IPv6 for private, secure connectivity without public Internet access, plus dual-stack endpoints. Simplifies global network management.

#AWS #AwsGovcloudUs #AwsPrivatelink #AwsCloudWan #Ipv6AtAws

Amazon CloudWatch Synthetics adds IPv6 support CloudWatch Synthetics now allows canaries running in a VPC to make outbound requests to IPv6 endpoints allowing monitoring of IPv6-only and dual stack enabled endpoints over IPv6. You can also access CloudWatch Synthetics APIs over both IPv4 and IPv6 through new dual stack compatible regional endpoints. Additionally, PrivateLink access to Synthetics within VPCs is now available over IPv6 connections. Using CloudWatch Synthetics, you can now monitor the availability and performance of websites or microservices accessible via IPv6 endpoints ensuring that end users can use the applications seamlessly irrespective of their network protocol. You can create IPv6 enabled canaries in your VPC using the CLI, CDK, CloudFormation, or the AWS console, and update existing VPC canaries to support dual stack connectivity without making any script changes. You can monitor endpoints external to your VPC by giving the canary internet access and configuring the VPC subnets appropriately. Now you can manage Synthetics resources in environments with IPv6-only networking policies, or access Synthetics APIs via IPv6 without traffic traversing the internet using PrivateLink helping meet security and regulatory requirements. IPv6 support for Synthetics is available in all commercial regions where CloudWatch Synthetics is present at no additional cost to the users. To learn how to configure a IPv6 canary in a VPC see https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Synthetics_Canaries_VPC.html, or click https://docs.aws.amazon.com/general/latest/gr/cw-synthetics_region.html to find dual-stack API management endpoints for Synthetics. See https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Synthetics_Canaries.html and https://catalog.workshops.aws/observability/en-US/aws-native/app-monitoring/synthetics to get started with CloudWatch Synthetics.

Amazon CloudWatch Synthetics adds IPv6 support

CloudWatch Synthetics now allows canaries running in a VPC to make outbound requests to IPv6 endpoints allowing monitoring of IPv6-only and dual stack enabled endpoints over IPv6. You can also access CloudWatch S...

#AWS #AmazonCloudwatch #Ipv6AtAws

Amazon CloudWatch Synthetics adds IPv6 support CloudWatch Synthetics now allows canaries running in a VPC to make outbound requests to IPv6 endpoints allowing monitoring of IPv6-only and dual stack enabled endpoints over IPv6. You can also access CloudWatch Synthetics APIs over both IPv4 and IPv6 through new dual stack compatible regional endpoints. Additionally, PrivateLink access to Synthetics within VPCs is now available over IPv6 connections. Using CloudWatch Synthetics, you can now monitor the availability and performance of websites or microservices accessible via IPv6 endpoints ensuring that end users can use the applications seamlessly irrespective of their network protocol. You can create IPv6 enabled canaries in your VPC using the CLI, CDK, CloudFormation, or the AWS console, and update existing VPC canaries to support dual stack connectivity without making any script changes. You can monitor endpoints external to your VPC by giving the canary internet access and configuring the VPC subnets appropriately. Now you can manage Synthetics resources in environments with IPv6-only networking policies, or access Synthetics APIs via IPv6 without traffic traversing the internet using PrivateLink helping meet security and regulatory requirements. IPv6 support for Synthetics is available in all commercial regions where CloudWatch Synthetics is present at no additional cost to the users. To learn how to configure a IPv6 canary in a VPC see documentation, or click here to find dual-stack API management endpoints for Synthetics. See user guide and One Observability Workshop to get started with CloudWatch Synthetics.

🆕 Amazon CloudWatch Synthetics adds IPv6 support

#AWS #AmazonCloudwatch #Ipv6AtAws

Amazon Location Service now supports Internet Protocol Version 6 (IPv6) Amazon Location Service announces the availability of dual-stack endpoints, enabling customers to connect using Internet Protocol Version 6 (IPv6), Internet Protocol Version 4 (IPv4), or dual-stack clients. These dual-stack endpoints are accessible through a new AWS DNS domain name, while existing Amazon Location Service endpoints remain available to ensure backward compatibility. The transition to IPv6 is essential due to the ongoing expansion of the internet, which is rapidly depleting available IPv4 addresses. With simultaneous support for both IPv4 and IPv6 on Amazon Location Service endpoints, customers can gradually migrate their systems and applications to IPv6-based architectures as needed. This flexibility allows businesses to meet IPv6 compliance requirements while maintaining uninterrupted connectivity through IPv4 for those not yet utilizing IPv6. IPv6 support for Amazon Location Service is now available in all regions where the service is generally available (GA). See https://docs.aws.amazon.com/general/latest/gr/location.html for a full list of supported endpoints and instructions on how to access them via https://docs.aws.amazon.com/sdkref/latest/guide/feature-endpoints.html. To learn more about Amazon Location Service, please visit https://aws.amazon.com/location/ and https://docs.aws.amazon.com/location/.  

Amazon Location Service now supports Internet Protocol Version 6 (IPv6)

Amazon Location Service announces the availability of dual-stack endpoints, enabling customers to connect using Internet Protocol Version 6 (IPv6), Internet Protocol V...

#AWS #AwsGovcloudUs #Ipv6AtAws #AmazonLocationService

Amazon Location Service now supports Internet Protocol Version 6 (IPv6) Amazon Location Service announces the availability of dual-stack endpoints, enabling customers to connect using Internet Protocol Version 6 (IPv6), Internet Protocol Version 4 (IPv4), or dual-stack clients. These dual-stack endpoints are accessible through a new AWS DNS domain name, while existing Amazon Location Service endpoints remain available to ensure backward compatibility. The transition to IPv6 is essential due to the ongoing expansion of the internet, which is rapidly depleting available IPv4 addresses. With simultaneous support for both IPv4 and IPv6 on Amazon Location Service endpoints, customers can gradually migrate their systems and applications to IPv6-based architectures as needed. This flexibility allows businesses to meet IPv6 compliance requirements while maintaining uninterrupted connectivity through IPv4 for those not yet utilizing IPv6. IPv6 support for Amazon Location Service is now available in all regions where the service is generally available (GA). See https://docs.aws.amazon.com/general/latest/gr/location.html for a full list of supported endpoints and instructions on how to access them via https://docs.aws.amazon.com/sdkref/latest/guide/feature-endpoints.html. To learn more about Amazon Location Service, please visit https://aws.amazon.com/location/ and https://docs.aws.amazon.com/location/.  

Amazon Location Service now supports Internet Protocol Version 6 (IPv6)

Amazon Location Service announces the availability of dual-stack endpoints, enabling customers to connect using Internet Protocol Version 6 (IPv6), Internet Protocol V...

#AWS #AwsGovcloudUs #Ipv6AtAws #AmazonLocationService

Amazon Location Service now supports Internet Protocol Version 6 (IPv6) Amazon Location Service announces the availability of dual-stack endpoints, enabling customers to connect using Internet Protocol Version 6 (IPv6), Internet Protocol Version 4 (IPv4), or dual-stack clients. These dual-stack endpoints are accessible through a new AWS DNS domain name, while existing Amazon Location Service endpoints remain available to ensure backward compatibility. The transition to IPv6 is essential due to the ongoing expansion of the internet, which is rapidly depleting available IPv4 addresses. With simultaneous support for both IPv4 and IPv6 on Amazon Location Service endpoints, customers can gradually migrate their systems and applications to IPv6-based architectures as needed. This flexibility allows businesses to meet IPv6 compliance requirements while maintaining uninterrupted connectivity through IPv4 for those not yet utilizing IPv6. IPv6 support for Amazon Location Service is now available in all regions where the service is generally available (GA). See here for a full list of supported endpoints and instructions on how to access them via AWS SDKs and CLI. To learn more about Amazon Location Service, please visit Amazon Location Service Product Page and developer guide.

🆕 Amazon Location Service now supports Internet Protocol Version 6 (IPv6)

#AWS #AwsGovcloudUs #Ipv6AtAws #AmazonLocationService

Announcing Internet Protocol Version 6 (IPv6) support for Recycle Bin Today, AWS announces Internet Protocol version 6 (IPv6) support for Recycle Bin, a data recovery feature that enables restoration of accidental deleted Amazon EBS Snapshots and EBS-backed AMIs. You now have the option of using IPv6 addresses for new and existing endpoints. By moving to IPv6, you can simplify your network stack by running dual-stack Recycle Bin endpoints on a network that supports both IPv4 and IPv6. Customers can create rules in Recycle Bin to retain deleted EBS Snapshots or deregistered EBS-backed AMI for a specific retention time. This capability allows you to immediately recover your deleted snapshots or EBS-backed AMIs when you create volumes or launch instance without a need to roll back to a snapshot or AMI from an earlier point in time. Recovered snapshots or AMIs retain attributes such as prior to deletion and can be used immediately for creating volumes or launching instances. Snapshots and AMIs that are not recovered from the Recycle Bin are permanently deleted upon expiration of the retention time. Recycle Bin with IPv6 and AWS PrivateLink is now available in all AWS Regions including the AWS GovCloud (US) Regions. To learn more about configuring Recycle Bin endpoints for IPv6, please refer to our https://docs.aws.amazon.com/ebs/latest/userguide/rbin-service-endpoints.html.  

Announcing Internet Protocol Version 6 (IPv6) support for Recycle Bin

Today, AWS announces Internet Protocol version 6 (IPv6) support for Recycle Bin, a data recovery feature that enables restoration of accidental deleted Amazon EBS S...

#AWS #Ipv6AtAws #AmazonEbsSnapshotsArchive #AwsPrivatelink

Announcing Internet Protocol Version 6 (IPv6) support for Recycle Bin Today, AWS announces Internet Protocol version 6 (IPv6) support for Recycle Bin, a data recovery feature that enables restoration of accidental deleted Amazon EBS Snapshots and EBS-backed AMIs. You now have the option of using IPv6 addresses for new and existing endpoints. By moving to IPv6, you can simplify your network stack by running dual-stack Recycle Bin endpoints on a network that supports both IPv4 and IPv6. Customers can create rules in Recycle Bin to retain deleted EBS Snapshots or deregistered EBS-backed AMI for a specific retention time. This capability allows you to immediately recover your deleted snapshots or EBS-backed AMIs when you create volumes or launch instance without a need to roll back to a snapshot or AMI from an earlier point in time. Recovered snapshots or AMIs retain attributes such as prior to deletion and can be used immediately for creating volumes or launching instances. Snapshots and AMIs that are not recovered from the Recycle Bin are permanently deleted upon expiration of the retention time. Recycle Bin with IPv6 and AWS PrivateLink is now available in all AWS Regions including the AWS GovCloud (US) Regions. To learn more about configuring Recycle Bin endpoints for IPv6, please refer to our documentation.

🆕 Announcing Internet Protocol Version 6 (IPv6) support for Recycle Bin

#AWS #Ipv6AtAws #AmazonEbsSnapshotsArchive #AwsPrivatelink