Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS::S3::Bucket.InventoryConfiguration Id AllowedPattern #1550

Closed
imrehg opened this issue May 25, 2020 · 1 comment
Closed

AWS::S3::Bucket.InventoryConfiguration Id AllowedPattern #1550

imrehg opened this issue May 25, 2020 · 1 comment
Labels
good first issue Good for newcomers

Comments

@imrehg
Copy link
Contributor

imrehg commented May 25, 2020

cfn-lint version: 0.32.1

Description of issue.

S3 InventoryConfiguration has a required Id property, and having any kind of string there passes the validation:

Resources:
  SomeBucket:
    Type: AWS::S3::Bucket
    Properties:
      ...
      InventoryConfigurations:
        - Id: "my daily inventory"
          ...

This will validate but will fail in the template creation/update phase, with something like:

The XML you provided was not well-formed or did not validate against our published schema (Service: Amazon S3; Status Code: 400; Error Code: MalformedXML; Request ID: ...; S3 Extended Request ID: ...)

It's because there are limitations on the characters that can be used in the Id, based on the AWS console's feedback:

Screenshot 2020-05-25 12 47 17

Would be great to be able to validate that Id for

Name can only contain letters, numbers, underscores, periods, or dashes.

Unfortunately this requirement is not explicit in the docs (at least not obvious)

@PatMyron PatMyron added the good first issue Good for newcomers label May 25, 2020
@PatMyron PatMyron changed the title Fail to lint InventoryConfiguration ID AWS::S3::Bucket.InventoryConfiguration Id AllowedPattern May 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants