anchor.diff:  (`AWS_ACCESS_KEY`, `AWS_SECRET_ACCESS_KEY`) needs to be passed to the EC2 instance on startup, but rather the
   credentials of the user which started the EC2 instance are used.
   
  -There's a configuration `./conf/aws.xml` which has this protocol in it:
  +There's a configuration `./conf/aws.xml` which includes this protocol:
   
   [source,xml]
   ----
  
positive.code: `S3_PING` is discussed in the JGroups manual at http://www.jgroups.org/manual4/index.html#_s3_ping.
  
  ==== TCPGOSSIP and GossipRouter
  
  ==== TCPPING
  
  ==== Route 53
  
  ==== Elastic IP addresses
  
  ==== Block of addresses in VPC
  
  
  === Publishing ports used by JGroups
  
  
  
  
  
negative.code: 
  Therefore, we have to resort to other ways of running discovery. They're discussed in the following sections.
  
  [[NATIVE_S3_PING]]
  ==== NATIVE_S3_PING
  
  NATIVE_S3_PING is a separate protocol developed at https://github.com/jgroups-extras/native-s3-ping. It uses the
  