2. Setup

An AWS account is required for building and deploying on AWS. An account can be created here

Necessary tools

• A fully set-up development environment
• AWS CDK (Automatically pre-installed in the development environment)

Setting up the AWS CLI

In order for the AWS CLI to access our account, it must be configured.

In the first step, it makes sense to create a new user for the AWS CLI in order to be able to restrict the rights. The use of the admin account is not recommended.

1. The new user can be created in the Identity and Access Management (IAM) portal at AWS.

2. Click on Create user.

3. Enter a user name of your choice.

4. Select Attach policies directly.

5. Add AdministratorAccess to the policies. This gives you full access to all resources. This is best for development purposes. Users in pipelines should never have AdministratorAccess!.

6. Click on Next.

7. Review your user and click on Create User.

8. The user is now created. Now we need to create access keys for the AWS CLI. To do this, click on the user name to edit the user.

9. Select the Security credentials tab.

10. Scroll down to Access Keys.

11. Click on Create Access Key.

12. Select Command Line Interface (CLI).

13. Confirm the conditions below.

14. The “description tags” can be left empty.

15. Now we receive the required AWS Access Keys.

16. Open a terminal and enter the following command:

    aws configure

    Now enter the access key, then the secret access key, eu-central-1 and leave the last field empty.

    

17. The connection can be checked with the following command:

    aws sts get-caller-identity

    

18. This completes the setup of the AWS CLI. Next, you can continue with the deployment of the application on AWS here.