reference deployment

VMware Tanzu Application Service on AWS

A modern runtime for Java, .NET, and Node.js apps

This Quick Start automatically deploys Tanzu Application Service (TAS)—previously known as Pivotal Cloud Foundry (PCF)—into your Amazon Web Services (AWS) account.

TAS is a cloud-native platform for deploying and operating modern applications. You can build your applications in Spring or .NET, and then deploy your code to the platform. TAS does the rest, handling much of the operational complexity for you.

With TAS on AWS, you can:

  • Deploy and run your Spring Boot apps with little or no modification. Most .NET apps that use the Hosted Web Core framework can be immediately migrated to TAS.
  • Instantly reap operational efficiencies with built-in monitoring, logging, rapid scaling, and four layers of high availability.
  • Use the TAS Service Broker for AWS to enhance your applications with AWS services such as Amazon Relational Database Service (Amazon RDS), Amazon Simple Storage Service (Amazon S3), Amazon DynamoDB, and Amazon Simple Queue Service (Amazon SQS).

This Quick Start was developed by VMware in collaboration with AWS. VMware is an APN Partner.

  •  What you'll build
  •  How to deploy
  •  Cost and licenses
  •  What you'll build
  • The Quick Start deploys and configures the following components:

    • A virtual private cloud (VPC) configured with two public and four private subnets. The Quick Start builds a new VPC for your deployment; it doesn’t support deployments into an existing VPC.
    • An internet gateway to provide access to the internet.
    • In a public subnet, a network address translation (NAT) instance to allow outbound internet connectivity for resources in the private subnets.
    • Three Elastic Load Balancing (ELB) load balancers.
    • All required TAS components, including Bootstrap, Ops Manager, BOSH Director, and TAS instances. 
    • S3 buckets for storage of buildpacks, droplets, packages, and resources. 
    • Amazon RDS MySQL DB instance and alternate instance for TAS internal use.
    • Amazon Route 53 for creating a hosted zone for your TAS domain.
    • Secure Shell (SSH) access to application containers.
    • Optional support for TCP routing with TCP routers.
  •  How to deploy
  • Before you deploy the Quick Start, check the prerequisites listed in the deployment guide. You can then build your TAS environment on AWS by following these steps:

    1. If you don't already have an AWS account, sign up at
    2. Create a hosted zone for your TAS domain in Amazon Route 53.
    3. Import the SSL certificate for your domain into AWS Certificate Manager.
    4. Launch the Quick Start and specify the necessary parameters. The deployment takes 2.5 to 3 hours. (For a list of supported AWS Regions, see the AWS CloudFormation template.)
    5. Test the deployment by accessing the TAS resources provisioned in your AWS account.

    The Quick Start includes parameters that you can customize. For example, you can change the deployment size and customize the network, DNS, TAS, and Amazon RDS configuration.

    Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on the Quick Start.  

  •  Cost and licenses
  • The Quick Start includes a 90-day free evaluation of TAS on AWS. You can use the trial version to independently evaluate the platform and its capabilities, or contact VMware for a proof of concept installation.

    During the Quick Start deployment, you will need to accept the TAS End User License Agreement (EULA). You must also supply a VMware Tanzu API token.

    This Quick Start deploys a recent major version of TAS by default. However, there could be a delay before a new version of the TAS that was published in the VMware Tanzu Network becomes available in the Quick Start.

    You are responsible for the cost of the AWS infrastructure, storage, and data services used while running this Quick Start reference deployment. There is no additional cost for using the Quick Start. The AWS CloudFormation template for this Quick Start includes configuration parameters for TAS. Some of these settings, such as the deployment size, will affect the cost of deployment.