Skip to content

Commit

Permalink
Change TTL from 180m to 60m
Browse files Browse the repository at this point in the history
The 180m value was failing with:

```
$ gds aws govuk-production-poweruser --assume-role-ttl 180m ./bin/replicate-mysql.sh whitehall
aws-vault: error: invalid input duration string, try --help
```

A bit of searching suggests that the maximum TTL is now 1 hour:
99designs/aws-vault#263
  • Loading branch information
ChrisBAshton committed Jul 12, 2024
1 parent a930b80 commit b7644ff
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/how-tos.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ There may be times when a full database is required locally. The following scri
You will need to assume-role into AWS using the [gds-cli](https://docs.publishing.service.gov.uk/manual/access-aws-console.html) before running the scripts. For example, to replicate data for Content Publisher, run:

```
gds aws govuk-staging-readonly --assume-role-ttl 180m ./bin/replicate-postgresql.sh content-publisher
gds aws govuk-staging-readonly --assume-role-ttl 60m ./bin/replicate-postgresql.sh content-publisher
```

All the scripts, other than `replicate-elasticsearch.sh`, take the name of the app to replicate data for.
Expand Down

0 comments on commit b7644ff

Please sign in to comment.