# AWS account

> The AWS account the aws-* packs talk to, set up the way the AWS SDK is set up for the real services.

Source: https://axx.nimbusxr.us/references/steps/aws-core/

The AWS account the aws-* packs talk to, set up the way the AWS SDK is set up for the real services.

Register the account once with `the {word} aws account with the following properties:`; every aws-* step of the scenario uses it (the first account registered is the default).

| Property | |
| --- | --- |
| `region` | required, e.g. `eu-west-1` |
| `endpoint` | where every service of the account is, instead of AWS: a local emulator such as `http://localhost:4566` (S3 is then addressed by path) |
| `profile` | a profile of the shared AWS config and credentials files |
| `access key id`, `secret access key`, `session token` | static credentials |

Without credentials in the table, the SDK finds them as it always does: the `AWS_*` environment variables, the shared files, then the container or instance role. `AWS_ENDPOINT_URL` is honored too, so the same features run against AWS and against an emulator. Values expand `${env:..}` and `${sys:..}`.

## `aws-core.account`

```gherkin
Given the {word} aws account with the following properties:
  | ... | ... |
```

Register the AWS account the aws-* steps talk to: `region` (required), `endpoint` (an emulator), `profile`, or `access key id` and `secret access key` (and `session token`). Without credentials the SDK's default chain is used.

**Parameters:** `{word}` (one word, no spaces)

**Example:**

```gherkin
Given the parcels aws account with the following properties:
```

_Since 0.1.0._