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

[New Resource & Data Source]: Image Block Public Access #33473

Closed
rymancl opened this issue Sep 14, 2023 · 4 comments · Fixed by #33810
Closed

[New Resource & Data Source]: Image Block Public Access #33473

rymancl opened this issue Sep 14, 2023 · 4 comments · Fixed by #33810
Labels
new-resource Introduces a new resource. service/ec2 Issues and PRs that pertain to the ec2 service.
Milestone

Comments

@rymancl
Copy link

rymancl commented Sep 14, 2023

Description

https://aws.amazon.com/about-aws/whats-new/2023/09/amazon-ec2-block-public-access-machine-images/
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sharingamis-intro.html#enable-block-public-access-for-amis

Add new resource and data source for AMI BPA.

Requested Resource(s) and/or Data Source(s)

  • aws_ec2_image_block_public_access
    • or aws_ami_block_public_access since you already use the "aws_ami" prefix for other resources

Potential Terraform Configuration

resource "aws_ec2_image_block_public_access" "this" {
  enabled = true
  # enabled = false
}

# or

resource "aws_ec2_image_block_public_access" "this" {
  image_block_public_access_state = "block-new-sharing"
  # image_block_public_access_state = "unblocked"
}

References

https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/ec2#Client.EnableImageBlockPublicAccess

Would you like to implement a fix?

No

@github-actions
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label Sep 14, 2023
@justinretzolk justinretzolk added new-resource Introduces a new resource. new-data-source Introduces a new data source. service/ec2 Issues and PRs that pertain to the ec2 service. and removed needs-triage Waiting for first response or review from a maintainer. labels Sep 14, 2023
@chilledornaments
Copy link
Contributor

@justinretzolk I'd love to tackle this one :)

@ewbankkit ewbankkit removed the new-data-source Introduces a new data source. label Oct 9, 2023
@github-actions github-actions bot added this to the v5.21.0 milestone Oct 10, 2023
@github-actions
Copy link

This functionality has been released in v5.21.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
new-resource Introduces a new resource. service/ec2 Issues and PRs that pertain to the ec2 service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants