Intern Resume

PROFESSIONAL SUMMARY:

Passionate and skilled engineering graduate with certified networking & cloud skills; seeking a position in computer networking and cloud computing.

TECHNICAL SKILLS:

Amazon Web Services(AWS), VMWare
HTTP, Frame Relay, SMTP, FTP, NTP, SNMP, IPv4, IPv6, OSPF, Confidential, BGP, STP, HSRP TCP/IP, ARP, UDP, DNS, DHCP, SSH, Telnet, SSL NAT, ACL, WAF, Event driven Security on AWS Chef (OpsWorks in AWS)
Wireshark, Splunk, CloudTrail GNS3, Cisco Packet Tracer, VMWare
S3, EC2, Lambda, RDS, EBS, SQS, SNS, SES, VPC, ELB, ElasticCache, CloudWatch,
RedShift, DynamoDB, AWS Import/Export, CloudTrail, CloudFormation, Docker on
ECS, IAM, AWS CLI, Data Pipeline
Windows, Mac OS, Cisco IOS, Linux
IEEE 802.11a/b/g/n/ac
C, C++, Python, Bash
MS Word, MS PowerPoint, MS Excel

WORK EXPERIENCE:

Intern

Confidential

Responsibilities:

Leveraged Route53 to create a complex DNS - level routing policy. Initiated four EC2 instances to mimic a multi-region environment and using a bottom up approach to first build region independent DNS and then point to the top level domain.
Weighted routing policies were used when configuring Route53 Record Sets.
By default, the servers behind an ELB do not receive information of the Client IP address. For a better logging system, it is desired that the servers store Client IP addresses accessing the application for parsing later on by a third party IDS/IPS appliance.
Proxy Protocol enables configuration of an additional header being passed to the webservers, that contains Client information accessing the ELB.
Traffic load balancing using Confidential . Used variance to understand load balancing in the topology.
Leveraged a Lambda function to execute a basic JavaScript code to add objects obtained from the Kinesis stream.
Also used lambda function with SNS and DynamoDB, such that with every new entry to the table, Lambda function was called to initiate SNS.
Used a Pipeline to move all the tables in an RDS database from one region to another, in a S3 bucket as csv files.
Configured a custom VPC with two subnets, a public subnet and a private subnet.
The private subnet had a Webserver with access to a provisioned Internet Gateway and a NAT instance to provide connectivity to the database server through the webserver.