You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The parameters CreateTemplateURLPrefix and LambdaS3BucketNamePrefix have descriptions that seem to direct the user to append . to the end of them. In both cases, the CloudFormation template is already appending AWS::Region to them, so if the user specifies this manually as well, it leads to buckets not being found.
create-cwl-s3-export.template:355 (Note that LambdaS3BucketNamePrefix is not used, that alertlogic-public-repo. is hard-wired as part of the prefix, with the AWS::Region appended to it).
Recommend updating CreateLambdaS3ExportWorkerFunction to use LambdaS3BucketNamePrefix instead of hard-wiring alertlogic-public-repo., and removing instructions from the parameter descriptions directing the user to append . to the end of CreateTemplateURLPrefix and LambdaS3BucketNamePrefix if the current AWS region is going to be automatically appended by the CloudFormation template anyways.
The text was updated successfully, but these errors were encountered:
The parameters CreateTemplateURLPrefix and LambdaS3BucketNamePrefix have descriptions that seem to direct the user to append . to the end of them. In both cases, the CloudFormation template is already appending AWS::Region to them, so if the user specifies this manually as well, it leads to buckets not being found.
cwl-s3-export.template:282
create-cwl-s3-export.template:355 (Note that LambdaS3BucketNamePrefix is not used, that alertlogic-public-repo. is hard-wired as part of the prefix, with the AWS::Region appended to it).
Recommend updating CreateLambdaS3ExportWorkerFunction to use LambdaS3BucketNamePrefix instead of hard-wiring
alertlogic-public-repo.
, and removing instructions from the parameter descriptions directing the user to append . to the end of CreateTemplateURLPrefix and LambdaS3BucketNamePrefix if the current AWS region is going to be automatically appended by the CloudFormation template anyways.The text was updated successfully, but these errors were encountered: