Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

credit specification of a t4 instance ignored #1779

Closed
rafalkrupinski opened this issue Jan 21, 2022 · 4 comments
Closed

credit specification of a t4 instance ignored #1779

rafalkrupinski opened this issue Jan 21, 2022 · 4 comments
Assignees
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed

Comments

@rafalkrupinski
Copy link

rafalkrupinski commented Jan 21, 2022

Hello!

Hi, I'm creating a t4g instance with 'standard' cpu credit but it's created with 'unlimited'

  • Vote on this issue by adding a 👍 reaction
  • To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already)

Issue details

I use this object to start t4Nano instance

new aws.ec2.Instance('bastion', {
    instanceType: aws.ec2.InstanceType.T4g_Nano,
    ami,
    creditSpecification: { cpuCredits: 'standard' },
});

But console shows its credit specification is 'unlimited' and the aws cli doesn't show anything regarding credits.

I was able to create identical instance with standard CPU credits via aws console.

version v3.22.1

@rafalkrupinski rafalkrupinski added the kind/bug Some behavior is incorrect or out of spec label Jan 21, 2022
@danielrbradley danielrbradley added the awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). label Jan 25, 2022
@danielrbradley
Copy link
Member

This appears to be an upstream issue: hashicorp/terraform-provider-aws#15156

@rafalkrupinski
Copy link
Author

Ah, the link has a workaround too, thank you @danielrbradley

Should the issue remain open until upstream bug is closed?

@danielrbradley
Copy link
Member

Yup, happy to leave open to help direct anyone else who encounters the issue 👍

@mikhailshilkov mikhailshilkov added resolution/fixed This issue was fixed and removed awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). labels Nov 2, 2023
@mikhailshilkov mikhailshilkov self-assigned this Nov 2, 2023
@mikhailshilkov
Copy link
Member

The upstream issue got closed in June 2022, so I'm closing this one too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Development

No branches or pull requests

3 participants