Guillaume Coré
2018-09-03 7d48ededb55fdfaa16f887b02d6279a7fc18cef6
refs
author Guillaume Coré <gucore@redhat.com>
Monday, September 3, 2018 14:24 +0200
committer Guillaume Coré <gucore@redhat.com>
Monday, September 3, 2018 14:24 +0200
commit7d48ededb55fdfaa16f887b02d6279a7fc18cef6
tree b66b29290acdcb6928a7c0e9327abfe138321923 tree | zip | gz
parent b5c784120a0c01d19e64129b8dfd93812bddeed1 view | diff
fix s3 bucket name, lowercase

Bucket names must be unique across all existing bucket names in Amazon S3.
Bucket names must comply with DNS naming conventions.
Bucket names must be at least 3 and no more than 63 characters long.
Bucket names must not contain uppercase characters or underscores.
Bucket names must start with a lowercase letter or number.
Bucket names must be a series of one or more labels. Adjacent labels are separated by a single period (.). Bucket names can contain lowercase letters, numbers, and hyphens. Each label must start and end with a lowercase letter or a number.
Bucket names must not be formatted as an IP address (for example, 192.168.5.4).
When you use virtual hosted–style buckets with Secure Sockets Layer (SSL), the SSL wildcard certificate only matches buckets that don't contain periods. To work around this, use HTTP or write your own certificate verification logic. We recommend that you do not use periods (".") in bucket names when using virtual hosted–style buckets.
1 files modified
2 ■■■ changed files
ansible/roles/infra-ec2-template-generate/tasks/main.yml 2 ●●● diff | view | raw | blame | history