An in-house advanced technical session on AWS Security Best Practices was organized. Participants included clients from different industry vertices. Our experts highlighted realistic use cases during the workshop, along with a live demonstration of how security patches may prevent attacks, conserve resources, and reduce costs. We believe the workshop was highly beneficial for our attendees. As a speaker, it was also helpful to connect with them to understand different challenges and discuss about possible solutions.

I have shared the presentation deck below if it helps.

For different purpose, it gets necessary to provide the EC2 access ton user or group. Providing AWS managed EC2 Full Access can be critical as if the credential is leaked or abused, there can have potential risk of huge bill end of the month. To avoid that, we can make a custom policy and mention the instance type you would like to permit. For instance, if you permit nano, micro, small and medium size of instance, you can define that. So that, the related users/group members won’t be able to launch EC2 other than the mentioned type,

Here are the steps:

Step 1: Go to IAM section of the AWS service

Step 2: Go to Policies

Step 3: Provide the following code in JSON with your preferred name of the policy

{
“Version”: “2012-10-17”,
“Statement”: [
{
“Effect”: “Allow”,
“Action”: “ec2:“, “Resource”: ““,
“Condition”: {
“ForAllValues:StringLike”: {
“ec2:InstanceType”: [
“.micro”,
“.nano”,
“*.small”,
“*.medium”

]
}
}
}
]
}

Step 4: Assign this policy to a role.

Step 5: Assign the role to a specific user/group to activate the policy

Big event is about to launch. AWS Community Day 2022 is going to happen on December 10, 2022. We are already in process of participants registration and speakers. As a community leader and co-founder of the largest AWS User group of Bangladesh, I am the core organizer of this event.

Here is the organizing team to make a successful execution of this event: