Forem: Dinesh Rathee

[Boost]

Dinesh Rathee — Wed, 12 Nov 2025 05:05:10 +0000

How to Set Up the OpenAI API with Python and Flask

dan ・ Feb 28 '24

#python #flask #openai #ai

[Boost]

Dinesh Rathee — Wed, 12 Nov 2025 02:32:10 +0000

Complete Guide to the OpenAI API 2025

Adrian Machado for Zuplo ・ Apr 22

#ai #api

[Boost]

Dinesh Rathee — Sat, 08 Nov 2025 04:11:54 +0000

Build a Recruitment Chatbot with Python and OpenAI

Sangram Sundaray ・ May 7 '24

#ai #chatgpt #python #tutorial

[Boost]

Dinesh Rathee — Sat, 08 Nov 2025 03:28:23 +0000

Prompt Engineering for OpenAI Chat Completions

sreejinsreenivasan ・ Feb 19 '24

#llm #openai #promptengineering

Amazing !!!

Dinesh Rathee — Fri, 03 Oct 2025 20:43:57 +0000

How to Migrate ECR Docker Images Between Repositories (with Automation)

Todor Todorov for AWS Community Builders ・ Sep 24

#ecr #move #images #docker

How to Copy a Security Group with Rules from one AWS Account to Another account ? 🧐✅👨‍💻👩‍💻

Dinesh Rathee — Thu, 21 Jan 2021 03:45:23 +0000

𝗜𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝗡𝗼𝘁𝗲: 📝𝗢𝗽𝗶𝗻𝗶𝗼𝗻𝘀 𝗮𝗿𝗲 𝗺𝘆 𝗼𝘄𝗻 🏁🙂 𝗔𝗻𝗱 𝗶𝘁 𝗶𝘀 𝗺𝘆 𝗽𝗲𝗿𝘀𝗼𝗻𝗮𝗹 𝗯𝗹𝗼𝗴.

As you might be already aware that you can copy rules from an existing security group to a new security group within same Account, you can refer to an existing AWS Knowledge Center Article

But the Challenge comes in when you need to Achieve it "From one AWS Account to another Account."

How to Copy a Security Group with Rules from one Account to Another ?

Use this Python Script CopySGFromOneAWSAccountToAnotherScript.py , and you will need to provide the following details:

Source Account:
- Access Key
- Secret Key
- Region
- Security Group Id

Destination Account:
- Access Key
- Secret Key
- Region

Script Content

# -*- coding: utf-8 -*-
"""
Created on Wed May 20 13:30:41 2021
@author: nikheel script, blog dinesh
"""

import boto3

sourceAccount={
        'AccessKey':'access key',
        'SecretKey':'secret key',
        'Region':'source region',
        'SecurityGroupId': 'security group id'
        }
destinationAccount = {
        'AccessKey':'access key',
        'SecretKey':'secret key',
        'Region':'destination region'
        }

# ------ Source Account ------ #

#set up boto3 client for source account

client = boto3.client(
        "ec2",
        region_name = sourceAccount['Region'],
        aws_access_key_id=sourceAccount['AccessKey'],
        aws_secret_access_key=sourceAccount['SecretKey']
        )

# describe security group that will be copied

response = client.describe_security_groups(
        GroupIds=[
                sourceAccount['SecurityGroupId']
                ]
        )["SecurityGroups"][0]

# extract ingress and egress rules for the security group

ingress = response["IpPermissions"]
egress = response["IpPermissionsEgress"]

# ------ Destination Account ------ #

#set up boto3 client for destination account

client = boto3.client(
        "ec2",
        region_name = destinationAccount['Region'],
        aws_access_key_id=destinationAccount['AccessKey'],
        aws_secret_access_key=destinationAccount['SecretKey']
        )

# create a new security group in the destination account

groupId = client.create_security_group(
        Description='security-group-from-{}'.format(sourceAccount['Region']),
        GroupName='security-group-from-{}'.format(sourceAccount['Region'])
        )["GroupId"]

# removed all egress rules from newly created security group

clearEgress = client.describe_security_groups(
        GroupIds=[groupId]
        )["SecurityGroups"][0]["IpPermissionsEgress"]

client.revoke_security_group_egress(
        GroupId=groupId,
        IpPermissions=clearEgress
        ) 

# create ingress and egress rules for the newly created security group   

client.authorize_security_group_ingress(
        GroupId=groupId,
        IpPermissions=ingress
        )
client.authorize_security_group_egress(
        GroupId=groupId,
        IpPermissions=egress
        )

I have structured the above in an easy to view and edit dictionary format. These are the only updates that will be needed to be performed on this script.

For the record, it is not advised to hard code access keys into our scripts as this can be a security risk if the script is accidentally exposed however, in this case, I just wanted to show the main principle of what needed to be done.

Created an example of your particular needs using the Python Boto3 SDK for AWS which you can find with attached script named "CopySGFromOneAWSAccountToAnotherScript.py"

Once you have executed this script, it will perform the following functions in this order:

describe the security group rule you would like to copy in the source account using the describe_security_groups API call
from the response obtained, we store the ingress and egress rules into variables for future reference
we create a new security group in the destination account using the create_security_group API call
remove all egress rules from the newly created security group using the revoke_security_group_egress API call
add the egress and ingress rules to the new security group using the API calls authorize_security_group_ingress and authorize_security_group_egress

References

Script - CopySGFromOneAWSAccountToAnotherScript.py

Thanks for reading.
Any feedback, please write it to me here in comments..
Also, 🤝🤗You can connect with us 🤝🤗

LinkedIn
DevTo
GitHub
Twitter

Script Credits - Nikheel Soni

𝗜𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝗡𝗼𝘁𝗲: 📝𝗢𝗽𝗶𝗻𝗶𝗼𝗻𝘀 𝗮𝗿𝗲 𝗺𝘆 𝗼𝘄𝗻 🏁🙂 𝗔𝗻𝗱 𝗶𝘁 𝗶𝘀 𝗺𝘆 𝗽𝗲𝗿𝘀𝗼𝗻𝗮𝗹 𝗯𝗹𝗼𝗴.

My 3️⃣✅ AWS Knowledge Center articles published to help customers on "AWS Lightsail" ☁️🔍⏳👨‍💻👩‍💻

Dinesh Rathee — Fri, 15 Jan 2021 01:12:26 +0000

Thought of sharing these with you 😊

"➜ As you might be aware that due to some new features Amazon Web Services (AWS) Lighsail Customers begin to run more complex environments and these articles can be handy.👨‍💻👩‍💻

I've written below two Articles on AWS Knowledge Center which you may find useful to manage your Lightsail Instances in your AWS account in a programmatic way using AWS CLI

How can I manage my Lightsail instance using AWS CLI commands?
How can I manage static IP addresses on my Lightsail instances using AWS CLI commands?
How can I manage my snapshots and create backups for my Lightsail instances using AWS CLI commands?

                 😇 Happy learning 😇

Sharing my next AWS Knowledge Center article published on helping customers to fix Encryption related issues☁️🔍⏳👨‍💻👩‍💻

Dinesh Rathee — Fri, 09 Oct 2020 16:35:16 +0000

Thought of sharing these with you 😊

➕1️⃣
𝗦𝗵𝗮𝗿𝗶𝗻𝗴 𝗺𝘆 𝗻𝗲𝘅𝘁 𝘁𝗿𝗼𝘂𝗯𝗹𝗲𝘀𝗵𝗼𝗼𝘁𝗶𝗻𝗴 𝗮𝗿𝘁𝗶𝗰𝗹𝗲 𝗽𝘂𝗯𝗹𝗶𝘀𝗵𝗲𝗱 𝗼𝗻 AWS 𝐊𝐧𝐨𝐰𝐥𝐞𝐝𝐠𝐞 𝐂𝐞𝐧𝐭𝐞𝐫 𝐭𝐨 𝐡𝐞𝐥𝐩 𝐜𝐮𝐬𝐭𝐨𝐦𝐞𝐫𝐬 ✍️👨‍💻👩‍💻⛔💭✅😇🤝

𝙃𝙤𝙬 𝙘𝙖𝙣 𝙄 𝙫𝙞𝙚𝙬 𝙚𝙣𝙘𝙧𝙮𝙥𝙩𝙞𝙤𝙣 𝙞𝙣𝙛𝙤𝙧𝙢𝙖𝙩𝙞𝙤𝙣 𝙖𝙗𝙤𝙪𝙩 𝙢𝙮 𝘼𝙈𝙄 𝙤𝙧 𝙨𝙣𝙖𝙥𝙨𝙝𝙤𝙩?

𝐁𝐚𝐜𝐤𝐠𝐫𝐨𝐮𝐧𝐝:

𝑴𝒂𝒏𝒚 𝑨𝑾𝑺 𝑪𝒖𝒔𝒕𝒐𝒎𝒆𝒓𝒔 𝒖𝒔𝒆 𝑨𝑾𝑺 𝑬𝑩𝑺 𝒗𝒐𝒍𝒖𝒎𝒆 𝒆𝒏𝒄𝒓𝒚𝒑𝒕𝒊𝒐𝒏 𝒖𝒔𝒊𝒏𝒈 𝑲𝑴𝑺 𝒌𝒆𝒚𝒔 𝒘𝒉𝒊𝒄𝒉 𝒑𝒓𝒐𝒕𝒆𝒄𝒕𝒔 𝒅𝒂𝒕𝒂 𝒇𝒐𝒓 𝒄𝒖𝒔𝒕𝒐𝒎𝒆𝒓𝒔. 𝑺𝒐𝒎𝒆𝒕𝒊𝒎𝒆𝒔 𝒄𝒖𝒔𝒕𝒐𝒎𝒆𝒓𝒔 𝒘𝒐𝒖𝒍𝒅 𝒘𝒐𝒏𝒅𝒆𝒓 𝒘𝒉𝒚 𝒕𝒉𝒆𝒚 𝒂𝒓𝒆 𝒏𝒐𝒕 𝒂𝒃𝒍𝒆 𝒕𝒐 𝒔𝒉𝒂𝒓𝒆 𝒔𝒏𝒂𝒑𝒔𝒉𝒐𝒕𝒔 𝒐𝒓 𝑨𝑴𝑰𝒔. 𝑻𝒉𝒊𝒔 𝒂𝒓𝒕𝒊𝒄𝒍𝒆 𝒘𝒊𝒍𝒍 𝒉𝒆𝒍𝒑 𝒚𝒐𝒖 𝒊𝒏 𝒐𝒓𝒅𝒆𝒓 𝒕𝒐 𝒊𝒅𝒆𝒏𝒕𝒊𝒇𝒚 𝒅𝒆𝒕𝒂𝒊𝒍𝒔 𝒐𝒇 𝒕𝒉𝒆 𝒓𝒆𝒔𝒐𝒖𝒓𝒄𝒆𝒔 (𝒂𝒔𝒔𝒐𝒄𝒊𝒂𝒕𝒆𝒅 𝒔𝒏𝒂𝒑𝒔𝒉𝒐𝒕, 𝑲𝑴𝑺 𝒌𝒆𝒚 𝒊𝒏 𝒖𝒔𝒆) 𝒘𝒉𝒊𝒄𝒉 𝒉𝒆𝒍𝒑𝒔 𝒊𝒏 𝒅𝒆𝒄𝒊𝒅𝒊𝒏𝒈 𝒂𝒑𝒑𝒓𝒐𝒑𝒓𝒊𝒂𝒕𝒆 𝒕𝒓𝒐𝒖𝒃𝒍𝒆𝒔𝒉𝒐𝒐𝒕𝒊𝒏𝒈 𝒂𝒄𝒕𝒊𝒐𝒏𝒔 𝒃𝒂𝒔𝒆𝒅 𝒐𝒏 𝒕𝒉𝒊𝒔 𝒊𝒏𝒇𝒐𝒓𝒎𝒂𝒕𝒊𝒐𝒏.

