What AWS skills should I prioritize for analytics and business strategy?
Asked by
MellowHarbor42
My company is moving its data sources—such as our CRM and project-management tools—into AWS. I now have access to explore the tables and dashboards, and my immediate work will mainly involve Amazon Athena and QuickSight. I work in Revenue Operations and Corporate Strategy rather than Data or Infrastructure, so I'm trying to figure out what AWS topics would be most valuable to learn next. Should I focus on the broader AWS fundamentals, services that support Athena and QuickSight, cost management, security, or something else?
Answers
Since your role touches strategy and operations, learn the cost side as well. Understand resource tagging by team, program, or business domain, along with budgets, alerts, cost reports, and chargeback or showback. Those practices make it much easier to identify what each initiative is costing and to have useful conversations with the technical team.
Reply to this answer
First, clarify whether you’ll just be an end user of the analytics environment or whether you’ll help administer it. If you’re mainly querying data and building dashboards, prioritize Athena and QuickSight, including SQL, data modeling, permissions from a user perspective, and dashboard design. You don’t need to learn every AWS configuration detail right away. It’s still useful to understand that Athena commonly queries data in S3 and that Glue may catalog and prepare that data, while IAM controls access.
Reply to this answer
Don’t overlook security basics. Learn the CIA triad—confidentiality, integrity, and availability—then get familiar with IAM, least-privilege access, authorization, and multifactor authentication. Avoid making data publicly accessible unless there is a deliberate, reviewed reason. The Well-Architected Framework is also a useful overview because it covers security, reliability, operational excellence, performance, cost optimization, and sustainability.
Reply to this answer
The Cloud Practitioner learning material is a good starting point even if you never take the certification exam. It gives you a practical overview of AWS concepts, accounts, regions, identity, storage, databases, networking, security, and pricing without going too deep into infrastructure. After that, focus on the services your team actually uses rather than trying to study AWS as a whole.
Reply to this answer
Add your answer
Answers are reviewed before publication.
MellowHarbor42: That sounds like the right level for me. I’m looking for enough context to understand how our data environment fits together, not to become an infrastructure engineer.