{
	"id": "e7aa9a5d-37b8-41d3-863a-dcfd9ed2846b",
	"created_at": "2026-04-06T00:08:59.269702Z",
	"updated_at": "2026-04-10T03:21:25.234744Z",
	"deleted_at": null,
	"sha1_hash": "031fdf544253877038c0833dbd0f91ca632ab576",
	"title": "Managing the lifecycle of objects",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 57674,
	"plain_text": "Managing the lifecycle of objects\r\nArchived: 2026-04-05 21:33:12 UTC\r\nS3 Lifecycle helps you store objects cost effectively throughout their lifecycle by transitioning them to lower-cost\r\nstorage classes, or, deleting expired objects on your behalf. To manage the lifecycle of your objects, create an S3\r\nLifecycle configuration for your bucket. An S3 Lifecycle configuration is a set of rules that define actions that\r\nAmazon S3 applies to a group of objects. There are two types of actions:\r\nTransition actions – These actions define when objects transition to another storage class. For example,\r\nyou might choose to transition objects to the S3 Standard-IA storage class 30 days after creating them, or\r\narchive objects to the S3 Glacier Flexible Retrieval storage class one year after creating them. For more\r\ninformation, see Understanding and managing Amazon S3 storage classes.\r\nThere are costs associated with lifecycle transition requests. For pricing information, see Amazon S3\r\npricing.\r\nExpiration actions – These actions define when objects expire. Amazon S3 deletes expired objects on\r\nyour behalf. For example, you might to choose to expire objects after they have been stored for a\r\nregulatory compliance period. For more information, see Expiring objects.\r\nThere are potential costs associated with lifecycle expiration only when you expire objects in a storage\r\nclass with a minimum storage duration. For more information, see Minimum storage duration charge.\r\nImportant\r\nGeneral purpose buckets — You can't use a bucket policy to prevent deletions or transitions by an S3 Lifecycle\r\nrule. For example, even if your bucket policy denies all actions for all principals, your S3 Lifecycle configuration\r\nstill functions as normal.\r\nExisting and new objects\r\nWhen you add a Lifecycle configuration to a bucket, the configuration rules apply to both existing objects and\r\nobjects that you add later. For example, if you add a Lifecycle configuration rule today with an expiration action\r\nthat causes objects to expire 30 days after creation, Amazon S3 will queue for removal any existing objects that\r\nare more than 30 days old.\r\nChanges in billing\r\nIf there is any delay between when an object becomes eligible for a lifecycle action and when Amazon S3\r\ntransfers or expires your object, billing changes are applied as soon as the object becomes eligible for the lifecycle\r\naction. For example, if an object is scheduled to expire and Amazon S3 doesn't immediately expire the object, you\r\nwon't be charged for storage after the expiration time.\r\nhttps://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html\r\nPage 1 of 3\n\nThe one exception to this behavior is if you have a lifecycle rule to transition to the S3 Intelligent-Tiering storage\r\nclass. In that case, billing changes don't occur until the object has transitioned to S3 Intelligent-Tiering. For more\r\ninformation about S3 Lifecycle rules, see Lifecycle configuration elements.\r\nNote\r\nThere are no data retrieval charges for lifecycle transitions. However, there are per-request ingestion charges when\r\nusing PUT , COPY , or lifecycle rules to move data into any S3 storage class. Consider the ingestion or transition\r\ncost before moving objects into any storage class. For more information about cost considerations, see Amazon S3\r\npricing.\r\nMonitoring the effect of lifecycle rules\r\nTo monitor the effect of updates made by active lifecycle rules, see How do I monitor the actions taken by my\r\nlifecycle rules?.\r\nManaging the complete lifecycle of objects\r\nWith S3 Lifecycle configuration rules you can tell Amazon S3 to transition objects to less-expensive storage\r\nclasses, archive or delete them. For example:\r\nIf you upload periodic logs to a bucket, your application might need them for a week or a month. After that,\r\nyou might want to delete them.\r\nSome documents are frequently accessed for a limited period of time. After that, they are infrequently\r\naccessed. At some point, you might not need real-time access to them, but your organization or regulations\r\nmight require you to archive them for a specific period. After that, you can delete them.\r\nYou might upload some types of data to Amazon S3 primarily for archival purposes. For example, you\r\nmight archive digital media, financial, and healthcare records, raw genomics sequence data, long-term\r\ndatabase backups, and data that must be retained for regulatory compliance.\r\nBy combining S3 Lifecycle actions to manage an object's complete lifecycle. For example, suppose that the\r\nobjects you create have a well-defined lifecycle. Initially, the objects are frequently accessed for a period of 30\r\ndays. Then, objects are infrequently accessed for up to 90 days. After that, the objects are no longer needed, so\r\nyou might choose to archive or delete them.\r\nIn this scenario, you can create an S3 Lifecycle rule in which you specify the initial transition action to S3\r\nIntelligent-Tiering, S3 Standard-IA, or S3 One Zone-IA storage, another transition action to S3 Glacier Flexible\r\nRetrieval storage for archiving, and an expiration action. As you move the objects from one storage class to\r\nanother, you save on storage costs. For more information about cost considerations, see Amazon S3 pricing.\r\nTopics\r\nTransitioning objects using Amazon S3 Lifecycle\r\nhttps://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html\r\nPage 2 of 3\n\nExpiring objects\r\nSetting an S3 Lifecycle configuration on a bucket\r\nHow S3 Lifecycle interacts with other bucket configurations\r\nConfiguring S3 Lifecycle event notifications\r\nLifecycle configuration elements\r\nHow Amazon S3 handles conflicts in lifecycle configurations\r\nExamples of S3 Lifecycle configurations\r\nTroubleshooting Amazon S3 Lifecycle issues\r\nSource: https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html\r\nhttps://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html\r\nPage 3 of 3",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html"
	],
	"report_names": [
		"object-lifecycle-mgmt.html"
	],
	"threat_actors": [],
	"ts_created_at": 1775434139,
	"ts_updated_at": 1775791285,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/031fdf544253877038c0833dbd0f91ca632ab576.pdf",
		"text": "https://archive.orkl.eu/031fdf544253877038c0833dbd0f91ca632ab576.txt",
		"img": "https://archive.orkl.eu/031fdf544253877038c0833dbd0f91ca632ab576.jpg"
	}
}