Error modifying your security group inbound rules in assignment: 1

while updating the security group inbound rules in order to build connection from ec2 to rds

I am getting the error as follows:

You may be missing IAM policies that allow ModifySecurityGroupRules. You are not authorized to perform this operation. User: arn:aws:sts::934914170681:assumed-role/voclabs/user4940573=gkbndleryabp is not authorized to perform: ec2:ModifySecurityGroupRules on resource: arn:aws:ec2:us-east-1:934914170681:security-group/sg-0cae4bcdad35e4891 because no identity-based policy allows the ec2:ModifySecurityGroupRules action. Encoded authorization failure message: IBc18daSKctviBV0hV10or6L7fdPjI0kODG_hL5kVWQ3KSv3yQR-M8SGtRLUIjU7qIiMr3jsEsNXqnWF4hlZeKxYQ0SiQ4viWhEXTeuXxHsi7P2fYuE-ZtLqLWnqYpeb0i86rQyKOjBQo-v5GX6oTDw4YOWtGbRDYBb9mPAQbHpMawOf4qeMzxnfz0sgmvpibc18SEDqbYWw1YgAHGoLZ5c1iUitaui5v44A7tON78aWZjcCTkybAlfsRXBUPoJ2d-cOVzr-m6kPXHMKCeUyEf4BVJ4nr9yRRqHZWMpWTGb07Squ1ThcCvpuF4emvE3BEYtDN7f__1LjYHd7nHaBw_FZMCHh_ki1HnGClO4tsk5_S2KsPIUfaz_0ArjxL7Hv8eFVcXtnd-sgR7m2abyBzGp3pVQnCpxxxJarP7pa_eisssRjFhfa90A2MkNOfaoHS707NNpxJ55SBRYIN5hWzo3ThrglCTWbEm3jrQy0NEOMv8fKOSW8tM0mORs4EHDI-TjfJSWReEshiYtQ75Y_ZR4JInp9-0BX_k0hRBOhNTusK7WsDVFT24rCDherg-Lluh2H3qcOcdlevzjR02l5htzqwKpPIqgcjse1n5x5T7ZUQtostFI5Q2ER8hcZajTyY_zohWI6qbzB5C9RPYyhsjXV-aN0GsgPMiXnYYwcTOmb2lhPvFQVoNC9ChGwEEJ7FCIZ3vgFjnRg-3fM4lSN7XWAxLH_PnpttWGQFFcLM78R9m2ThKYNo00B3h4dVPToBrgofLKtsMJdgqg4Y5GfetPqbMu9f3oXdtdTdfFOQpJabTiEEDZsvy2vQe4y-AIkxamLzpVKkO3ho7L_PpZDgFmWfsm4mVvHCWcFLXKF5xZDdP6wDTDN5VTWOo15B3v-3krP4F66BA

@Rao_Huzaifa Hi! I think this question was answered here:

Let us know, if you need extra clarification.

thanks for the reply, unfortunately after correctly adding new inbound rule with ec2 security group , I tried to connect to rds with new password it refusing the connection with error :slight_smile:

psql: error: connection to server at (10.0.3.22), port 5432 failed: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.

@Rao_Huzaifa Try to reboot the lab and start from the beginning.