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
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.
The text was updated successfully, but these errors were encountered:
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 theserverlessrepo
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 theserverlessrepo
Application Template Parameters to use with theserverlessrepo-NewRelic-s3-log-ingestion
Lambda Function.The text was updated successfully, but these errors were encountered: