| Location | Fort Lauderdale, FL (Remote) |
All current openings
AWS Architect
Easy ApplyApply Now
Job Description
AWS Architect - Principal AWS Enterprise Architect
Location: Fort Lauderdale, FL (Remote)
Job Type: C2C
About the Role
Join a high-impact, remote-first team as a Principal AWS Enterprise Architect. You will architect and implement foundational AWS platforms that empower multiple application teams to build and scale securely. This hands-on role offers you the chance to lead the design and delivery of enterprise-scale AWS environments, directly shaping infrastructure, security, identity, networking, and compliance for a regulated, data-driven organization.
Responsibilities
Required Skills and Experience
Preferred Skills
Benefits
How to Apply
Ready to architect the future? Submit your resume showcasing your AWS landing zone experience, technical leadership, and reference architectures. Qualified candidates will be contacted promptly for next steps.
Easy ApplyApply Now
Interested in this role?
Easy ApplyApply Now
Job details
Job ID JPC - 205910
Location Fort Lauderdale, Florida, United States
Work Model On-site
Job Type C2C
Posted July 2, 2026
Skills Principal AWS Enterprise ArchitectThe roleWe're looking for a Principal AWS Enterprise Architect to design the AWS environment our application teams will build on top of This is a foundation and platform role Workload migration is owned by other team how the network is laid out how identity works how we connect back to the data center how we protect PII how we host Databricks and VDI and what guardrails and patterns the rest of the org consumesThis is a hands-on architect role We expect diagrams working IaC reference modules written decisions and time in the room with security Networking Data and application leadership - not just recommendations By the time you wrap the in-house team should own and be able to extend what you leave behindWhat you'll work onAWS foundation and landing zone• The target AWS Organizations layout: OUs the account model (workload security log archive network Shared Services sandbox) and how new accounts get vended Control Tower is on the table pick what makes sense• SCPs permission boundaries and a tagging policy that actually gets enforced• Baseline guardrails wired in from day one: CloudTrail Config GuardDuty security hub IAM Access Analyzer centralized log aggregation• Reference IaC - Terraform preferred CDK acceptable - that workload teams inherit when they get a new accountIdentity and access• Federation through IAM Identity Center integrated with our corporate IdP (Okta) A clear story for break-glass JIT elevation and what humans get vs what workloads get• Role and policy patterns workload teams can reuse without inventing their own Least privilege ABAC where it actually pays off permission boundaries• Secrets and KMS Key hierarchy rotation cross-account access - the boring stuff that has to be rightNetwork• Multi-account topology with Transit Gateway Shared VPCs through AWS RAM segmentation by environment and sensitivity and DNS (Route 53 Resolver private zones hybrid resolution)• Hybrid connectivity to the data center Direct Connect with a resilience model that matches our risk tolerance Direct Connect Gateway VPN as backup
Share this job
*