- Newest
- Most votes
- Most comments
Hi,
I have seen EC2 instances having such issues when their IAM execution role was incorrect.
Did you check that you execution role is set according to: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/instance_IAM_role.html ?
Best,
Didier
Based on the information available, I cannot definitively confirm that in-kind credits given by AWS apply to Capacity Blocks. AWS credits are generally applied automatically to eligible services and products, but the specific applicability to Capacity Blocks is not explicitly mentioned in the provided sources.
AWS credits are typically applied in a specific order, starting with the credit closest to expiration, then the credit with the fewest eligible services, and finally the oldest credit. These credits are used to cover charges for applicable services or products until they are consumed or expire.
However, Capacity Blocks are a specific offering within Amazon EC2 that allows users to purchase targeted capacity reservations for a set period. They have their own pricing and billing structure, which may differ from standard EC2 instances.
If you have received bills for Capacity Blocks despite having in-kind credits, it's possible that:
- The credits may not be applicable to Capacity Blocks specifically.
- The credits might have been applied to other eligible services first.
- The amount of credits may not have been sufficient to cover the entire cost of the Capacity Blocks.
To get a definitive answer about whether your specific in-kind credits apply to Capacity Blocks, it would be best to contact AWS Support directly. They can provide you with accurate information about your account's credit application and billing for Capacity Blocks.
Sources
Applying AWS credits - AWS Billing
Use AWS credits and invoicing in my AWS account | AWS re:Post
Find and purchase Capacity Blocks - Amazon Elastic Compute Cloud
Relevant content
- asked 3 months ago
- asked 5 years ago
- asked a year ago
- Accepted Answerasked 4 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 3 years ago