AWS Sharing experience with transfer costs between different regions and cost issues incurred during APM operation
When using AWS and applying APM, a lot of network-related costs occurred, so I organized it to remember the information. It was interesting to discover a network traffic problem that was difficult to recognize in small traffic. In the future, I think we can pay more attention to managing network costs well.
Server structure
- Actual service target area is Korea
- Previously, there was no AWS in the Korea Region, but a server existed in the Tokyo Region.
- About 10 major services are being serviced in the Tokyo Region
- Recent environments are installed in Korea Region
- APM (application performance monitoring) tool installed in Tokyo Region
- APM service transmits data to Opensearch in Korea Region
Problem situation
- I knew that there was no network cost for the same region.
- Even if it is the same region, fees are charged if the availability zone is different
- Approximately USD 0.01 per GB when transferring data across multiple Availability Zones in the same Region
- Not properly aware of the cost of transmitting data to different regions
- The cost of transmitting data from different regions is approximately USD 0.09 per GB
- Not properly aware of traffic volume
- Transfer approximately 30TB of data per month from APM to Opensearch, i.e. to another region
30000 GB * 0.09 = $2700
, which requires quite a lot of data transfer costs- Additionally, traffic costs incurred from servers in different availability zones are also added even if they are in the same region.
organize
It was an opportunity to realize that network costs are higher than expected. Personally, I thought that the price of data transfer in TB was not very expensive, but when I actually checked, it was quite expensive.
In the future, we plan to set up cost monitoring alerts, traffic alerts, etc. using cloudwatch, and take more measures to ensure that unnecessary costs are not incurred and can be used for other necessary expenses.