AWS
Cloud hosting for your app's infrastructure — set up the account and grant us access so we can deploy and manage it.
Why we need this
AWS is where your app's infrastructure lives: the compute, managed databases, and object storage that run your backend and keep it online. Calda needs access so we can deploy new versions, configure services, and keep an eye on your infrastructure.
Like all other accounts, this one should be owned by you. Your servers, data, and billing are tied to the account, so keeping it under your company means your infrastructure — and everything running on it — belongs to you, not us.
Do I need a credit card?
Yes. AWS requires a valid payment method (credit card) to activate an account, and you're billed for the resources your app uses — there's no free tier for hosting like there is with email providers.
Billing stays under your account
Because hosting is a paid, usage-based service, the payment method and all infrastructure billing live under your AWS account. We'll help you right-size resources so you only pay for what your app actually needs.
Step-by-step setup
Create the AWS account
Sign up at aws.amazon.com using your company email, then add a payment method when prompted. You'll sign in as the root user — the account owner with full control — which you'll use to create the access we need in the next steps.
Create an IAM user for Calda
In the AWS console, open the IAM service, go to Users → Create user, and
name it something recognizable like calda-deploy. On the permissions step,
attach AdministratorAccess (or a deployment-scoped policy we agree on) so we
can set up and manage the services your app needs.
What we'll do once we're in
After you've created the user, we'll set up the compute, databases, and any other services your app needs — you don't need to configure anything else.
Generate access keys
Open the calda-deploy user, go to Security credentials → Create access key,
and choose the Command Line Interface (CLI) use case. AWS will show an
Access Key ID and a Secret Access Key — the secret is only shown once,
so capture both before closing the page.
Share the keys securely with Calda
Send us the Access Key ID and Secret Access Key through the secure method we share with you.
Don't paste secret keys in plain Slack messages
Access keys are passwords for your account. Avoid pasting the secret key directly into a regular chat or email — use the secure share method we provide so it doesn't end up in your message history.
Confirm in Slack
Don't forget to notify us in Slack so we can verify the keys work and confirm we can sign in.
Conclusion
That is it — with this access we can deploy and run your app on your own AWS account. Once you've shared the keys and confirmed in Slack, we'll handle the rest of the infrastructure setup on our side.
How is this guide?
Codemagic
Continuous delivery for your mobile app — build, sign, and ship iOS and Android releases automatically. Set up the account and invite us so we can run the pipeline.
Google Cloud
The Google Cloud project behind your app's Google APIs — Sign-In, Maps, push notifications, and more — set up the account and grant us access so we can configure them.