vdm

"AZs are physically separated by a meaningful distance, many kilometers, from any other AZ, although all are within 100 km (60 miles) of each other."

https://aws.amazon.com/about-aws/global-infrastructure/regio...

> 'ok, understand but Ide competent, knows many things, need more info before can do the thing'

   tcpflow stores all captured data in files that have names of the form:

   [timestampT]sourceip.sourceport-destip.destport[--VLAN][cNNNN]
   where: timestamp is an optional timestamp of the time that the first packet was seen

   .B t
   Prepends each filename with a Unix timestamp (seconds since epoch).
   .B T
   Prepends each filename with an ISO-8601 timestamp.

This does get me writing tests sooner.

AWS IAM does have resource condition keys which allow matching resources by account, org, org path, and tag. Resources in a Cloudformation stack would be automatically tagged, for example.

https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_p...

Philipp K. Janert

https://janert.me/books/feedback-control-for-computer-system...

/tmp is ephemeral in the sense that it dies with the Lambda instance, but it is also persistent between multiple serial invocations landing on that instance, even if the instance is frozen and thawed between some of those invocations.

The process memory state on the instance (set up during the Init phase) is also available between invocations.

https://docs.aws.amazon.com/lambda/latest/dg/runtimes-contex...

Also S3 should no-op transitions for objects smaller than the break-even size for each storage class, even if you ask it to.

I gave vantage.sh 5 minutes and did not see anything for S3 that is not already available from the built-in Cost Explorer, Storage Lens, Cost and Usage Reports, and taking 1 hour to study the docs https://docs.aws.amazon.com/AmazonS3/latest/userguide/Bucket...

Most "cloud optimisation" products want to tell you which EC2 instance type to use, but can't actually give actionable advice for S3. Happy to be corrected on this.

Not easy, but is possible and effective.

Lifecycle rules can filter by min/max object size. (since Nov 2021)

"Minimum storage duration charge" along with "Minimum capacity charge per object" is a property of an S3 Storage Class, not a lifecycle policy. Therefore this cost needs to be considered before selecting a storage class.

The charges for deleting before the minimum storage duration are documented for each storage class at https://docs.aws.amazon.com/AmazonS3/latest/userguide/storag...

Refer to the "Performance across the S3 Storage Classes" table at https://aws.amazon.com/s3/storage-classes/

0. https://docs.aws.amazon.com/AmazonS3/latest/userguide/batch-...

If you can select your objects with a lifecycle policy (by object tag or prefix) you don't need the LISTs either. The prefix can be "" to select all objects. Just be careful with that.

> LIST requests for any storage class are charged at the same rate as S3 Standard PUT, COPY, and POST requests.

I read this as LISTs do not cost double for infrequent access, even though other Tier 1 requests do.

"S3 Batch Operations" sends S3 requests based on a csv file, which can but does not have to be from S3 Inventory. But S3 Batch Operations supports only a subset of APIs and this does not include DeleteObject(s). [0]

An AWS Batch job could run a container which sends DeleteObjects requests but only when triggered by a job queue which seems redundant here.

If I can't use an expiration lifecycle policy because I need a selection of objects not matching a prefix or object tags, I would run something with `s5cmd rm` [1]. Alternatively roll your own golang which parses the CSV and sends many DeleteObjects requests in parallel goroutines.

0. https://docs.aws.amazon.com/AmazonS3/latest/userguide/batch-...

1. https://github.com/peak/s5cmd#delete-multiple-s3-objects

In production you probably want the host-vm and vm-vm confinement provided by svirt https://libvirt.org/drvqemu.html#driver-security-architectur...