𝐈𝐟 𝐲𝐨𝐮 𝐧𝐞𝐞𝐝 𝐦𝐨𝐫𝐞 𝐞𝐱𝐭𝐞𝐧𝐝𝐞𝐝 𝐝𝐞𝐭𝐚𝐢𝐥𝐬 𝐨𝐟 𝐭𝐡𝐞𝐬𝐞 𝐚𝐫𝐭𝐢𝐜𝐥𝐞𝐬, 𝐩𝐥𝐞𝐚𝐬𝐞 𝐫𝐞𝐟𝐞𝐫 𝐦𝐲 𝐛𝐥𝐨𝐠 𝐩𝐨𝐬𝐭 𝐛𝐞𝐥𝐨𝐰:

[+]https://dev.to/dineshrathee12/how-to-get-details-of-an-ami-or-snapshot-if-it-is-encrypted-and-with-which-key-aws-managed-cmk-or-customer-manager-cmk-aws-7b0

                 😇 𝙃𝙖𝙥𝙥𝙮 𝙡𝙚𝙖𝙧𝙣𝙞𝙣𝙜😇

🤝👥Join my Facebook Group "AWS Troubleshooting Tips and Tricks & Blogs" ☁️🔍⏳👨‍💻👩‍💻🛠️✅

Dinesh Rathee — Sun, 13 Sep 2020 00:34:13 +0000

Thought of sharing this with you 😊

I've started posting my articles here on Facebook group as well

"AWS Troubleshooting Tips and Tricks & Blogs"☁️🔍⏳👨‍💻👩‍💻🛠️✅

You can join here

[+] https://www.facebook.com/groups/2588950954550770/?ref=gs&fref=gs&dti=2588950954550770&hc_location=group

  ☁️🔍⏳👨‍💻👩‍💻🛠️✅😇 Happy learning 😇☁️🔍⏳👨‍💻👩‍💻🛠️✅

My two AWS Knowledge Center articles published to help customers on "AWS Service Quotas" ☁️🔍⏳👨‍💻👩‍💻

Dinesh Rathee — Fri, 11 Sep 2020 09:37:13 +0000

Thought of sharing these with you 😊

" As you might be already aware of that you can request, view, and manage "AWS service quotas", formerly known as "limits", from the Service Quotas Console or using AWS CLI commands

I've written below two Articles on AWS Knowledge Center which you may find useful to control AWS account quotas or limits in a programmatic way using AWS CLI

How can I request, view, and manage service quota increase requests using AWS CLI commands ?
How can I troubleshoot errors using the AWS CLI to manage my service quota requests?

If you need more extended details of these articles, please refer my blog post below :

[+] https://dev.to/dineshrathee12/manage-my-service-quotas-also-referred-to-as-limits-in-aws-account-using-aws-cli-commands-5cg2

                 😇 Happy learning 😇

Via AWS CLI-☁️📢Automating my post - Using AWS Systems Manager Automation Document🧐to fix✅SSH issue on a Linux EC2 Instance👨‍💻👩‍💻

Dinesh Rathee — Mon, 20 Jul 2020 00:48:52 +0000

How to execute actions listed under Post using AWS CLI

We've followed AWS Console Steps to use AWS Systems Manager Automation Document - "AWSSupport-ExecuteEC2Rescue" to fix SSH issue on a Linux EC2 Instance.

To check console steps , please click below link
How to use AWS Systems Manager Automation Document - "AWSSupport-ExecuteEC2Rescue" to fix SSH issue on a Linux EC2 Instance

Now, I will be explaining you how we can achieve this using AWS CLI commands using simple steps:

Make sure you have AWS CLI setup and you've enough permissions to use SSM to execute these documents.
If you have admin privileges , it will be great !

If you would like to know how to install and configure AWS CLI, please refer this link

Steps Using AWS CLI:

• Running the Automation Document for an unreachable Instance (i-xxxxxxxxx) :

