1. Required Skills and Knowledge
The deployment guide is designed to support non-technical users with step-by-step instructions for launching the platform via AWS Marketplace.
However, for ongoing maintenance and operations, the following baseline knowledge is recommended:
Basic Familiarity with AWS Services:
IAM – managing user roles and permissions
EC2 – locating instances, viewing logs, and basic restart actions
S3 – accessing uploaded media and configurations
VPC & Networking – reading subnet, routing, and gateway setups
CloudFormation – reviewing stack outputs and troubleshooting
Understanding AWS Marketplace:
Subscribing to the product
Accessing deployment documentation and release notes
Monitoring usage, updates, and support options
Domain & SSL Awareness:
Configuring DNS to custom domains
Understanding SSL/TLS certificate roles and propagation time
2. AWS Account Access & Permissions
No AWS root user credentials are required. Instead, you should use an IAM user or role with the following capabilities:
Subscribe to AWS Marketplace products, initiate the provisioning process
Deploy infrastructure using AWS CloudFormation
Request any necessary service quota increases via AWS Support.
View billing and usage information (optional but recommended for cost monitoring)
Have the appropriate permissions to create and manage the required infrastructure components, including but not limited to:
Service | Required Components |
|---|---|
Identity and Access Management (IAM) | Roles, Policies, Instance Profiles, OIDC Provider |
Elastic Kubernetes Service (EKS) | Cluster, Node Groups, Add-ons (VPC CNI, CSI) |
Elastic Compute Cloud (EC2) | Launch Templates, Auto Scaling Groups, Elastic IPs |
Virtual Private Cloud (VPC) | VPC, Subnets, Route Tables, NAT, Internet Gateway, NACLs, DHCP Options |
Amazon RDS | DB Instances, Subnet & Parameter Groups, Security Groups |
Amazon ElastiCache | Redis Cluster, Subnet Group, Security Group |
Amazon MSK | Kafka Cluster, Security Group |
OpenSearch Service | Domains, Security Groups |
S3 | Buckets, ACLs, CORS, Ownership Controls |
Elastic Load Balancing (ELB) | Load Balancers, Target Groups |
AWS Certificate Manager (ACM) | Certificates |
AWS Key Management Service (KMS) | Keys, Aliases |
Systems Manager (SSM) | SSM Parameters (e.g., for AMI) |
It is also strongly recommended to get the fundamental knowledge on AWS Service listed above. If you are interested to learn more please use this link.
3. Domain Name System (DNS) Mapping
To make the application accessible from the Internet, you must configure a public DNS record pointing to the solution's load balancer or public endpoint. This can be done using your preferred DNS provider or services like Cloudflare or Route 53.
It is recommended to use a subdomain (e.g., ph.yourdomain.com) and ensure that appropriate DNS records (typically CNAME or A/ALIAS) are in place. This step is essential for enabling user access and setting up HTTPS via SSL/TLS certificates.
Note: DNS changes may require some time to propagate globally.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article