.svg?alt=media&token=0f6df7c7-5b98-4a62-98b8-a54e38a8329e){kind=logo}
AWS FAQ
Popular and frequently asked questions about DuploCloud and AWS
Last updated
Popular and frequently asked questions about DuploCloud and AWS
Last updated
© DuploCloud, Inc. All rights reserved. DuploCloud trademarks used herein are registered trademarks of DuploCloud and affiliates
AWS Copilot is used only for ECS cluster management, which is a small subset of overall cloud operations. The chart below shows that DuploCloud includes container management and multiple other functions. You can still use Copilot with DuploCloud for ECS management. Other clients have used tools like Harness or Helm with DuploCloud for Kubernetes management.
If your application runs in a DuploCloud Tenant, you do not need a long-term credential like an AWS access key. After your application runs in the Tenant, test your connection using the AWS CLI to verify access.
Use the AWS constructor that takes only the region (e.g., us-west-2) as the argument. DuploCloud setup links your instance profile and resources. The DuploCloud Host already has access to the resources within the Tenant. DuploCloud AWS resources are reachable only from DuploCloud Hosts on the same account.
IMPORTANT: You cannot connect to DuploCloud AWS resources from your local machine.
Duplo uses an IAM role, specifically an instance profile, to access AWS accounts. This methodology does not involve access keys.
See the DuploCloud documentation on Cross-Tenant Access.
To give DuploCloud Services (i.e., Cronjobs) access to an S3 bucket created in a non-DuploCloud AWS account, add the following permissions to your AWS accounts.
After you add these permissions, s3GetObject permission is configured in the source and destination accounts respectively, enabling cross-account data sharing for the objects in the S3 bucket.
Depending on the use case, you may need to add additional permissions. For example, in addition to the s3:GetObject permission shown in the snippets above, you may need to add s3:ListBuckets or s3:PutObject. Be sure to add permissions to both policies, respectively, as shown in the example.
In DuploCloud, AWS Control Tower is not directly managed. DuploCloud installs in an EC2 instance within your AWS account and provides a web interface, API, and Terraform provider to manage your AWS infrastructure. It handles the lower-level nuances of AWS configuration, such as access control, security, and compliance, through its automation and best practices.
DuploCloud's concept of "Tenants" is a logical construct above AWS that represents an application's entire lifecycle, including dev, stage, and production environments. It automatically configures the necessary AWS services, IAM policies, and other resources within each Tenant, without the need for complex AWS Control Tower setup and management.
Additionally, DuploCloud provides Just-In-Time (JIT) access to the AWS console and CLI, with least-privileged IAM permissions and short-lived access, making it more secure and easier to manage than traditional AWS access methods.
Yes. This is a major advantage of using DuploCloud. All controls are mapped to various compliance standards. DuploCloud is also very flexible, enabling you to add custom policies (resource quotas, the ability to create public-facing endpoints, etc.).
To estimate Amazon GuardDuty pricing, you can use the AWS pricing calculator.
No, enabling or disabling Amazon GuardDuty does not affect the vulnerabilities and security standards insights DuploCloud provides.
CI/CD is the topmost layer of the DevOps stack. DuploCloud should be viewed as a deployment and monitoring solution invoked by your CI/CD pipelines, written with tools such as CircleCI, Jenkins, GitHub Actions, etc. You build images and push them to container registries without involving DuploCloud, but you invoke DuploCloud to update the container image. An example of this is in the CI/CD section. DuploCloud also offers its own CI/CD tool (KatKit).
If your application runs in a DuploCloud Tenant, you do not need a long-term credential, such as an AWS access key. After your application runs in the Tenant, test your connection using the AWS CLI to verify access.
DuploCloud provisions a Load Balancer for your K8s service. If you want to look at detailed Load Balancer settings like idle timeout, access logs, and more, you can view them in AWS by following these steps:
Find the Load Balancer name for your service by navigating to Kubernetes -> Services, selecting your Service from the list, and clicking the Load Balancer tab. If you're using K8s Ingress, go to the K8s Ingress tab to find the Load Balancer configuration.
Once you have the Load Balancer name, you can access the AWS Console via the DuploCloud UI. In the AWS Console, navigate to the EC2 service view and select Load Balancers from the left navigation menu. Find your Load Balancer name and scroll down to view detailed attributes.
Many customers prefer Terraform to CloudFormation. There are many non-AWS cloud DevOps elements (e.g., native Kubernetes, MongoDB, Data Dog, Okta, etc.), and all support Terraform providers.
No. DuploCloud achieves High Availability (HA) using cluster management. You own your AWS account, so your data is always secure in AWS.
Our customers have never been blocked from performing urgent configuration updates because DuploCloud is unavailable. If DuploCloud is down, it is similar to your DevOps engineer being unavailable. In this case, someone else can take their place by directly configuring AWS.
Our customers consider this single-platform approach beneficial for centralizing operations and maximizing developer access. DuploCloud runs in a VM in your account. We manage this VM with your permission, and we can also give you simple steps to troubleshoot or install new updates. We are available 24x7 and work as your extended DevOps team.
Yes. DuploCloud manages scale in the same way. We expose these thresholds in a simple form that is much easier to configure, even for a user with no DevOps experience. Behind the scenes, DuploCloud maps to the same native AWS constructs.
You can create AWS secrets from within the DuploCloud Portal and the Tenant-scoped permissions will work. If you encounter any issues, please let us know.
The documentation for using AWS Secrets Manager in DuploCloud can be found here; however, this documentation does not provide instructions on how to use Tenant-specific AWS Secrets Manager.
Yes. This documentation provides more details about using the SecretProviderClass and mounting AWS Secrets Manager secrets in DuploCloud.
Yes, Kubernetes is necessary to integrate AWS Secrets Manager with DuploCloud using the SecretProviderClass.
For Native Docker, we recommend loading the secrets as part of your entry point script using the AWS CLI. For more information, refer to the AWS documentation.
Another option is to use the AWS Software Development Kit (SDK) and the associated documentation.
The existing permissions in DuploCloud are sufficient to access AWS Secrets Manager.
Small instances are generally no problem. DuploCloud can manage dynamic database spin-up/down with a single RDS database. Sharing AWS services in dynamic environments also helps reduce costs.
Yes.
Yes. See AWS Console and your cloud provider for compatibility requirements. While versions 5.7.40, 5.7.41, and 5.7.42 cannot be upgraded to version 8.0.28, you can upgrade these versions to version 8.0.32 and higher.
Yes.
DuploCloud creates and tests changes to the DuploCloud platform to support the new EKS version. Once testing is complete, updates are rolled out on the DuploCloud customer platform. Then, users can update the EKS version.
There may be a delay between the release of a new EKS version and a DuploCloud version that supports it. This is due to the time needed to develop and test changes to the DuploCloud Platform. DuploCloud ensures customers are always on a supported/non-deprecated version of EKS.
DuploCloud notifies users when an EKS upgrade is planned.
The upgrade plan scope includes everything (by DuploCloud or Helm) deployed on the cluster.
