Move Fargate doc to contrib

Signed-off-by: Tim Hansen <timbonicus@gmail.com>

docs/deployment/fargate.md

@@ -1,21 +0,0 @@
----
-id: fargate
-title: Deploying with AWS Fargate and Aurora
-sidebar_label: AWS
-description: How to deploy Backstage on AWS Fargate and Aurora
----
-
-There are any number of ways to deploy backstage containers on AWS. One of the
-simplest from a management and ops perspective is to leverage AWS Fargate and
-Aurora PostgreSQL, where both the container orchestration and database clusters
-are AWS managed services.
-
-However, to use them properly there are a large number of supporting resources
-(VPCs, Security Groups, Load Balancers, Certificate, etc) required. One approach
-is to use [AWS Cloud Development Kit (CDK)](https://aws.amazon.com/cdk/) to
-simplify and automate the creation of the entire infrastructure stack along with
-automating the build and deploy of the container.
-
-Check out the [Backstage On AWS](https://github.com/rbogle/backstage-on-aws)
-repository, for a ready to use CDK application for deploying your custom
-Backstage app onto AWS ECS Fargate and Aurora.

docs/deployment/index.md

@@ -30,7 +30,9 @@ There is also an example of deploying on [Heroku](heroku.md), which only
 requires the first two steps.
 
 An example of deploying Backstage with a [Helm chart](helm.md), a common pattern
-in AWS, is also available.
+in AWS, is also available. There is also a contrib guide to deploying Backstage
+with
+[AWS Fargate and Aurora PostgreSQL](https://github.com/backstage/backstage/blob/master/contrib/docs/tutorials/aws-fargate-deployment.md)
 
 Please consider contributing other deployment guides if you get Backstage set up
 on common infrastructure, it would be a great benefit to the community.