# aws ssm start-automation-execution --document-name "AWSSupport-ExecuteEC2Rescue" --document-version "\$DEFAULT" --parameters '{"UnreachableInstanceId":["i-xxxxxxxxxxxxx"],"EC2RescueInstanceType":["t2.small"],"SubnetId":["CreateNewVPC"]}' --region eu-west-2
{
    **"AutomationExecutionId": "43f1918f-b0bb-4a25-xxxxxxxxxxxxx"**
}

• You can also see the automation scheduled (using Console)

• Checking the Automation progress / Status:

# aws ssm get-automation-execution --automation-execution-id "43f1918f-b0bb-4a25-xxxxxxxxxxxxxxxx" --output text --query "AutomationExecution.AutomationExecutionStatus"  --region eu-west-2
**InProgress**

• Let’s wait for few mins to get this completed and we can check the status again:

# aws ssm get-automation-execution --automation-execution-id "43f1918f-b0bb-4a25-xxxxxxxxxxxxxx" --output text --query "AutomationExecution.AutomationExecutionStatus"  --region eu-west-2
**Success**

• You can also verify this (using Console)

• After the Status is returned as “Success”, Let’s try to SSH to the Instance again: (Success)

# ssh -i "eu-west-2_key_pair.pem" ec2-user@ec2-xxxxxxxxx.eu-west-2.compute.amazonaws.com

Conclusion

AWSSupport-ExecuteEC2Rescue is a new Automation document that automates all the steps required to fix common issues on your unreachable Windows & Linux instance using respective EC2Rescue for Linux & EC2Rescue for Windows tool tools, which is a framework for executing diagnostic and troubleshooting modules for analyzing and remediating issues.

Overall, It will save a lot of time which is being invested with manual process of detach, attach volume and further steps to troubleshoot issues. This document does all the steps for you in an automated way in just few minutes.

Tip

With the integration between CloudWatch Events and Systems Manager
Automation, you can run AWSSupport-ExecuteEC2Rescue automatically in
response to an event in your infrastructure.

Thanks for reading.
Any feedback, please write it to me here in comments..
Also, 🤝🤗You can connect with me🤝🤗

LinkedIn
DevTo
GitHub
Twitter

👨‍💻👩‍💻How to use AWS Systems Manager Automation Document🧐to fix✅SSH issue on a Linux EC2 Instance☁️📢

Dinesh Rathee — Mon, 20 Jul 2020 00:44:41 +0000

When you face SSH issues over EC2 Instance👨‍💻☁️, What procedure do you follow ?

Stop the Instance --> detach root volume --> attach volume to rescue Instance --> and then further steps to troubleshoot issue

Right ?🤔💭

Here's something to Automate this procedure⏩⏩

"This procedure will save a lot of time which we invest with manual process. AWS Systems Manager Automation Document - "AWSSupport-ExecuteEC2Rescue" does all the steps for you in an automated fashion."

How it works ?👨‍🏭

It uses EC2Rescue for Linux & EC2Rescue for Windows tool, which is a framework for executing diagnostic and troubleshooting modules for analyzing and remediating issues on Windows and Linux instances.

Here I will discuss about most common SSH issue on Linux instance.

Also, I will guide you through Console way to get familiar with the workflow. If you're interested in using AWS CLI, please check out my Blog Post

How "AWSSupport-ExecuteEC2Rescue" works in the background ?💻

This Automation document executes EC2Rescue for Linux on an offline instance (which does not need to have the SSM agent installed or be user-accessible) by creating rescue resources, moving the root volume of the target instance to the rescue instance, and later reattaching the root volume to the original instance. - All will be done via an automated set of steps in the document, which are as listed here:

To know more on this document walkthrough, please check here.

Prerequisites🔎⚙️

Before you begin with next steps, you should have:

Required: "Instance ID" of the unreachable instance. You will specify this ID in the procedure.
In addition, there are some optional parameters, which you can refer here
The IAM role for this execution. If no role is specified, AWS Systems Manager Automation will use your IAM permissions of the user logged in to execute this document. To know more on granting permissions by using IAM policies, please refer here

I will explain more in details with below real time example.🎯🎯

