How to opt-out of applying s3LifecycleConfigurationRules if s3 bucket already exists

[Tim0401]

I am using artillery to run tests with Playwright and Fargate.
Each time I ran the test, the LifecycleConfiguration of the s3 bucket was overwritten, but the behavior conflicted with our company policy.

artillery/packages/artillery/lib/platform/aws-ecs/ecs.js

Lines 23 to 57 in 4cf8d05

	class PlatformECS {
	constructor(script, payload, opts, platformOpts) {
	this.opts = opts;
	this.platformOpts = platformOpts;
	this.testRunId = platformOpts.testRunId;
	if (!this.testRunId) {
	throw new Error('testRunId is required');
	}
	this.s3LifecycleConfigurationRules = [
	{
	Expiration: { Days: 2 },
	Filter: { Prefix: 'tests/' },
	ID: 'RemoveAdHocTestData',
	Status: 'Enabled'
	},
	{
	Expiration: { Days: 7 },
	Filter: { Prefix: 'test-runs/' },
	ID: 'RemoveTestRunMetadata',
	Status: 'Enabled'
	}
	];
	}
	async init() {
	await setDefaultAWSCredentials(AWS);
	this.accountId = await getAccountId();
	await ensureSSMParametersExist(this.platformOpts.region);
	await ensureS3BucketExists('global', this.s3LifecycleConfigurationRules);
	await createIAMResources(this.accountId);
	}

artillery/packages/artillery/lib/platform/aws/aws-ensure-s3-bucket-exists.js

Lines 13 to 65 in 4cf8d05

	const setBucketLifecyclePolicy = async (
	bucketName,
	lifecycleConfigurationRules
	) => {
	const s3 = new AWS.S3();
	const params = {
	Bucket: bucketName,
	LifecycleConfiguration: {
	Rules: lifecycleConfigurationRules
	}
	};
	try {
	await s3.putBucketLifecycleConfiguration(params).promise();
	} catch (err) {
	debug('Error setting lifecycle policy');
	debug(err);
	}
	};
	// Create an S3 bucket in the given region if it doesn't already exist.
	// By default, the bucket will be created without specifying a specific region.
	// Sometimes we need to use region-specific buckets, e.g. when
	// creating Lambda functions from a zip file in S3 the region of the
	// Lambda and the region of the S3 bucket must match.
	module.exports = async function ensureS3BucketExists(
	region = 'global',
	lifecycleConfigurationRules = []
	) {
	const accountId = await getAWSAccountId();
	let bucketName = `${S3_BUCKET_NAME_PREFIX}-${accountId}`;
	if (region !== 'global') {
	bucketName = `${S3_BUCKET_NAME_PREFIX}-${accountId}-${region}`;
	}
	const s3Opts = region === 'global' ? {} : { region };
	const s3 = new AWS.S3(s3Opts);
	try {
	await s3.listObjectsV2({ Bucket: bucketName, MaxKeys: 1 }).promise();
	} catch (s3Err) {
	if (s3Err.code === 'NoSuchBucket') {
	await s3.createBucket({ Bucket: bucketName }).promise();
	} else {
	throw s3Err;
	}
	}
	if (lifecycleConfigurationRules.length > 0) {
	await setBucketLifecyclePolicy(bucketName, lifecycleConfigurationRules);
	}
	debug(bucketName);
	return bucketName;
	};

Therefore, I have prepared and run a script with s3LifecycleConfigurationRules as an empty array.

Would it be possible to add an option to not apply s3LifecycleConfigurationRules if the s3 bucket already exists?
Or if there are other, better workarounds, I'd like to know.