Skip to Content
1
Jul 30, 2020 at 09:12 AM

Could I change saving location of cronjob log including S3 domain?

38 Views Last edit Jul 30, 2020 at 03:11 PM 3 rev

We customized mediaModel's S3 long domain to short one through using defaultS3MediaURLStrategy several months ago.

long domain : https://blablabla-northeast-2-prod-metadata.s3-ap-northeast-2.amazonaws.com

short domain : https://media.domain.com

The short domain works well in storefront.

After a couple of months, Our AWS administrator removed public access authorities from S3.

So long domain doesn't work anymore.

Storefront's media url(short domain) still works well.

But we found a lot of cronjob errors in dynatrace.

Error logs showed old long S3 domain with cronjob log path as below.

https://blablabla-northeast-2-prod-metadata.s3-ap-northeast-2.amazonaws.com/sys-master/cronjob/h57/hd7/9035967234078/20200720_062821-94995803-58db-4a12-a790-6fdfd89df39c.zip- Rarely occurred

https://blablabla-northeast-2-prod-metadata.s3-ap-northeast-2.amazonaws.com/sys-master/cronjob/hed/hdc/9035988107294/20200720_054421-c380c79f-9ed1-4005-a82a-5b6849174c41.zip- Rarely occurred

https://blablabla-northeast-2-prod-metadata.s3-ap-northeast-2.amazonaws.com/sys-master/cronjob/hf9/h70/9035974475806/20200720_072728-ece3ece8-198f-4504-8bf2-0270ff6beabc.zip- Rarely occurred

I don't know why this error occurred.

Could I change saving location of cronjob log including S3 domain?

Even any little clue would be very helpful.

Thanks in advance =)