Now, I will show you how to use AWS Systems Manager Automation Document - "AWSSupport-ExecuteEC2Rescue" in real time use-case for a common Linux SSH issue.

Issue😨😨:-

(I have changed permissions of */home directory to 777** and now I am not able to SSH and getting “Permission denied")*🚫😜

Checking SSH verbose output:

# ssh -vvv -i "eu-west-2_key_pair.pem" ec2-user@ec2-xxxxxxxxxxx.eu-west-2.compute.amazonaws.com

Getting permission denied error😖😖

Now , let’s use "AWSSupport-ExecuteEC2Rescue" Automation Document to Fix this issue:

• Open the AWS Systems Manager via EC2 Console -- Type "Systems Manager"

• In the navigation pane, choose Automation ----> Choose Execute Automation.

• In the Automation document section categories, You can choose "Self service support workflows" and check for the Document named - "AWSSupport-ExecuteEC2Rescue" like below and click “Next”

• Please provide the Instance ID of unreachable Instance (Required) and click Execute button to start Automation workflow:

Some Information on Input Parameters:💭💭

Mandatory / Required:

UnreachableInstanceId : (Required) ID of your unreachable EC2 instance. IMPORTANT: AWS Systems Manager Automation stops this instance, and creates an AMI before attempting any operations. Data stored in instance store volumes will be lost. The public IP address will change if you are not using an Elastic IP.
EC2RescueInstanceType : (Required) The EC2 instance type for the EC2Rescue instance. Recommended size: t2.small. (by default it is auto-selected )

Optional but could be really useful:

LogDestination: (Optional) S3 bucket name in your account where you want to upload the troubleshooting logs. > Make sure the bucket policy does not grant unnecessary read/write > permissions to parties that do not need access to the collected logs.

Now, Let’s proceed further
• Once you click on "Execute" Button, the Automation will start and you can the Status “In Progress”:

• To see more details you can click on the "Execution ID"

Checking what it does in the background:

• Procedure creates an SSM helper Instance / recovery Instance with name tag AWS-Support-EC2Rescue-I-xxxx

• Creates an AMI as well for Backup Purpose before it executes further steps:

• Stops the Problematic Unreachable Instance and Detaches the Root Volume from it and Attaches on the SSM enabled Recovery/Helper Instance:

• Then procedure runs EC2Rescue for Linux over helper Instance to Fix the Issue and you can also track the steps below:

• You can always check the details of each "Execution ID" and its Associated steps using “Step ID” , For example, checking details of “Step-2” below:

Please Note –

“It may show a step failed for Windows since the Instance is Linux,
So don't worry about it”🙆‍♂️👍

• You can monitor the Overall Status of the Procedure using the Execution Status tab under Automation Executions and wait for it to get “Success” which marks it as complete.

• Now, checking the Instance state again - You can see the Rescue / SSM enabled Helper Instance has been terminated and Automation have Started the Problematic Unreachable Instance again after fixing the issue:

Now, Let's Try to connect to the Instance:👩‍💻🤔

I am able to SSH and Issue has been fixed now. ✅✅🏁🏁

Interested to know about logs to see what was fixed on Instance to gain access?❓🙋‍♂️

• You can check the details of Step ID “getEC2RescueForLinuxResult” which will provide you a location of the log presence on instance.

• Please make a note of the location displayed there for example, In my case - The output logs are located in: /var/tmp/ec2rl/2020-06-25T01_44_08.560197

• Now, I will check the Log location on instance and see detailed information as follows:

Hence, I have also identified what fixes have been applied by EC2Rescue for Linux over instance to fix the issue in an automated way.

Conclusion🎯🧐📚🤖

Tip

With the integration between CloudWatch Events and Systems Manager
Automation, you can run AWSSupport-ExecuteEC2Rescue automatically in
response to an event in your infrastructure.

Also, I would like to mention that above I've guided you through Console way to get familiar with the workflow. If you're interested in using AWS CLI, please check out my Blog Post

Thanks for reading.
Any feedback, please write it to me here in comments..
Also, 🤝🤗You can connect with me🤝🤗

LinkedIn
DevTo
GitHub
Twitter