anchor.diff:  		 <jdbc:pool-attributes initialSize="1" " maxActive="200" minIdle="10"
            		testOnBorrow="true" validationQuery="SELECT 1" />
    </jdbc:dataSource>
  +
  +</beans>
   ----
   
   A full list of all configuration attributes with their value is available http://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html[here]
  
positive.code: 
  The Spring Cloud AWS JDBC module comes as a standalone module and can be importet with the following dependency declaration
  
  [source,xml]
  ----
  <dependency>
   <groupId>org.springframework.cloud</groupId>
   <artifactId>spring-cloud-aws-jdbc</artifactId>
   <version>1.0.0.RELEASE</version>
  </dependency>
  ----
  
  
negative.code: ====
  The database tag _aws:cloudformation:aws:cloudformation:stack-name_ is a default tag that is created if the
  database is configured using CloudFormation.
  ====
  
  ==Sending mails
  Spring has an built-in support to send E-Mail based on the http://www.oracle.com/technetwork/java/javamail/index.html[Java Mail API]
  to avoid any static method calls while using the Java Mail API and thus supporting the testability of application.
  Spring Cloud AWS supports the http://aws.amazon.com/de/ses/[Amazon SES] as an implementation of the Spring Mail abstraction.
  
  As a result Spring Cloud AWS users can decide to use the Spring Cloud AWS implementation of the Amazon SES service or
  use the standard Java Mail API based implementation that send mails via SMTP to Amazon SES
  
  [TIP]
  ====
  It is preferred to use the Spring Cloud AWS implementation instead of the SMTP mainly for performance reasons.
  Spring Cloud AWS uses one API call to send a mail message, the SMTP protocol makes multiple requests (EHLO, MAIL FROM, RCPT TO, DATA, QUIT)
  until it sends an e-mail
  ====
  
  === Configuring the mail sender
  Spring Cloud AWS provides a XML element to configure a Spring _org.springframework.mail.MailSender_ implementation for the
  client to be used. The default mail sender work without a Java Mail dependency and is capable of sending messages without
  attachment as simple mail messages. A configuration with the necessary elements will look like this
  
  
  [source,xml,indent=0]
  ----
  <beans xmlns:aws-mail="http://www.springframework.org/schema/cloud/aws/mail"
     xsi:schemaLocation="http://www.springframework.org/schema/cloud/aws/mail
        http://www.springframework.org/schema/cloud/aws/mail/spring-cloud-aws-mail-1.0.xsd">
  
  	<aws-context:context-credentials>
  	  ..
  	</aws-context:context-credentials>
  
  	<aws-context:context-region region="EU_WEST_1" />
  
  	<aws-mail:mail-sender id="testSender" />
  
  </beans>
  ----
  
  === Sending simple mails
  Application developers can inject the _MailSender_ into their application code and directly send simple text based e-mail
   messages. The sample below demonstrates the creation of a simple mail message.
  
  [source,java,indent=0]
  ----
  public class MailSendingService {
  
  	private MailSender mailSender;
  
  	@Autowired
  	public MailSendingService(MailSender mailSender){
  		this.mailSender = mailSender;
  	}
  
  	public void sendMailMessage() {
  		SimpleMailMessage simpleMailMessage = new SimpleMailMessage();
  		simpleMailMessage.setFrom("foo@bar.com");
  		simpleMailMessage.setTo("bar@baz.com");
  		simpleMailMessage.setSubject("test subject");
  		simpleMailMessage.setText("test content");
  		this.mailSender.send(simpleMailMessage);
  	}
  }
  ----
  
  
  === Sending attachments
  Sending attachments with e-mail protocol requires mime messages to be created and sent. In order to create MimeMessages,
  the Java Mail dependency is required and have to be included into the classpath. Spring Cloud AWS will detect the
  dependency and create a _org.springframework.mail.javamail.JavaMailSender_ implementation that allows to create and
  build mime messages and send them. A dependency configuration for the Java Mail api is the only change in the configuration
  which is shown below.
  
  [source,xml,indent=0]
  ----
  <dependency>
  	<groupId>javax.mail</groupId>
  	<artifactId>mailapi</artifactId>
  	<version>1.4.1</version>
  	<exclusions>
  		<!-- exclusion because we are running on Java 1.7 that includes the activation API by default-->
  		<exclusion>
  			<artifactId>activation</artifactId>
  			<groupId>javax.activation</groupId>
  		</exclusion>
  	</exclusions>
  </dependency>
  ----
  
  [HINT]
  ====
  Even though there is a dependency to the Java Mail API there is still the Amazon SES API used underneath to send mail
  messages. There is no http://docs.aws.amazon.com/ses/latest/DeveloperGuide/send-email-smtp.html[SMTP setup] required
  on the Amazon AWS side.
  ====
  
  Sending the mail requires the application developer to use the _JavaMailSender_ to send an E-Mail that is shown in the example
  below.
  
  [source,java,indent=0]
  ----
  public class MailSendingService {
  
  
  	private JavaMailSender mailSender;
  
      @Autowired
  	public MailSendingService(JavaMailSender mailSender){
  		this.mailSender = mailSender;
  	}
  
  	public void sendMailMessage() {
  		this.mailSender.send(new MimeMessagePreparator() {
  
          			@Override
          			public void prepare(MimeMessage mimeMessage) throws Exception {
          				MimeMessageHelper helper = new MimeMessageHelper(mimeMessage, true, "UTF-8");
          				helper.addTo("foo@bar.com");
          				helper.setFrom("bar@baz.com");
          				helper.addAttachment("test.txt", new ByteArrayResource("attachment content".getBytes("UTF-8")));
          				helper.setSubject("test subject with attachment");
          				helper.setText("mime body", false);
          			}
          		});
  	}
  }
  ----
  
  === Configuring regions
  Amazon SES is not available in all http://docs.aws.amazon.com/ses/latest/DeveloperGuide/regions.html[regions] of the
  Amazon Webservices cloud. Therefore an application hosted and operated in a region that does not support the mail
  service will produce an error while using the mail service. Therefore the region must be overridden for the mail
  sender configuration. The example below shows a typical combination of a region (EU-CENTRAL-1) that does not provide
  and SES service, the client is overridden to usa a valid region EU-WEST-1.
  
  [source,xml,indent=0]
  ----
  <beans ...>
  
   <aws-context:context-region region="EU_CENTRAL_1" />
   <aws-mail:mail-sender id="testSender"  region="EU_WEST_1"/>
  
  </beans>
  ----
  
  === Authenticating E-Mails
  To avoid any spam attacks on the Amazon SES mail service, application without production access must
  http://docs.aws.amazon.com/ses/latest/DeveloperGuide/verify-email-addresses.html[verify] each
  e-mail receiver otherwise the mail sender will throw an _com.amazonaws.services.simpleemail.model.MessageRejectedException_.
  
  http://docs.aws.amazon.com/ses/latest/DeveloperGuide/request-production-access.html[Production access] can be requested
   and will disable the need for mail address verification.
  
  