Merge branch 'docs-aws-wrapper-31167' into 'master'

Added AWS Docker image documentation

See merge request gitlab-org/gitlab!21509

doc/ci/README.md

@@ -127,6 +127,7 @@ Its feature set is listed on the table below according to DevOps stages.
 | [GitLab Pages](../user/project/pages/index.md) | Deploy static websites. |
 | [GitLab Releases](../user/project/releases/index.md) | Add release notes to Git tags. |
 | [Review Apps](review_apps/index.md) | Configure GitLab CI/CD to preview code changes. |
+| [Cloud deployment](cloud_deployment/index.md) | Deploy your application to a main cloud provider. |
 |---+---|
 | **Secure** ||
 | [Container Scanning](../user/application_security/container_scanning/index.md) **(ULTIMATE)** | Check your Docker containers for known vulnerabilities.|

doc/ci/cloud_deployment/index.md

+---
+type: howto
+---
+
+# Cloud deployment
+
+Interacting with a major cloud provider such as Amazon AWS may have become a much needed task that's
+part of your delivery process. GitLab is making this process less painful by providing Docker images
+that come with the needed libraries and tools pre-installed.
+By referencing them in your CI/CD pipeline, you'll be able to interact with your chosen
+cloud provider more easily.
+
+## AWS
+
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/31167) in GitLab 12.6.
+
+GitLab's AWS Docker image provides the [AWS Command Line Interface](https://aws.amazon.com/cli/),
+which enables you to run `aws` commands. As part of your deployment strategy, you can run `aws` commands directly from
+`.gitlab-ci.yml` by specifying GitLab's AWS Docker image.
+
+Some credentials are required to be able to run `aws` commands:
+
+1. Sign up for [an AWS account](https://docs.aws.amazon.com/IAM/latest/UserGuide/getting-set-up.html) if you don't have one yet.
+1. Log in onto the console and create [a new IAM user](https://console.aws.amazon.com/iam/home#/home).
+1. Select your newly created user to access its details. Navigate to **Security credentials > Create a new access key**.
+
+   NOTE: **Note:**
+   A new **Access key ID** and **Secret access key** pair will be generated. Please take a note of them right away.
+
+1. In your GitLab project, go to **Settings > CI / CD**. Set the Access key ID and Secret access key as [environment variables](../variables/README.md#gitlab-cicd-environment-variables), using the following variable names:
+
+   | Env. variable name      | Value                    |
+   |:------------------------|:-------------------------|
+   | `AWS_ACCESS_KEY_ID`     | Your "Access key ID"     |
+   | `AWS_SECRET_ACCESS_KEY` | Your "Secret access key" |
+
+1. You can now use `aws` commands in the `.gitlab-ci.yml` file of this project:
+
+   ```yml
+   deploy:
+     stage: deploy
+     image: registry.gitlab.com/gitlab-org/cloud-deploy:latest
+     script:
+       - aws s3 ...
+       - aws create-deployment ...
+   ```