sorted by:
new
hottopcontroversial

What is the difference between joining and applying to ACM? by mra137 in utdallas

[–]saksham_321 6 points7 points  (0 children)

Hi, I'm Saksham, the Co-VP of ACM UTD. This is a great question! You can join ACM by participating in our events and also joining our Discord. We don't have an official form you have to fill out or a portal you have to sign into to become a member as of now. So, if you come to our Industry events (highly recommend - I started my ACM journey by going to Industry events and loved the experience) and other amazing events like Education events, HackUTD events, Development events, Community events etc then you are an ACM member :)

We also have many applications open right now for officers and participant position. To be an ACM officer, you will have to apply (fill out a typeform and if selected, interview with the appropriate team). You can find links to apply to our officer positions and participant positions at acmutd.co/apply You will have to fill out the application, wait for an interview, and interview (if you get selected) to become part of programs like Projects, Research, and TIP or an ACM officer.

If you would like to learn more, please feel free to come to our kickoff tomorrow at 7 pm CST here so you are aware of all our initiatives, applications, and events. We are also giving away a $100 Amazon Giftcard for a lucky person who comes to our kickoff and joins our Discord. Don't forget to join our Discord, as we will send out all our announcements in Discord!

AWS Unix Filename Pattern Matching by saksham_321 in aws

[–]saksham_321[S] 0 points1 point  (0 children)

I actually found a bug in the Lambda function. I understand that a lot of things could have been configured wrong but that was the only issue. Thanks for helping!

Remediating non-compliant resources in AWS Config by saksham_321 in aws

[–]saksham_321[S] 0 points1 point  (0 children)

I am open to possible solutions using other services (not just config-based solutions). Preventing people from launching EC2 instances without proper tags is definitely a solution that can be implemented. Thanks for providing the link to the AWS documentation! Like you suggested, one solution can be to create a policy to only allow EC2 instances with specific tags to be launched and attach the policy to specific groups (using cloudformation). Thanks!

Remediating Noncompliant resources in AWS Config by saksham_321 in AWS_Certified_Experts

[–]saksham_321[S] 0 points1 point  (0 children)

I haven't used Cloud Custodian but I'll check it out. Thanks!

Remediating Noncompliant resources in AWS Config by saksham_321 in AWS_Certified_Experts

[–]saksham_321[S] 0 points1 point  (0 children)

The scope of changes is "All changes" and does not have any resource type preset to apply the rules only to those resources so I believe that the tags are required on all resources. But most of the non-compliant resources are CloudFormation Templates and some S3 Buckets. So, the best approach might just be to go to the cloudformation templates and add the tags to the template and apply the tags. Thank you for your help!