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

Migrate to AWS SDKv2 #770

Open
james03160927 opened this issue Oct 16, 2024 · 3 comments · Fixed by #773, #787, #789 or #790 · May be fixed by #785
Open

Migrate to AWS SDKv2 #770

james03160927 opened this issue Oct 16, 2024 · 3 comments · Fixed by #773, #787, #789 or #790 · May be fixed by #785
Assignees

Comments

@james03160927
Copy link
Contributor

The AWS SDK v1 is officially deprecated (end-of-support is July 31, 2025). We need to migrate code to v2 before it ends the support for this.

@james03160927 james03160927 self-assigned this Oct 16, 2024
This was referenced Oct 16, 2024
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Oct 20, 2024
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Oct 20, 2024
…shboard, cloudWatch logGroup, codeDeploy Application, dynamodb to awsSDKv2 gruntwork-io#770
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Oct 20, 2024
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Oct 26, 2024
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Oct 26, 2024
…shboard, cloudWatch logGroup, codeDeploy Application, dynamodb to awsSDKv2 gruntwork-io#770
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Oct 26, 2024
james03160927 pushed a commit that referenced this issue Oct 28, 2024
* change port access_analyzer, acm, acmpca, ami, API GWv1 & API GWv2 to awsSDKv2 #770

* change port backup vault, cloudTrail, cloudWatch alarm, cloudWatch dashboard, cloudWatch logGroup, codeDeploy Application, dynamodb to awsSDKv2 #770

* change port appRunner, ASG, config recorder, config service, dataSync location, dataSync task to awsSDKv2 #770
@james03160927 james03160927 reopened this Oct 31, 2024
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Oct 31, 2024
…c beanstalk, elasticache, elb, elbv2, guardduty to awsSDKv2 gruntwork-io#770
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Oct 31, 2024
…c beanstalk, elasticache, elb, elbv2, guardduty to awsSDKv2 gruntwork-io#770
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Oct 31, 2024
…c beanstalk, elasticache, elb, elbv2, guardduty to awsSDKv2 gruntwork-io#770
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Nov 1, 2024
…c beanstalk, elasticache, elb, elbv2, guardduty to awsSDKv2 gruntwork-io#770
james03160927 pushed a commit that referenced this issue Nov 2, 2024
…c beanstalk, elasticache, elb, elbv2, guardduty to awsSDKv2 #770 (#777)
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Nov 3, 2024
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Nov 6, 2024
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Nov 9, 2024
…ey pair, ec2 placement group, kinesis firehose, kinesis stream, kms customer key, lambda layer, lambda, macie to awsSDKv2 gruntwork-io#770
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Nov 9, 2024
…ey pair, ec2 placement group, kinesis firehose, kinesis stream, kms customer key, lambda layer, lambda, macie to awsSDKv2 gruntwork-io#770
james03160927 pushed a commit that referenced this issue Nov 12, 2024
…ey pair, ec2 placement group, kinesis firehose, kinesis stream, kms customer key, lambda layer, lambda, macie to awsSDKv2 #770 (#781)
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Nov 18, 2024
…l, ec2 ipam resource discovery, ec2 ipam scope, ec2 ipam to awsSDKv2 gruntwork-io#770 (gruntwork-io#781)
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Nov 18, 2024
…l, ec2 ipam resource discovery, ec2 ipam scope, ec2 ipam to awsSDKv2 gruntwork-io#770
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Nov 19, 2024
james03160927 pushed a commit that referenced this issue Nov 20, 2024
…l, ec2 ipam resource discovery, ec2 ipam scope, ec2 ipam to awsSDKv2 #770 (#790)
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Nov 20, 2024
wakeful added a commit to wakeful/cloud-nuke that referenced this issue Nov 20, 2024
…ll resource policy, network firewall rule group, network firewall tls config to awsSDKv2 gruntwork-io#770
@wakeful wakeful linked a pull request Nov 20, 2024 that will close this issue
5 tasks
@sc250024
Copy link
Contributor

@james03160927 @wakeful Is EC2 being covered by someone? If not, then I think a new issue just for that would be nice. It's a much larger refactor. I would be happy to do it, but along the way, I would have some questions about how it's desired to be structured.

@wakeful
Copy link
Contributor

wakeful commented Nov 21, 2024

@sc250024 You can pick the ec2 resource. AFAIK, there is some reference between ec2 resources and VPC (and actually all other network-related ones). Just ping on this issue to let us know what you'll be working on to avoid duplication. I’ll look over the weekend for any remaining resources that need a 'bump'.

@sc250024
Copy link
Contributor

@wakeful I will open a new issue then. The reason is because I started down the rabbit hole with internet-gateway and egress-only-internet-gateway before realizing that EC2, VPC, Subnets, etc. are all interconnected somehow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment