Could the Auto-generated S3 bucket be optional, and configurable by name. Currently, the auto-generated bucket forces a S3 Bucket with the name of: serverlessrepo-newrelic-s3-log-in-sourcelogbucket-XXXXXXXXXXXXX. If the user decided to take advantage of a S3 bucket created by the serverlessrepo Application, it would be nice if the Parameters took a value to customize this generated S3 Buckets name. Similarly, If the user decided to not use the generated S3 Bucket, the choice to auto-create a S3 Bucket should be optional, and we should be able to specify a pre-existing S3 Bucket to use via the serverlessrepo Application Template Parameters to use with the serverlessrepo-NewRelic-s3-log-ingestion Lambda Function.
Could the Auto-generated S3 bucket be optional, and configurable by name. Currently, the auto-generated bucket forces a S3 Bucket with the name of:
serverlessrepo-newrelic-s3-log-in-sourcelogbucket-XXXXXXXXXXXXX. If the user decided to take advantage of a S3 bucket created by theserverlessrepoApplication, it would be nice if the Parameters took a value to customize this generated S3 Buckets name. Similarly, If the user decided to not use the generated S3 Bucket, the choice to auto-create a S3 Bucket should be optional, and we should be able to specify a pre-existing S3 Bucket to use via theserverlessrepoApplication Template Parameters to use with theserverlessrepo-NewRelic-s3-log-ingestionLambda Function.