We are pleased to announce today that Shipa, the cloud-native Application as Code [AaC] platform is now available on the AWS Marketplace. Bringing the power of Shipa to your internal customers on AWS infrastructure has never been easier with click to install from the AWS Marketplace.
Installing Shipa from the AWS Marketplace
Installing from the AWS Marketplace is straightforward leveraging the AWS CLI and Helm. You first will need to subscribe to the product.
Once you have subscribed, head over to the subscription then enter the configuration.
Select a version then Continue to Launch.
If you have an existing EKS Cluster, you can skip Step 2 in the launch instructions. As versions update, make sure to follow the latest Launch and Usuage Instructions.
Installation Commands
The first step is to authenticate to the ECR repository holding the Helm Chart.
export HELM_EXPERIMENTAL_OCI=1 aws ecr get-login-password --region us-east-1 | helm registry login --username AWS --password-stdin 709825985650.dkr.ecr.us-east-1.amazonaws.com
Then next pull the Helm Chart.
helm chart pull 709825985650.dkr.ecr.us-east-1.amazonaws.com/shipa/shipa:1.6.1
Next, export the Helm Chart
helm chart export 709825985650.dkr.ecr.us-east-1.amazonaws.com/shipa/shipa:1.6.1 --destination ./awsmp-chart
You will notice a new folder.
Now you are ready to install from the AWS Marketplace. The Usuage Instructions have the full Helm Values that you need to install.
E.g
helm install --generate-name --namespace shipa-system --create-namespace --timeout=15m --set=auth.adminUser=admin@shipa.io --set=auth.adminPassword=shipa2022 ./awsmp-chart/*
Once you execute, you are now ready to start your Shipa adventure!
The next steps would be to download and wire your Shipa CLI Client, head to the Shipa Dashboard, and create your first set of Shipa objects such as a Framework.
Shipa and AWS, Better Together
Providing a clean developer experience is certainly a challenge. Not only having to navigate application complexities but infrastructure and application infrastructure complexities such as Kubernetes increase toil on developers. Allowing Shipa to abstract out the application definition and policy enforcement across your EKS clusters will certainly allow developers to focus on the features.
Cheers,
-Ravi