Closed Russ-K closed 3 years ago
There's a section in the developer guide that reads:
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.
There's some more context here about virtual hosting S3. After looking into it, I don't believe we are use any of the virtual hosting settings, but I'd like to try this change out by standing up a dev portal with some periods in the bucket name before approving it.
Issue #, if available: Issue #247 Also partially addresses item 1 from Issue #130
Description of changes: Added validation for the S3 bucket name parameters. Validation uses the Min / Max length properties for length validation and regex for the name format validation. Names must start and end with a lowercase letter or number and may also contain . or -. This should cover the majority of the validation from https://docs.aws.amazon.com/AmazonS3/latest/dev/BucketRestrictions.html I didn't add validation for the following clauses as I think they add a lot of complexity to the regex but offer little (they can be added if required):
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.