Fieldtex Products, Inc.

Fieldtex is a private family owned company that operates out of a 55,000 sq.ft. facility in Rochester, NY and employs over 190 people.

It was founded in 1973 and is made up of three divisions:

Division 1: Fieldtex Cases – Their contract manufacturing division that produces soft sided carrying cases for portable electronic equipment for medical and military markets, wearable medical and military garments, and other textile innovations.

Division 2: Fieldtex Medical – Their First Aid Supplies division, distributes stock First Aid Kits, custom First Aid Kits, and First Aid supplies to emergency medical corps., schools, cities, towns, youth team sports leagues and the general safety marketplace.

Division 3: OTC Benefits Solutions – Works with Health Plans and other organizations to offer Supplemental Over the Counter Benefit Programs to members of Medicare Advantage Health Plans.

The Challenge

Fieldtex had multiple applications hosted with a relatively expensive offsite provider. As part of a tech refresh most applications were migrated to new hardware and their public facing .com website was the only application being hosted on two large legacy servers that were significantly over-provisioned (two 16×64 servers). Source control was not in place and there was no formal release process.

The Solution

Innovative proposed migrating their .com website to AWS, leveraging appropriately provisioned Amazon EC2 instances in AWS Elastic Beanstalk environments. AWS CodeCommit allowed for the website’s code to be to be version controlled. AWS CodePipeline was leveraged to create application packages that could be deployed to the AWS Elastic Beanstalk environments. Amazon Aurora Serverless was used to minimize infrastructure costs and operational overhead while providing flexibility in the case of unexpected bursts of traffic. Amazon SES is used to send email.

Innovative also created an integration with Office 365 APIs to push notifications to Microsoft Teams whenever a manual approval is needed. This was accomplished by creating an Amazon SNS topic for manual approval steps that triggers an AWS Lambda function that pushes to Office 365.


  • This field is for validation purposes and should be left unchanged.