AWS and VXLAN

Via Cloudwatch you can set up autoscaling , by any metric you want , Cpu utilization  latency , network in/out , Disk IO ...

You create an Alarm on the AWS management console ,on the alarm Interface Select EC2 aggregated by auto scaling group , type your auto scaling group , choose your metrics ...

Can leverage exist capability like
- AWS CloudWatch serves to creates alarm and triggers.
- AWS OpsWorks users leverage Chef recipes to automate operations like software configurations, package installations, database setups, server scaling, and code deployment.

E.g. OpsWorks sends metrics from all your resources to CloudWatch. The latter alarm that was created to act on upon threshold will for example sends an AWS Simple Notification Service, SNS message when the alarm changes state.

Possible use cases include
http://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/AlarmThatSendsEmail.html

Set Up Amazon Simple Notification Service
Create an Alarm
Send Email Based on CPU Usage Alarm
Send Email Based on Load Balancer Alarm
Send Email Based on Storage Throughput Alarm
Create Alarms That Stop, Terminate, Reboot, or Recover an Instance
Monitor Your Estimated Charges Using Amazon CloudWatch

So it appears the request is more related to this:

“IP Spoofing: Creation of Internet Protocol (IP) packets with a forged source IP address, called spoofing, with the purpose of concealing the identity of the sender or impersonating another computing system”

Is there a workaround to IP spoofing for AWS?

Thanks for the suggestion so far. Sorry for keeping topic but I was misinformed.

The goal is to use OVS with VXLAN to create a tunnel from the on-premise site to AWS's OVS so that the hosts are seen with AWS as neighboring hosts (as if they are on the same subnet).

Is this possible?

Hi Btan,

Do you know who has tested this solution:  https://www.ravellosystems.com/blog/vxlan-nvf-testing-aws-google/.  

Also, have you tried the F5 solution as well?

thanks,