Cristian Magherusan-Stanciu

I'm juggling between about a dozen of AWS accounts, for which I have defined credential profiles in ~/.aws, so for me the cache would need to be split on a...

I am running 8.0 for x86. But I noticed that the `tce-load -wic` is working fine after fixing the ownership of a directory reported in an error message, so I...

@omieomye additionally the replication is a Push architecture, the source ECR needs to be aware of all the destinations it's replicating to. There are cases where for various reasons you...

As a workaround for [AutoSpotting](https://github.com/AutoSpotting/AutoSpotting) I've implemented a custom CloudFormation resource that copies the Docker image from a source ECR to local ECR usable from Lambda using the `crane` tool...

@tedivm the CloudFormation custom resource I mentioned in my previous comment only clones the image relevant to the current Lambda function into a dedicated ECR created in the current AWS...

> Is this done now? https://aws.amazon.com/blogs/compute/introducing-cross-account-amazon-ecr-access-for-aws-lambda/ This works across accounts in the same region. But certain use cases need it also to support using images from other regions.

> @cristim as workaround you could replicate the images to other regions in shared account. Unfortunately I don't have access to the source account (it's maintained by the AWS Marketplace...

Thanks, that's actually a good idea for a new tool, I'll try to implement it once I'm done with my current work, I'll let you know once I have something...

Have you considered running the application on Spot instances? They're more likely to be interrupted so that the tasks uptime can be reduced. Or just bounce the ec2 instances from...

Because there is a newer version that benefits from recent developments introduced in golang 1.8: https://github.com/eawsy/aws-lambda-go-shim The new version decouples the Python wrapper and the cgo shim into a pre-built...