Hi Amit, Scalr is only able to leverage the Cloud Credentials that are configured for a given Environment. If you have fully deleted the previous AWS credentials from Scalr, there should be no way that Scalr would continue to provision instances using the non-existant AWS credentials. If you are able to consistently replicate this issue, please attach screenshots of your AWS account configured for the Environment, steps to reproduce in the Scalr UI, and wrong-account confirmation from your AWS console UI. These will be helpful to better understand your experience.
Many thanks, Wm. Marc O'Brien Scalr Technical Support On Wednesday, February 1, 2017 at 7:36:40 AM UTC-7, Amit Saini wrote: > > Hi Team, > > I want to replace new AWS account in Scalr. I have deleted the key and > added new key which is related to new account AWS and then launch the > Instance but Instance is launched in old AWS account > > Regards > Amit > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
