Read our blog for the latest insights on sales and marketing Take Me There
Webinar: Use Sugar Data to Easily Generate Complex Documents Register
Webinar: Advanced Calendar Solution for Sugar Register
Starting today, Bring Your Own IP (BYOIP) is available in Asia Pacific (Mumbai), Asia Pacific (Sydney), Asia Pacific (Tokyo), Asia Pacific (Singapore) and South America (Sao Paulo) in additional to EU (Dublin), EU (London), EU (Frankfurt), Canada (Central), US East (N. Virginia), US East (Ohio), and US West (Oregon) AWS Regions. Also starting today, BYOIP will support onboarding of IP addresses registered to Asia Pacific Network Information Center (APNIC) in addition to American Registry for Internet Numbers (ARIN) and Réseaux IP Européens Network Coordination Centre (RIPE).
BYOIP allows you to bring your own publicly-routable IP address prefixes to AWS and advertise them on the internet. You can create Elastic IP addresses from your BYOIP address prefix and use them with AWS resources such as EC2 instances, Network Load Balancers, and NAT gateways. The Elastic IP addresses you create from BYOIP address prefixes work the same way as Elastic IP addresses you get from AWS. BYOIP also allows you to minimize your downtime during migration by simultaneously advertising your IP address prefix from AWS and withdrawing it from the current location.
If your applications are using trusted IP addresses that your partners and customers have whitelisted in their firewalls, you can now move these applications to AWS without requiring your partners and customers to change their IP address whitelists. BYOIP is also useful for applications that rely on IP address reputation to allow traffic from your endpoints to reach intended recipients, such as commercial email services. Some legacy applications have hard-coded IP address dependencies. Bring Your Own IP enables you to migrate such applications to AWS with minimal disruptions.
There is no additional charge to use the BYOIP feature. Also, you don’t have to pay for Elastic IP addresses that you create from BYOIP address prefixes.
For more information about this feature, visit the BYOIP documentation.
Beginning today, you can associate private hosted zones with the same Virtual Private Cloud even if they have overlapping namespaces (for example, if one of those hosted zones is a subdomain of the other, such as acme.example.com and example.com). Support for overlapping namespaces makes it easy to manage permissions across your organization. For example, it lets a central team in your organization manage a parent hosted zone (such as example.com) while allowing independent teams to manage their own subdomains of that zone (such as acme.example.com and zenith.example.com).
Amazon Virtual Private Cloud (VPC) now supports IPv6 traffic over Inter-Region VPC Peering. With this launch, your resources in different AWS regions, can communicate with each other using IPv6 addresses without requiring gateways, VPN connections, or separate physical hardware. Inter-Region VPC Peering encrypts inter-region traffic with no single point of failure or bandwidth bottleneck. Traffic using Inter-Region VPC Peering always stays on the AWS global network and never traverses the public internet.
To get started, you need to setup an inter-region VPC Peering connection between two dual stack VPCs in different AWS Regions and add routes pointing to the V6 CIDRs of the peered VPCs. Resources in these VPCs can then communicate with each other using IPv6 addresses.
Data sent over Inter-Region VPC Peering connections is charged at the standard inter-region data transfer rates.
For more information, see the documentation on Amazon VPC peering.
Starting today, Amazon Virtual Private Cloud (Amazon VPC) Traffic Mirroring is available in Asia Pacific (Sydney) and Asia Pacific (Hong Kong) regions.
Amazon VPC Traffic Mirroring allows customers to replicate the network traffic from an EC2 instance within their VPC and forward that traffic to security and monitoring appliances for use cases such as content inspection, threat monitoring, and troubleshooting.
With this launch, Amazon VPC Traffic Mirroring is now available in 19 AWS regions. You can learn more about this feature by reading Amazon's documentation.
You can now enable your Amazon Kinesis Data Analytics for Java applications to access resources within your Amazon Virtual Private Cloud (Amazon VPC). This feature enables you to use your streaming applications to read and write data from resources within your VPCs like Amazon Elasticsearch Service clusters, Amazon RDS databases, Amazon Redshift data warehouses, Amazon Managed Streaming for Apache Kafka (Amazon MSK) clusters, and more.
Amazon Kinesis Data Analytics is the easiest way to analyze streaming data, gain actionable insights, and respond to your business and customer needs in real time. With Amazon Kinesis Data Analytics, SQL users and Java developers (leveraging Apache Flink) build streaming applications to transform and analyze data in real time.
You can configure your Amazon Kinesis Data Analytics for Java application to connect to private subnets in a VPC using the AWS Management Console or AWS SDKs. You add VPC connectivity to your application by configuring one to many security groups and subnet identifiers associated with the VPCs you want to access resources in. Amazon Kinesis Data Analytics creates one or more elastic network interfaces in one of the subnets provided in the application’s VPC configuration.
For a list of where Amazon Kinesis Data Analytics is available, please see the AWS Region Table. This capability is available in US East (N. Virginia), US West (Oregon), EU (Frankfurt), and EU (Ireland). The capability is coming soon in all other regions where Amazon Kinesis Data Analytics is available.
You can learn about accessing resources within a VPC in the Amazon Kinesis Data Analytics Developer Guide for Java Applications.
You can now use Amazon CloudWatch to monitor metrics related to VPC Traffic Mirroring. You can collect information such as the amount of traffic mirrored or not mirrored on your network interface that is part of a traffic mirror session. You can also set up CloudWatch Alarms to receive notifications on any metrics crossing pre-defined thresholds. To get started with these metrics, see Monitoring Mirrored Traffic Using Amazon CloudWatch.
Amazon VPC Traffic Mirroring allows customers to replicate the network traffic from an EC2 instance within their VPC and forward that traffic to security and monitoring appliances for use cases such as content inspection, threat monitoring, and troubleshooting. You can read more about Amazon VPC Traffic Mirroring in Amazon's documentation.