You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having problems deploying my site to different AWS accounts for staging purposes. I have two AWS accounts, one for DEV and one for PROD. My current approach to deploy to either one is by running sls deploy --stage <stage> --aws-account <account>. Each AWS account stored within .aws/credentials is pointing to the corresponding IAM user with admin access. It seems like the --aws-account flag is being ignored and the bucket is created in the account associated with the provider account linked within the Serverless dashboard.
I also tried adding a provider for each account for my app within the dashboard following https://www.serverless.com/framework/docs/guides/providers/. By doing this I'm able to deploy other components (database, api, permissions) to the right accounts but the website component keeps failing with an Access denied error.
So am I missing something? My goal is ultimately to wire this up to a CI/CD pipeline - what is the correct way to deploy to different AWS accounts/stages?
The text was updated successfully, but these errors were encountered:
I'm having problems deploying my site to different AWS accounts for staging purposes. I have two AWS accounts, one for DEV and one for PROD. My current approach to deploy to either one is by running
sls deploy --stage <stage> --aws-account <account>
. Each AWS account stored within.aws/credentials
is pointing to the corresponding IAM user with admin access. It seems like the--aws-account
flag is being ignored and the bucket is created in the account associated with the provider account linked within the Serverless dashboard.I also tried adding a provider for each account for my app within the dashboard following https://www.serverless.com/framework/docs/guides/providers/. By doing this I'm able to deploy other components (database, api, permissions) to the right accounts but the
website
component keeps failing with anAccess denied
error.So am I missing something? My goal is ultimately to wire this up to a CI/CD pipeline - what is the correct way to deploy to different AWS accounts/stages?
The text was updated successfully, but these errors were encountered: