chore: add docs and e2e for alias (#2379)

<!-- Provide summary of changes -->
Part of #1188.
<!-- Issue number, if available. E.g. "Fixes #31", "Addresses #42, 77" -->

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Author: iamhopaul123

e2e/app-with-domain/app_with_domain_test.go

@@ -15,7 +15,7 @@ import (
 
 var _ = Describe("App With Domain", func() {
 	const domainName = "copilot-e2e-tests.ecs.aws.dev"
-	const svcName = "nginx"
+	const svcName = "hello"
 	const envName = "test"
 
 	Context("when creating a new app", func() {
@@ -70,10 +70,10 @@ var _ = Describe("App With Domain", func() {
 
 		BeforeAll(func() {
 			_, svcInitErr = cli.SvcInit(&client.SvcInitRequest{
-				Name:    svcName,
-				SvcType: "Load Balanced Web Service",
-				Image:   "nginx",
-				SvcPort: "80",
+				Name:       svcName,
+				SvcType:    "Load Balanced Web Service",
+				Dockerfile: "./hello/Dockerfile",
+				SvcPort:    "80",
 			})
 		})
 
@@ -107,7 +107,7 @@ var _ = Describe("App With Domain", func() {
 			// Validate route has the expected HTTPS endpoint.
 			route := svc.Routes[0]
 			Expect(route.Environment).To(Equal(envName))
-			Expect(route.URL).To(Equal(fmt.Sprintf("https://%s.%s.%s.%s", svcName, envName, appName, domainName)))
+			Expect(route.URL).To(Equal(fmt.Sprintf("https://%s", domainName)))
 
 			// Make sure the response is OK.
 			// Since the www app was added second, it should have app appended to the name.
@@ -118,7 +118,7 @@ var _ = Describe("App With Domain", func() {
 				return resp.StatusCode, fetchErr
 			}, "60s", "1s").Should(Equal(200))
 			Eventually(func() (int, error) {
-				httpRoute := fmt.Sprintf("http://%s.%s.%s.%s", svcName, envName, appName, domainName)
+				httpRoute := fmt.Sprintf("http://%s", domainName)
 				resp, fetchErr = http.Get(httpRoute)
 				return resp.StatusCode, fetchErr
 			}, "60s", "1s").Should(Equal(200))

e2e/app-with-domain/copilot/hello/manifest.yml

@@ -0,0 +1,16 @@
+# We're creating the manifest ahead of time as we want to test the service with a count > 1.
+name: hello
+type: Load Balanced Web Service
+image:
+  build: 
+    dockerfile: hello/Dockerfile
+    context: hello
+  port: 80
+
+http:
+  path: '/'
+  alias: copilot-e2e-tests.ecs.aws.dev
+
+cpu: 256
+memory: 512
+count: 1

e2e/app-with-domain/hello/Dockerfile

@@ -0,0 +1,3 @@
+FROM nginx
+EXPOSE 80
+COPY index.html /usr/share/nginx/html

e2e/app-with-domain/hello/index.html

@@ -0,0 +1 @@
+hello

mkdocs.yml

@@ -42,6 +42,7 @@ nav:
       - Scheduled Job: docs/manifest/scheduled-job.en.md
       - Pipeline: docs/manifest/pipeline.en.md
     - Developing:
+      - Domain: docs/developing/domain.en.md
       - Environment Variables: docs/developing/environment-variables.en.md
       - Custom Environment Resources: docs/developing/custom-environment-resources.en.md
       - Secrets: docs/developing/secrets.en.md
@@ -167,8 +168,8 @@ plugins:
     - search
     - redirects:
         redirect_maps:
-            'docs/installing.md': 'docs/getting-started/install.md'
-            'docs/getting-started.md': 'docs/getting-started/first-app-tutorial.md'
+            'docs/installing.md': 'docs/getting-started/install.en.md'
+            'docs/getting-started.md': 'docs/getting-started/first-app-tutorial.en.md'
     - i18n:
         default_language: en
         languages:

site/content/community/get-involved.en.md

@@ -1,6 +1,6 @@
 # Welcome to the AWS Copilot Community ❤️
 
-This is a place to share your [[applications, articles, videos](https://aws.github.io/copilot-cli/community/guides/)] and any other resources related to the AWS Copilot CLI 👩‍✈️.
+This is a place to share your [[applications, articles, videos](../community/guides.en.md)] and any other resources related to the AWS Copilot CLI 👩‍✈️.
 
 You can get involved with the CLI by:
 

site/content/community/get-involved.ja.md

@@ -1,6 +1,6 @@
 AWS Copilot コミュニティへようこそ ❤️
 
-[[アプリケーション、ブログ記事、動画](https://aws.github.io/copilot-cli/community/guides/)] のような AWS Copilot CLI に関連するリソースを皆で共有しましょう👩‍✈️
+[[アプリケーション、ブログ記事、動画](../community/guides.ja.md)] のような AWS Copilot CLI に関連するリソースを皆で共有しましょう👩‍✈️
 
 コミュニティへの参加方法は他にもあります！
 

site/content/docs/commands/secret-init.en.md

@@ -44,7 +44,7 @@ $ copilot secret init --cli-input-yaml input.yml
 ## What's next?
 
 Copilot will create SSM parameters named `/copilot/<app name>/<env name>/secrets/<secret name>`. 
-Using the parameter names, you can then modify the `secrets` section in your [service's](https://aws.github.io/copilot-cli/docs/manifest/backend-service/#secrets) or [job's](https://aws.github.io/copilot-cli/docs/manifest/scheduled-job/#secrets) manifest to reference the secrets that were created. 
+Using the parameter names, you can then modify the `secrets` section in your [service's](../manifest/backend-service.en.md#secrets) or [job's](../manifest/scheduled-job.en.md#secrets) manifest to reference the secrets that were created. 
 
 For example, suppose you have an application `my-app`, and you've created a secret `db_host` in your `prod` and `dev` environments.
 You can modify your service's manifest as follows:

site/content/docs/commands/secret-init.ja.md

@@ -44,7 +44,7 @@ $ copilot secret init --cli-input-yaml input.yml
 ## 作成したシークレットをアプリケーションから参照する
 
 Copilot は `/copilot/<app name>/<env name>/secrets/<secret name>` という名前の SSM パラメータを作成します。
-[Service](https://aws.github.io/copilot-cli/ja/docs/manifest/backend-service/#secrets) あるいは [Job](https://aws.github.io/copilot-cli/ja/docs/manifest/scheduled-job/#secrets) Manifest の `secrets` セクションでこのパラメータ名を指定することでこのシークレットをアプリケーションから参照できます。
+[Service](../manifest/backend-service.ja.md#secrets) あるいは [Job](../manifest/scheduled-job.ja.md#secrets) Manifest の `secrets` セクションでこのパラメータ名を指定することでこのシークレットをアプリケーションから参照できます。
 
 例えば、`my-app` という Application があり、その `prod` と `dev` Environment に `db_host` というシークレットを作ったとすると、Service の Manifest は以下のようになるでしょう。
 ```yaml

site/content/docs/developing/domain.en.md

@@ -0,0 +1,35 @@
+# Domain
+
+As mentioned in the [Application Guide](../concepts/applications.en.md#additional-app-configurations), you can configure the domain name of your app when running `copilot app init`. After deploying your [Load Balanced Web Services](../concepts/services.en.md#load-balanced-web-service), you should be able to access them publicly via
+
+```
+${SvcName}.${EnvName}.${AppName}.${DomainName}
+```
+
+For example:
+
+```
+https:kudo.test.coolapp.example.aws
+```
+
+## How do I configure an alias for my service?
+If you don't like the default domain name Copilot assigns to your service, setting an [alias](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-choosing-alias-non-alias.html) for your service is also very easy. You can add it directly to your [manifest's](../manifest/overview.en.md) `alias` section. The following snippet will set an alias to your service.
+
+``` yaml
+# in copilot/{service name}/manifest.yml
+http:
+  path: '/'
+  alias: example.aws
+```
+
+!!!info
+    Currently, you can only use aliases under the domain you specified when creating the application. We'll make this feature more powerful in the future by allowing you to import certificates and use any aliases!
+
+## What happens under the hood?
+Under the hood, Copilot
+
+* creates a hosted zone in your app account for the new app subdomain `${AppName}.${DomainName}`
+* creates another hosted zone in your env account for the new env subdomain `${EnvName}.${AppName}.${DomainName}`
+* creates and validates an ACM certificate for the env subdomain
+* associates the certificate with your HTTPS listener and redirects HTTP traffic to HTTPS
+* creates an optional A record for your alias