[decom] Decommission of s3.traveloka.com S3 Bucket
Overview
As part of the initiative to decommission tvlk-prod legacy shared account. Cloud Infra team is decommissioning s3.traveloka.com bucket (not to be confused with traveloka S3 bucket).
This bucket is currently allow public access (via bucket policy). No principal is allowed to write to this bucket via bucket policy.
Why?
- To remove unused resource in
tvlk-prod.
- Reduce potential risk of data leak since this bucket allow public read.
Plan
- Jan 11th, 2020 : Deny all write access to this bucket via bucket policy.
- March 1st, 2020 : Remove public read access (from bucket policy)
- March 31st, 2020 : Decommission the bucket.
What do you need to do?
- Please check your application code for reference to s3.traveloka.com S3 bucket or s3.traveloka.com domain.
- If your application still rely on this bucket, please raise raise issue in infra-production-playbook repository and explain your use case and schedule to migrate.
Usage Data
You can find usage data per 2010-01-28 in this sheet : https://docs.google.com/spreadsheets/d/1KdyrdPBko5iQ29EM_tqScOLGBtVVU0CUG4RrxEJKx0I/edit#gid=512670173
Should you have questions or concerns regarding this deprecation please do let Cloud Infra know in #site-infra-channel.