收到七月帳單發現服務費用突增,想請教下次怎麼預防

I understand you're concerned about an unexpected increase in your July bill, particularly for Neptune, Kendra, and OpenSearch services. Here are some suggestions to help prevent this in the future:

For Amazon Neptune:

• Monitor your Neptune instance usage and consider terminating instances when not in use, especially if you're using Neptune Analytics which bills by the hour based on m-NCU usage.
• Check if you're using the appropriate instance types for your workload. Neptune offers different configurations including Standard and I/O-Optimized with different pricing models.
• Review your storage and I/O usage, as these are billed separately per GB-month and per million requests.
• Consider using Neptune Serverless if your workload has variable demand, as it automatically adjusts capacity based on application needs.
• Set up AWS Budgets and CloudWatch Alarms to alert you when costs exceed expected thresholds.
• If you're eligible and haven't used it yet, you could take advantage of Neptune's free tier which includes 750 hours of db.t3.medium or db.t4g.medium instance, 10 million I/O requests, and 1 GB of storage and backup for 30 days.

For all three services (Neptune, Kendra, and OpenSearch):

• Regularly review your AWS Billing Console to track usage.
• Set up cost allocation tags to better understand which projects or departments are driving costs.
• Consider implementing AWS Cost Explorer to analyze your spending patterns.
• Review and optimize your resource configurations to ensure you're not over-provisioning.

These steps should help you better manage and predict your AWS costs going forward.
Sources
Amazon Neptune Pricing
Amazon Neptune Free Trial | Fully Managed Graph Database | Amazon Web Services