Moving s3 as a basic quickstart to model AWS resources (#509)

* Moving s3 as a quickstart

* Adding logos and tags

* Updates to content

* Update docs/content/getting-started/quickstarts/quickstart-aws-s3/_index.md

Co-authored-by: Aaron Crawfis <[email protected]>

* Update docs/content/getting-started/quickstarts/quickstart-aws-s3/_index.md

Co-authored-by: Aaron Crawfis <[email protected]>

* Address comments

* Update docs/content/getting-started/quickstarts/quickstart-aws-s3/_index.md

Co-authored-by: Aaron Crawfis <[email protected]>

* Update docs/content/getting-started/quickstarts/quickstart-aws-s3/_index.md

Co-authored-by: Aaron Crawfis <[email protected]>

* Address feedback

* Update s3 bucket

* Remove tags and make aws recipes quickstart hidden

* Update bucket name as parameter

* Add pointer to creating a different IAM role

* Update docs/content/getting-started/quickstarts/quickstart-aws-s3/_index.md

Co-authored-by: Will <[email protected]>

* Update docs/content/getting-started/quickstarts/quickstart-aws-s3/_index.md

Co-authored-by: Will <[email protected]>

* Update docs/content/getting-started/quickstarts/quickstart-aws-s3/_index.md

Co-authored-by: Will <[email protected]>

* Update docs/content/getting-started/quickstarts/quickstart-aws-s3/_index.md

Co-authored-by: Will <[email protected]>

* Address comments

* Update app digram

* Address comments

* Address comments

* Address feedback

* Update docs/content/getting-started/quickstarts/quickstart-aws-s3/_index.md

Co-authored-by: Will <[email protected]>

* Update docs/content/getting-started/quickstarts/quickstart-aws-s3/_index.md

Co-authored-by: Will <[email protected]>

* Update docs/content/getting-started/quickstarts/quickstart-aws-s3/snippets/s3.bicep

Co-authored-by: Aaron Crawfis <[email protected]>

* address feedback

* Trigger Build

* Address feedback

* Address feedback

* Fix spelling

* update ref

* Address comments

* Fix bicep code

* Add further reading section

---------

Co-authored-by: Aaron Crawfis <[email protected]>
Co-authored-by: Will <[email protected]>

.github/config/en-custom.txt

@@ -421,4 +421,5 @@ kubernetesMetadata
 daprSidecar
 manualScaling
 httpGet
-tcp
+tcp
+BucketName

docs/content/author-apps/platform-resources/aws/index.md

@@ -4,7 +4,7 @@ title: "AWS resources"
 linkTitle: "AWS"
 description: "Deploy and connect to AWS resources in your application"
 weight: 900
-categories: "Concept"
+categories: "Overview"
 tags: ["AWS"]
 ---
 

docs/content/author-apps/platform-resources/azure/index.md

@@ -4,7 +4,7 @@ title: "Microsoft Azure resources"
 linkTitle: "Microsoft Azure"
 description: "Deploy and connect to Azure resources in your application"
 weight: 800
-categories: "Concept"
+categories: "Overview"
 tags: ["Azure"]
 ---
 

docs/content/author-apps/platform-resources/kubernetes/index.md

@@ -4,7 +4,7 @@ title: "Kubernetes resources"
 linkTitle: "Kubernetes"
 description: "Deploy and connect to Kubernetes resources in your application"
 weight: 1000
-categories: "Concept"
+categories: "Overview"
 tags: ["Kubernetes"]
 ---
 

docs/content/getting-started/quickstarts/quickstart-aws-s3/_index.md

@@ -0,0 +1,107 @@
+---
+type: docs
+title: "Quickstart: Deploy AWS resources"
+linkTitle: "Deploy AWS resources"
+description: "Learn about how to add AWS resources to your application and deploy them with Radius"
+categories: "Quickstart"
+tags: ["AWS"]
+
+---
+
+This quickstart will show you:
+
+- How to model an AWS S3 resource in Bicep
+- How to use a sample application to interact with AWS S3 bucket
+
+   <img src="./s3appdiagram.png" alt="Screenshot of the sample application to interact with s3 bucket " width=400>
+
+## Prerequisites
+
+- Make sure you have an [AWS account](https://aws.amazon.com/premiumsupport/knowledge-center/create-and-activate-aws-account) and an [IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/getting-started_create-admin-group.html)
+    - [Create an IAM AWS access key](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html) and copy the AWS Access Key ID and the AWS Secret Access Key to a secure location for use later. If you have already created an Access Key pair, you can use that instead.
+- [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html)
+    - Configure your CLI with [`aws configure`](https://docs.aws.amazon.com/cli/latest/reference/configure/index.html), specifying your configuration values
+- [eksctl CLI](https://docs.aws.amazon.com/eks/latest/userguide/eksctl.html)
+- [kubectl CLI](https://kubernetes.io/docs/tasks/tools/install-kubectl/)  
+
+## Step 1: Create an EKS Cluster
+
+Create an EKS cluster by using the `eksctl` CLI. 
+
+```bash
+eksctl create cluster --name <my-cluster> --region=<my-region> 
+```
+
+## Step 2: Create a Radius environment with the AWS cloud provider
+
+Create a [Radius environment]({{< ref "/operations/environments" >}}) where you will deploy your application.
+
+Use the `rad init` command to initialize a new environment into your current kubectl context:
+
+```bash
+rad init
+```
+
+Follow the prompts to install the [control plane services]({{< ref architecture-concept >}}), create an [environment resource]({{< ref "operations/environments" >}}), and create a [local workspace]({{< ref workspaces >}}). You will be asked for:
+
+- **Namespace** - When an application is deployed, this is the namespace where your containers and other Kubernetes resources will be run. By default, this will be in the `default` namespace.
+{{% alert title="💡 About namespaces" color="success" %}} When you initialize a Radius Kubernetes environment, Radius installs the control plane resources within    the `radius-system` namespace in your cluster, separate from your applications. The namespace specified in this step will be used for your application deployments.
+{{% /alert %}}
+- **Add AWS provider** - An [AWS cloud provider]({{<ref providers>}}) allows you to deploy and manage AWS resources as part of your application. Enter 'y' and follow the instructions. Provide a valid AWS region and the values obtained for IAM Access Key ID and IAM Secret Access Keys.
+- **Environment name** - The name of the environment to create. You can specify any name with lowercase letters, such as `myawsenv`.
+
+## Step 3: Create a Bicep file to model AWS Simple Storage Service (S3)
+
+Create a new file called `app.bicep` and add the following bicep code to model an AWS S3 Bucket:
+
+{{< rad file="snippets/s3.bicep" embed=true >}}
+
+Radius uses the [AWS Cloud Control API](https://docs.aws.amazon.com/cloudcontrolapi/latest/userguide/what-is-cloudcontrolapi.html) to interact with AWS resources. This means that you can model your AWS resources in Bicep and Radius will be able to deploy and manage them. You can find the list of supported AWS resources in the [AWS resource library]({{< ref "/author-apps/platform-resources/aws#resource-library" >}}).
+
+## Step 4: Add a Radius container to interact with the AWS S3 Bucket
+
+Open the `app.bicep` and append the following Radius resources:
+
+{{< rad file="snippets/s3app.bicep" embed=true marker="//S3APP" >}}
+
+Your final `app.bicep` file should look like this
+
+{{< rad file="snippets/app.bicep" embed=true >}}
+
+This creates a container that will be deployed to your Kubernetes cluster. This container will interact with the AWS S3 Bucket you created in the previous step.
+
+## Step 5: Deploy the application
+
+1. Deploy your application to your environment:
+
+   ```bash
+   rad deploy ./app.bicep -p aws_access_key_id=<AWS_ACCESS_KEY_ID> -p aws_secret_access_key=<AWS_SECRET_ACCESS_KEY>
+   ```
+   > Replace `<AWS_ACCESS_KEY_ID>` and `<AWS_SECRET_ACCESS_KEY>` with the values obtained from the previous step.
+
+   {{% alert title="Warning" color="warning" %}}It is always recommended to have separate IAM credentials for your container to communicate with S3 or any other data store. 
+   Radius is currently working on supporting [direct connections]({{< ref "appmodel-concept#adding-connections" >}}) to AWS resources so that your container can automatically communicate with the data store securely without having to manage separate credentials for data plane operations{{% /alert %}}
+
+1. Port-forward the container to your machine with [`rad resource expose`]({{< ref rad_resource_expose >}}):
+
+    ```bash
+    rad resource expose containers frontend -a s3app --port 5234
+    ```
+
+1. Visit [localhost:5234](http://localhost:5234/swagger/index.html) in your browser. This is a swagger doc for the sample application. You can use this to interact with the AWS S3 Bucket you created. For example, you can try to upload a file to the bucket via the `/upload` endpoint.
+
+    <img src="./s3app.png" alt="Screenshot of the sample application to interact with s3 bucket " width=900>
+
+## Step 6: Cleanup
+
+1. When you're done with testing, you can use the rad CLI to [delete an environment]({{< ref rad_env_delete.md >}}) to delete all Radius resources running on the EKS Cluster.
+
+2. Cleanup AWS Resources - AWS resources are not deleted when deleting a Radius environment, so make sure to delete all resources created in this reference app to prevent additional charges. You can delete these resources in the AWS Console or via the AWS CLI. Instructions to delete an AWS S3 Bucket are available [here](https://docs.aws.amazon.com/AmazonS3/latest/userguide/delete-bucket.html).
+
+## Further Reading
+
+{{< categorizeby category="Overview" tag="AWS" >}}
+
+{{< categorizeby category="How-To" tag="AWS" >}}
+
+{{< categorizeby category="Reference application" tag="AWS" >}}

docs/content/getting-started/reference-apps/aws-s3/snippets/app.bicep → docs/content/getting-started/quickstarts/quickstart-aws-s3/snippets/app.bicep

@@ -1,17 +1,9 @@
 import aws as aws
-import radius as radius
-
-param environment string
 
-param bucket string
-
-@secure()
-param aws_access_key_id string
-
-@secure()
-param aws_secret_access_key string
+import radius as radius
 
-param aws_region string
+@description('The name of your S3 bucket.The AWS S3 Bucket name must follow the [following naming conventions](https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html).')
+param bucket string ='mys3bucket'
 
 resource s3 'AWS.S3/Bucket@default' = {
   alias: bucket
@@ -20,14 +12,28 @@ resource s3 'AWS.S3/Bucket@default' = {
   }
 }
 
-// get a radius container which uses the s3 bucket
+@description('The environment ID of your Radius application. Set automatically by the rad CLI.')
+param environment string
+
 resource app 'Applications.Core/applications@2022-03-15-privatepreview' = {
-  name: 'webapp'
+  name: 's3app'
   properties: {
     environment: environment
   }
 }
 
+@description('IAM Access Key ID')
+@secure()
+param aws_access_key_id string
+
+@description('IAM Access Key Secret')
+@secure()
+param aws_secret_access_key string
+
+@description('Region where the S3 bucket is created. This will be the same region that you input when adding AWS cloudprovider to an environment in Radius.')
+param aws_region string = 'us-west-2'
+
+// get a radius container which uses the s3 bucket
 resource frontend 'Applications.Core/containers@2022-03-15-privatepreview' = {
   name: 'frontend'
   properties: {

docs/content/getting-started/quickstarts/quickstart-aws-s3/snippets/s3.bicep

@@ -0,0 +1,11 @@
+import aws as aws
+
+@description('The name of your S3 bucket.The AWS S3 Bucket name must follow the naming conventions described at https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html')
+param bucket string ='mys3bucket-${uniqueString(resourceGroup().id)}'
+
+resource s3 'AWS.S3/Bucket@default' = {
+  alias: bucket
+  properties: {
+    BucketName: bucket
+  }
+}

docs/content/getting-started/quickstarts/quickstart-aws-s3/snippets/s3app.bicep

@@ -0,0 +1,53 @@
+import aws as aws
+
+import radius as radius
+
+@description('The name of your S3 bucket.The AWS S3 Bucket name must follow the [following naming conventions](https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html).')
+param bucket string ='mys3bucket'
+
+resource s3 'AWS.S3/Bucket@default' = {
+  alias: bucket
+  properties: {
+    BucketName: bucket
+  }
+}
+
+//S3APP
+@description('The environment ID of your Radius application. Set automatically by the rad CLI.')
+param environment string
+
+resource app 'Applications.Core/applications@2022-03-15-privatepreview' = {
+  name: 's3app'
+  properties: {
+    environment: environment
+  }
+}
+
+@description('IAM Access Key ID')
+@secure()
+param aws_access_key_id string
+
+@description('IAM Access Key Secret')
+@secure()
+param aws_secret_access_key string
+
+@description('Region where the S3 bucket is created. This will be the same region that you input when adding AWS cloud provider to an environment in Radius.')
+param aws_region string = 'us-west-2'
+
+// get a radius container which uses the s3 bucket
+resource frontend 'Applications.Core/containers@2022-03-15-privatepreview' = {
+  name: 'frontend'
+  properties: {
+    application: app.id
+    container: {
+      env: {
+        BUCKET_NAME: s3.properties.BucketName
+        AWS_ACCESS_KEY_ID: aws_access_key_id
+        AWS_SECRET_ACCESS_KEY: aws_secret_access_key
+        AWS_DEFAULT_REGION: aws_region
+      }
+      image: 'radius.azurecr.io/reference-apps/aws:edge'
+    }
+  }
+}
+//S3APP