-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Feature Request: AWS Shield Protection #1769
Comments
I'm developing this resource. But ShieldProtection requires ShiledSubscription and I'm having a trouble to find the way of activating shield advanced... |
My company has it - how can I help? |
Hey, any progress on this one? |
@atsushi-ishibashi I maybe able to get you access to a test account to setup shield advanced as I have this subscription already ;) |
This depends on the policy of the acceptance test🤔 |
+1 |
How can we test this for the community? @akataz |
+1 |
I was able to successfully test only the shield advanced part via 'make testacc' by adding '-run=TestAccAWSShieldSubscription' the makefile, as I showed in: PR #1899 . I have not had success testing the complete run-through of 'make testacc'; if anyone has any suggestions they would be appreciated. |
I've talked to Hashicorp Support and they said they need another company to test the PR before they can merge this, is there anyone with a Shield Advanced Subscription that can test this? @grealish @countergram |
A new For future bug reports or feature requests with the Shield Advanced service, please submit a new GitHub issue. Thanks! |
The new |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
I would like to be able to manage "protection" objects within AWS Shield so that I can declaratively add protections to my resources (which are also managed through Terraform)
The text was updated successfully, but these errors were encountered: